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.
There are around 27,200 people in the United Kingdom doing a job that official statistics cannot find. They read customer drawings, size and configure products, run the calculations and write the technical quotes that industrial firms live on. Ask the firms and the role is obvious. Ask the labour market data and it dissolves.
- 27,200
- employed application engineers in the UK
- 16
- candidate occupation codes the title spreads across
- 44%
- of sampled job adverts out of scope on review
Central estimate, grade B
SOC 2020, grade B
286 of 645 adverts
One role, three classifications
The trouble starts with the title. Application engineer maps to no single code in SOC 2020, the standard occupational classification the UK statistics system runs on. Depending on the wording of the advert alone, the same job lands in an engineering professional group (the 212x codes), an engineering technician group (311x) or a sales group (3552 or 3556). Across our crosswalk it touches sixteen candidate codes.
The confusion runs deeper than coding. In a hygiene review of 645 job adverts pulled for the role, 286 of them, 44%, fell out of scope once the software developer sense of the title and pure sales roles with no engineering content were stripped away. The role straddles engineering and sales and sits cleanly in neither, which is exactly why the taxonomy keeps dropping it.
Why an invisible role stays underserved
Software vendors size markets from occupation codes. Analysts build reports from them. Budgets get argued from headcount lines that roll up to them. A role split across sixteen codes never shows up anywhere as itself, so nobody builds for it, and the people doing the work inherit tools designed for someone else: CRM built for salespeople, CAD built for designers, spreadsheets built for everything left over.
A function this large that the standard taxonomy cannot see is a function that standard tooling has not been built for.
The numbers, with their error bars
Because no clean code exists, no off-the-shelf market figure exists either. The numbers below are triangulated from official employment pools, the composition of live job adverts and the company register, and each carries a confidence grade. We publish the grade beside the number on purpose: a graded estimate you can interrogate is worth more than a confident figure you cannot.
| Lens | Central estimate | Envelope | Grade |
|---|---|---|---|
| People | 27,200 employed | 11,550 to 30,550 | B |
| Money | £1.36bn gross salary a year | £482.6m to £1.85bn | C |
| Hiring | about 900 new adverts a month | 186 live in scope | B official, C live |
What the miscount costs
If you employ application engineers you already know the practical version of this story. They are scarce, they are expensive at a blended £50,115 gross salary per head, and when one leaves the replacement takes months because nobody can even agree what to put in the advert. The miscount is not a statistical curiosity. It is the reason the quoting bottleneck in industrial firms has stayed a people problem for decades while every adjacent function got software.
We built Kabaido for the work this role actually does, starting with the part that gates every order. But the first step was simply proving the role exists at scale, and that took counting a workforce the official numbers cannot see.
Sources and method
- ONS Annual Population Survey, four digit occupation estimates (statistic in development)
- SOC 2020, the UK Standard Occupational Classification
- Adzuna live job adverts, UK snapshot of 4 June 2026
- Kabaido market research: UK application engineer headcount analysis, 4 June 2026