Deep Tech Talent Signal • Issue #010

Two Unicorns,
One Craft

Two European unicorns posted the same craft under different titles last week. The job title is the wrong unit of measurement — the craft is.

2 roles reviewed • 2 European unicorns hiring in the UK • 26 May 2026
4 min read
→ Same craft, different titles, 88× different visible pool. Jump to the 11 pre-loaded market snapshots →

Last week we reviewed 2 deep-tech roles at 2 European unicorns hiring in the UK — and both are senior software engineers who write code at the silicon boundary. STARK (German HQ in Berlin, UK engineering office in Swindon) closed a Series C at $1B+ valuation in February for autonomous-flight defence drones. Fractile (UK, London + Bristol) closed a $220M Series B at $1B post-money in May for AI inference silicon. Same career profile. Two completely different industries. Two completely different job titles.

The visible market reflects the title, not the work. STARK posted Senior Embedded Software Engineer — one of the most common deep-tech titles: 67,594 engineers across 121 companies. Fractile posted Senior Systems Software Engineer — almost no one uses that title in this context: the literal pool is 763 engineers across 7 companies. Same craft. Different title. 88× different visible pool.

Two unicorns. One craft. The job title is the wrong unit of measurement — the craft is. Sourcing only the title the company posted gives you a fraction of the addressable pool.

If you’re sourcing either role this quarter, your candidate set lives across at least 3 titles — Embedded Software Engineer, Systems Software Engineer, and Linux Kernel Engineer. Search across them, dedupe, then brief the hiring manager on the combined number — not the headline of whichever title was typed first.

Software for autonomous flight · defence drones
STARK — Senior Embedded Software Engineer
Swindon, UK (UK Security Clearance eligibility required)
Yocto-based custom Linux distribution for autonomous flight platforms — MIPI camera + sensor drivers + cross-compilation toolchains. STARK reached unicorn status Feb 2026 on a €2.4B Bundeswehr framework deal — the Virtus loitering munition for a German brigade in Lithuania by end-2026. German HQ in Berlin, Munich production, UK engineering office in Swindon.
67,594
Embedded SWE pool
121
companies
Software for AI inference · AI silicon
Fractile — Senior Systems Software Engineer
London / Bristol, UK (3 days office, 2 days WFH)
Control chain for AI inference racks — bare-metal, RTOS, embedded Linux, management controllers between chip and OS. $220M Series B at $1B post-money, May 2026, with Anthropic in early talks to buy Fractile’s chips for Claude inference. C / Rust + Zephyr + Embedded Linux. London, Bristol, San Francisco, Taipei.
763
Systems SWE pool
7
companies
Sources: STARK Series C and Bundeswehr deal — Financial Times, Reuters, Sifted (Feb 2026). Fractile $220M Series B — Tech.eu primary, Sifted, Fractile official announcement (13 May 2026). Pool counts — Trutalent market_lookup_cache (25 May 2026 read).
Embedded Linux — the base layer for both
Appeared in 2 of 2 roles. STARK runs Yocto-based custom distributions for autonomous flight; Fractile builds management controllers on embedded Linux for AI inference racks.
Sourcing tactic: prioritise candidates with custom-distribution experience (Yocto, Buildroot) over generic Linux familiarity — that’s the differentiator between “Linux user” and “kernel + driver engineer”.
Bare-metal + RTOS — the hardware-software boundary
Appeared in 2 of 2 (Fractile explicit; STARK implicit in mission-critical flight code). This is where the work actually happens at the silicon boundary — not in application code.
Sourcing tactic: Zephyr or FreeRTOS commits on GitHub are a stronger signal than “RTOS experience” on a CV.
C / C++ / Rust — Rust as the second language
STARK runs C/C++ (17/20/23) + driver development; Fractile runs C and Rust together. The systems-software tier of UK deep tech is moving toward Rust as a second language alongside C/C++.
Sourcing tactic: the C + Rust combination is the most durable filter for forward-looking semiconductor and defence hires — it captures engineers who’ll still be productive in 5 years.
UK Security Clearance — the asymmetry
STARK requires SC eligibility; Fractile is open. The cleared candidate pool narrows STARK’s addressable count by ~75%, but cleared engineers move slower (3–6 month notice periods).
Sourcing tactic: start with the cleared pool first for STARK; the rest of the cross-title pool is the next-quarter conversation.
Watch this space — hardware/software co-design
Both roles emphasise close collaboration with hardware teams (STARK explicit on MIPI camera + sensor driver work; Fractile explicit on “close collaboration with hardware”). The defining filter going forward: engineers who can read schematics, debug at JTAG, and write production firmware.
Sourcing tactic: the cross-discipline person is becoming the bottleneck for every silicon-adjacent role. Tag them now, before the next quarter’s reqs.
Build the cross-title shortlist
before you write the brief

When two unicorns post the same craft under different titles, your candidate map needs to bracket the work — not the title. STARK’s Embedded SWE and Fractile’s Systems SWE are 95% the same shortlist; the remaining 5% is industry experience (drones vs AI silicon) and clearance posture.

This week’s data shows the spread concretely: the literal “Embedded Software Engineer” search returns 67,594 engineers across 121 companies. “Systems Software Engineer” returns 763 across 7. Same engineers, different titles. The same engineer appears in 2–3 of these buckets simultaneously when you cross-reference by Git history + custom-Linux experience + RTOS commits.

The 3-title cross-search routine
1
Open three snapshots in parallel. Embedded Software Engineer, Systems Software Engineer, Linux Kernel Engineer. The pool sizes alone tell you which title the wider market actually uses — and which one the company posted because it’s how they think internally.
2
Dedupe by candidate, not by title. The same engineer often appears under all three labels at different points in their career. Filter by Git history (Yocto, Zephyr, FreeRTOS), then count the union, not the sum.
3
Brief the hiring manager on the combined pool. “100–200 viable engineers across three titles” lands very differently than “763 in the literal title.” The combined number is the one that makes the calendar realistic for the search.
4
Layer the asymmetric filter last. Clearance for defence, on-site cadence for AI silicon, Rust experience for forward-looking semis. The asymmetric filter is what separates the two companies’ final shortlists — not the title they posted.
Run all three lookups in parallel See the snapshots →

Click any role below and the snapshot loads instantly — pool size, companies, industry breakdown, all rendered. No typing, no sign-up, no wait.

Role not listed? Request a mapping. Request a mapping →
Don’t search. Open.
11 deep-tech roles pre-loaded with pool size, company list, and industry breakdown. Open a snapshot, brief the hiring manager, run the search the same hour.
Open a market snapshot →
377K+ engineers • 837+ companies • 19 engineering disciplines