How Many Companies Hire Forward Deployed Engineers?
We track 101 companies hiring forward deployed engineers and adjacent embedded roles, 74 of them for an explicitly forward deployed title. Here is the count, how we classify it, and what the registry does and does not prove.
BY ARJUN MEHTA · FDEINTERVIEWS EDITORIAL · UPDATED SEPTEMBER 12, 2026 · 6 MIN READ
PRACTICE THIS:Every company we track, with its loop ·The must-know FDE questions ·Customer and behavioral rounds ·System design under customer constraints
We track 101 companies hiring forward deployed engineers or an adjacent embedded role, as of September 2026. Of those, 74 hire for an explicitly forward deployed title: Forward Deployed Engineer, Forward Deployed Software Engineer, or Forward Deployed AI Engineer. The other 27 hire for the same embedded customer work under a machine learning engineer or applied AI engineer title.
That is a count of our registry, not a census of the market. The distinction matters and we keep it visible throughout.
The breakdown
| Role scope | Companies |
|---|---|
| Explicitly forward deployed title | 74 |
| Machine learning engineer, embedded | 16 |
| Applied AI engineer, embedded | 11 |
| Total tracked | 101 |
Every one of the 101 has an interview-process entry in our research, though the depth of that entry varies a great deal, which is the next section.
How much we actually know about each loop
A company being in the registry does not mean its interview process is public. We label every entry with a confidence level so that a reader can tell the difference between a loop we can describe stage by stage and one where we know the role exists and little else.
| What we hold | Companies |
|---|---|
| Documented process, stage by stage | 31 |
| Partial, some stages described | 14 |
| Limited, role confirmed, process thin | 56 |
The 56 in the last row are not a research failure. Most companies never publish their interview loop, and we would rather say so than pad an entry with a plausible-sounding sequence. If you are preparing for one of those, the forward deployed engineer interview process guide describes the shape the role's loop takes almost everywhere, which is a better starting point than a guess dressed up as research.
What counts, and what does not
We add a company when we can point at evidence that it hires for this work: a job posting, an engineering blog post, a public description of the loop, or a role description that names embedded customer deployment as the job. We do not add a company because a recruiter mentioned it or because the role seems likely.
Three groups are therefore missing by construction. Companies hiring quietly or through agencies. Companies using an internal title we have not mapped to this pattern. And companies whose forward deployed work is done by a consulting partner rather than by employees. Read the number as a floor.
Why the title undercounts the market
The most practical finding from building this registry is that filtering a job board on the exact phrase will hide most of your options. Twenty-seven of our 101 companies run what is unmistakably a forward deployed loop under a different header.
The reliable signal is in the description rather than the title. If a posting talks about embedding with customer teams, owning a deployment end to end, or turning a proof of concept into something that survives contact with a customer's systems, the interview will test scoping ambiguous problems, messy data, and stakeholder communication, whatever the role is called. That is the same loop, and the same preparation works.
Where the role concentrates
Palantir originated the pattern and still runs the largest and most structured Forward Deployed Software Engineer organization, which is why its loop is the most documented one we hold. See the Palantir interview page for the stage-by-stage breakdown.
Beyond it, the consistent hirers in our registry are the AI labs and the data platforms: OpenAI, Anthropic, Scale AI, Databricks and Glean. The more interesting movement is outside that group. The title now appears at companies that sell no platform at all, in defense technology, in developer tooling, and inside the applied AI arms of large incumbents. That spread is the strongest available evidence that this is a pattern being adopted rather than one company's job title.
How to use this number
If you are a candidate, the useful takeaway is not 101. It is that 74 companies advertise the title and another 27 run the loop without it, so your search should be built around the work rather than the words. Start with the full company list, then work the rounds that decide these loops in the must-know questions.
If you are citing this figure, please attribute it as companies tracked by FDEInterviews.com as of September 2026, rather than as a market total. We would rather be quoted accurately than quoted often.
Method
Counts are computed directly from our company registry and interview-process research, not typed in by hand, and a check in our build fails if a published figure drifts from the underlying data. Confidence labels are assigned per company: documented means we can describe the loop stage by stage from public material, partial means some stages are described, limited means the role is confirmed and the process is not public. Figures are current as of 12 September 2026.
Turn it into offers. Work the real questions and concepts this maps to:
FAQ
We track 101 companies hiring forward deployed engineers or an adjacent embedded role, as of September 2026. Of those, 74 hire for an explicitly forward deployed title such as Forward Deployed Engineer, Forward Deployed Software Engineer or Forward Deployed AI Engineer. The remaining 27 hire for roles that do the same embedded customer work under a machine learning engineer or applied AI engineer title.
Discussion (5)
The core against adjacent split is the useful part here. I have interviewed at three places that advertised machine learning engineer and the loop was pure FDE: a customer scenario, a messy data exercise, and a stakeholder conversation. If you filter job boards on the exact title you will miss most of the market.
That is exactly why the registry carries both. Filtering on the literal string is the single most common way candidates undercount their options. The tell is in the job description rather than the title: if it mentions customers, deployments or embedding with a client team, the loop will look forward deployed whatever the header says.
Reader question: does a company appearing in the registry mean they are hiring right now, or that they have hired for this at some point?
At some point, and that is a deliberate choice. Postings open and close weekly, so a live-vacancy list would be stale within days and would tell you nothing about how to prepare. The registry answers a slower question, which is where this role exists and what the loop looks like when it runs.
Worth saying out loud that the 56 companies with limited process detail are not a gap in the research so much as a reflection of reality. Most companies simply do not publish their loop. Treating absence of detail as evidence of an easy loop would be a mistake.