What Thirty Recruiter Messages Say About the FDE Market
A season of inbound outreach, read as a dataset rather than a compliment
Since spring, around thirty recruiter messages about Forward Deployed Engineer roles have landed in my LinkedIn inbox. Most of them arrived in the past few weeks, and the pace is still picking up.
Before anything else, the obvious caveat. This volume has little to do with me being exceptional and a lot to do with me being findable. Between the FDE role and running FDE Hub, my profile sits near the top of exactly the searches recruiters are now running daily. Rory O’Brien observed earlier this year that FDEs are getting spammed while recruiters are “chasing a moving target of what the ideal candidate even is”. My inbox is simply where that observation became measurable.
So rather than treating the messages as noise, I started treating them as data. Thirty messages is a small sample, and a skewed one, since it over-represents whoever runs outbound at volume. But it is also something you cannot get from job boards or press releases: a direct reading of what the market thinks it is buying when it says Forward Deployed Engineer.
Here is what it revealed.
The market has a template, and the template is wrong
Two of the messages could have been written by the same person. Different senders, different companies, no connection between them, and nearly identical text: strong Python, SQL, data pipelines, customer-facing engineering. A third asked for deep expertise in Python, SQL, data engineering and system integrations, combining technical problem-solving with direct customer impact.
Somewhere in the past year, a default FDE job spec got written, and the market copied it. The trouble is what the template describes. Python plus SQL plus pipelines plus customer-facing is a data engineer who attends meetings.
What the template never mentions is the part of the job that determines whether a deployment survives. Nothing about discovery, or scoping, or sitting with the operators whose workarounds define how the process actually runs. Nothing about earning the trust to move a system from advisory mode to autonomy. Nothing about owning an outcome rather than a backlog. The skills in the template are real prerequisites, but they are the entry ticket, not the job. A market hiring against this spec will fill seats and then wonder why the deployments stall.
The title points in both directions at once
The stranger finding is that the label has come loose from the work entirely, and it drifts both ways.
One message pitched a Forward Deployed Engineer role that, on inspection, involved no customer at all. The job was building an internal AI platform: backend, cloud, Kubernetes, enabling other teams to deploy. Worthwhile work, and roughly the opposite of forward deployment. Someone had stapled the market’s hottest title onto an infrastructure requisition, presumably because it improves response rates.
Meanwhile, the most accurate descriptions of FDE work in the entire pile arrived under different names. One healthcare AI role, titled AI Product Engineer, was described as owning the whole thing: talk to users, write the code, ship it, no tickets, no story points. Another, titled Staff AI Engineer at a logistics scale-up, was end-to-end ownership of production agents inside a messy real-world domain. Both are closer to the craft this newsletter covers than most of the messages that used the actual words. One sender split the difference and hedged the title with a slash.
The purest specimen was an FDE role where Python was, quoting loosely, helpful but definitely not essential. To be precise about what is wrong there: Python does not define this role, engineering does. Being able to build is the floor everything else stands on, and fluency in a language like Python is the cheapest reliable signal of it. A sender can reasonably swap the language. A sender who declares it optional, without asking for any other evidence of engineering ability, has waived the floor itself. At that point there is no role behind the message, only a vacancy.
The practical lesson for anyone fielding these messages is to read each one twice. Once for the title, which tells you what the market currently rewards, and once for the work, which tells you what you would actually be doing. In this sample the two agreed less than half the time.
An industry has formed around the title
The messages themselves are only half the dataset. The senders are the other half, and they show a recruiting industry rapidly restructuring itself around a single job title.
One headhunter now describes himself, in his signature, as a Forward Deployed Engineering headhunter, with regional specialisation across Europe, the Gulf and Singapore. His message contained no role at all. He wanted to understand my motivations for a next move before any specific mandate entered the conversation. That is talent pooling: building inventory ahead of demand, which only makes sense if you expect the demand to keep coming.
A managing director at an executive search firm reached out about a leadership search, and the interesting part was what she wanted. Not my CV. My network. Visible practitioners are becoming sourcing infrastructure, a routing layer the search industry queries when it cannot find supply on its own.
Further down the chain sit the sourcers: research consultants at boutique agencies running outbound volume on roles they did not scope and will not close. One of these roles did not appear anywhere on the client’s own careers page, which means the person most distant from the work was the only person publicly attached to it.
And then the scene that summarises the whole season. A recruiter messaged me about a role building an agentic AI platform for enterprises. When I asked for details about the company and the role, the reply directed me to a five-minute AI prescreening call, with a link and a privacy notice. A human recruiter, hiring a human to deploy AI agents, delegating the first human conversation to an AI agent. Whatever your position on AI in recruiting, the loop has visibly closed.
Across all of this, one pattern held with almost no exceptions: message quality degraded with every layer between the sender and the actual work. The template spam came from the outermost layer. The single best message in the pile came from an in-house sourcer at a company standing up a new AI unit, and it described real forward-deployed work in specific terms: owning the customer engagement from adoption readiness through implementation, first hire on a founding team, a path into leadership. Proof that the role is perfectly describable, provided the person describing it sits close enough to it.
The inbox does not look like the headlines
The final finding is about whose demand this actually is.
The FDE story of the past two months has been told in billions: captive deployment organisations, thousands of embedded engineers, hiring announced by press release. Going by the headlines, you would expect an inbox full of hyperscalers.
The count in mine: one. A single message from one of the giants, describing an embedded builder bridging the gap between prototypes and production, language lifted almost directly from its public job descriptions. Accurate, credible, and alone.
The ratio says less about any individual inbox than about how these two markets hire. A handful of giants against hundreds of startups will always lose on volume. The giants also recruit through their own channels, in-house teams, referrals and hiring managers who are active on LinkedIn themselves, while the startup demand arrives through agencies and sourcers running outbound at scale. What fills an inbox is not the biggest demand. It is the most intermediated demand.
Everything else came from a different market entirely. European seed and Series A companies. A fintech hiring through an agency platform. A startup a few months past its seed round, whose recruiter presented its handful of early contracts as a sweeping global enterprise footprint. Several companies hiring their first FDE ever, in one case explicitly hire number one of a founding unit.
So there are two demands running in parallel. The headline demand is concentrated, capitalised and slow, hiring in the thousands through its own channels. The inbox demand is fragmented, small and immediate: companies buying their first forward deployed engineer, often without a settled idea of what one is, frequently through intermediaries who understand the role even less. The first market sets the narrative. The second is where most FDEs will actually end up working, and it is far messier than the narrative suggests.
Who teaches the market?
Thirty messages, one conclusion: the market has learned to say the words faster than it has learned what they mean. The demand is real at every layer, from the giants to the seed rounds. The definition has not kept up, and every layer of intermediation makes it worse.
That gap will close eventually, the way it closed for titles like site reliability engineer and product manager before this one. The open question is who does the closing. The companies, through expensive mis-hires that teach them what the role is not. The recruiters, as the specialists among them learn to tell forward deployment from data engineering with meetings. Or the practitioners, by being loud enough about what the work actually is that the template eventually gets rewritten.
My inbox suggests nobody has claimed the job yet.