Last week we reviewed 12 deep-tech roles across 3 disciplines — and 10 of them carry "Systems Engineer" or "Systems Architect" in the title. Same label, wildly different jobs.
The "Systems Engineer" talent pool has 74,636 engineers across 133 companies — sounds easy. But only 30% sit in aerospace & defence (22,468 engineers across 32 companies), and just 11% sit in software platforms (8,308 engineers). A Cloudflare Systems Engineer writes distributed-systems IPC code; a Leonardo Systems Engineer owns radar requirements documents; a Spire Systems Engineer specifies satellite payload buses. They pull from completely non-overlapping pools — but keyword searches return the same CVs.
The same 74,636-engineer pool collapses to 22K (defence) or 8K (hyperscaler) depending on sector.
The signal: 10 of 12 roles share one title. Three of them pull from different talent pools entirely — defence (22K), hyperscaler software (8K), space (a few thousand). The job title is the weakest filter in deep-tech sourcing.
Even starker: the "Systems Architect" market is a different animal entirely — 23,929 engineers across 52 companies, 44% in semiconductor, 32% in software, and only 2.7% in aerospace & defence (653 engineers). Airbus Defence and Space hiring a Systems Architect in Guildford is fishing in a 653-engineer defence-architect puddle, not the 22K defence-systems-engineer ocean. Same word. Different market.
Roles We Reviewed
Systems Engineering — Defence (6)
→
Saab — Systems Engineer (Radar), Fareham
Radar + signal processing + SC clearance — the real pool is the 22K defence subset, not the 74K headline
→
Thales — Senior Hardware Systems Engineer, Crawley
Naval / maritime hardware SE — competes with BAE, QinetiQ, and Ultra along the south coast corridor
→
Leonardo — Systems Engineer (Radar Systems), London
AESA radar + electronic warfare — Edinburgh, Luton, and south coast radar clusters are the primary pool
→
Ultra I&C — Principal Systems Engineer, Maidenhead
Secure comms + SIGINT + DV clearance at principal level — Thames Valley / Cheltenham cluster
→
BAE Systems — Senior Systems Engineer, Portsmouth
Naval MBSE + ISO 15288 — Barrow, Glasgow, Bristol, Portsmouth are the cleared maritime clusters
→
Airbus Defence and Space — Systems Architect, Guildford
Architect market is tiny (24K total) and only 2.7% in defence — most hires require cross-industry recruitment
Systems Engineering — Space (3)
→
Spire Global — Senior Systems Engineer, Glasgow
Nanosatellite + RF payload + on-orbit — cross-over from semi + software, not defence
→
SSTL — Senior Systems Engineer, Guildford
Mission lifecycle + AIT + thermal/structural/EMC — space-specific pool overlaps Spire
→
CesiumAstro — FPGA Engineer I, Milton Keynes
Space comms startups recruit from semiconductor + defence radar teams — same DSP foundation
Systems Engineering — Hyperscaler (2)
→
Cloudflare — Senior Systems Engineer, Durable Objects DevEx, London
Distributed systems + API design + hyperscale — 8K-engineer software subset, not defence
→
Cloudflare — Principal Systems Engineer, IPC, London
Principal IPC + concurrency at hyperscale — dozens of candidates globally, not thousands
FPGA Engineering — Defence (1)
→
MBDA — FPGA Designer, Bristol
FPGA pool is 36K total but only 5% in defence — competing head-on with semiconductor firms for RTL talent
Model-based systems engineering is now table stakes in defence + space. Engineers without it filter out of principal-level shortlists — but it means nothing at Cloudflare.
SC / DV Clearance7 of 12 roles
The single biggest pool-shrinking factor. Cleared candidates are in long programme cycles with 3–6 month notice periods — and nearly impossible to poach without security sponsorship.
Radar / DSP / RF Signal Processing5 of 12 roles
Transferable foundation across defence radar, space comms, and EW. The recruiter's cross-sector bridge — Saab, Leonardo, MBDA, CesiumAstro, Spire all draw from the same DSP base.
Distributed Systems + IPCWatch this space
Only 2 of 12 roles (both Cloudflare). Hyperscale systems engineering is a completely different discipline sharing nothing but the title with defence SE. Different maps, different CVs, different pipelines.
Map by (domain + seniority + clearance), never by title alone
"Systems Engineer" is the most overloaded title in deep tech. A single keyword search returns 74K LinkedIn profiles — but 95%+ of them are irrelevant to any given role because the domain is wrong. Sector (defence / space / hyperscaler / semi) is what makes a profile actually match.
Before you run the LinkedIn search, decide which of these three pools you're actually in: defence + aerospace SE (~22K, cleared + MBSE + V-model), hyperscaler + software SE (~8K, distributed systems + dev tools), or space / new-space SE (small overlap of the above, mission lifecycle + RF payloads). When the title is "Systems Architect", stop — that's a different market entirely.
Three Questions Before You Search
1
What does the system control? RF waveforms → radar pool; microservices → hyperscaler pool; satellite bus → space pool
2
What's the certification or clearance gate? SC/DV → UK-national pool; ISO 15288 → MBSE pool; no clearance → 10x wider
3
Is the title "Engineer" or "Architect"? Architect = different, smaller, semi/software-dominant pool
4
Those three answers shrink a 74K-engineer LinkedIn firehose to a 2–5K real pool — which is where sourcing actually happens
Click any role below and the talent market snapshot loads instantly — no typing, no sign-up, no wait. We've pre-cached the results so the page opens with pool size, company list, and industry breakdown already rendered.
