Skip to content

Where £1.36bn of quoting capacity sits

UK application engineer pay barely varies by domain, so headcount is the whole map. Three domains hold 41.7% of it. A tour of a top-heavy market.

Industry researchKabaido2 min read

The most surprising thing in our salary research is how boring the pay is. Across 19 industrial domains, every single one sits within 14% of the £48,892 advertised median for application engineers. A bearings specialist, a metrology engineer and a fluid power engineer all cost their employers roughly the same. Which means the interesting question is never what the role costs. It is how many of them each domain employs.

£1.36bn
annual gross salary spend on UK application engineers

Grade C, envelope £482.6m to £1.85bn

15,650
engineers in the five densest domains

Fluid power, machine tools, automation lead

within 14%
every domain's pay against the £48,892 median

The top five domains

Estimated UK application engineer headcount and salary spend, top five domains, snapshot 4 June 2026. Headcount grade B, spend grade C.
DomainHeadcountShareSalary spend
Fluid power4,30015.8%£210.3m
Machine tools and CNC4,10015.1%£200.7m
Automation and robotics2,95010.8%£148.7m
Sensors and industrial IoT2,2008.0%£116.0m
Bearings, motion and power transmission2,1007.8%£106.0m
Top five together15,65057.5%£781.7m
Estimated UK application engineers by domain, top five (grade B)Fluid power4,300£210.3mMachine tools and CNC4,100£200.7mAutomation and robotics2,950£148.7mSensors and industrial IoT2,200£116.0mBearings and motion2,100£106.0mTop three hold 41.7% of headcount; top five hold 57.5%. Snapshot 4 June 2026.
Headcount by domain, top five. Because pay is near-uniform, the headcount ranking and the spend ranking are the same list.

Flat pay makes headcount the map

When pay varies a lot between segments, market maps get complicated: you weigh people against rates and argue about mix. Here the uniformity does the work for you. Salary spend and headcount rank the 19 domains in the same order, so one chart answers both questions. Where the engineers are is where the money is, and the engineers cluster hard. The top three domains hold 41.7% of headcount and 41.1% of spend. The top five hold 57.5% and 57.3%.

A top-heavy market with thin tails

The tail is genuinely thin. Materials and metallurgy returned no in-scope live advert at all in our snapshot, and seven further domains rest on fewer than ten posting observations each, which is why their figures carry a C grade. This is not a market spread evenly across industry. It is a handful of dense domains, then a long quiet shelf.

For anyone building for this workforce, the concentration is the strategy. A product proven in machine tools, fluid power and automation reaches the majority of the spend while touching a fraction of the surface area. The same logic applies inside a distributor or manufacturer deciding where to standardise its quoting first: start where the engineers are.

The lever on this £1.36bn is throughput per engineer, not price.

Because pay is flat and the work is repeatable, the spend is best read as the cost of human throughput on specification and quoting. Anything that lets one engineer specify and quote more, faster, moves that number directly. Hiring moves it too, in the wrong direction, and as we cover elsewhere on this blog, the market is already trying to hire its way out and struggling.

Sources and method

More from the blog

Industry research2 min read

You cannot hire your way out of a quoting backlog

The UK posts about 900 new application engineer adverts a month against a 27,200 base. What continuous re-hiring of a hard-to-define role really signals.

Read the post
Industry research3 min read

The job title the labour market cannot see

Around 27,200 people in the UK do a job that official statistics cannot find. Here is what happens when a role spreads across sixteen occupation codes.

Read the post
Inside the work2 min read

What an RFQ actually contains

An RFQ looks like a document. It is closer to a scattered set of claims, each hiding somewhere else. How engineers read one, and how software should.

Read the post

Put the research to work

Kabaido reads requests the way the engineers in these posts do: structured, cited and honest about gaps.