The engineer who goes to where the mess is.
A forward deployed engineer embeds inside a customer's organisation, writes production code against their real data, and is measured on whether that one customer actually gets the outcome — not on whether a feature shipped.
Four trackers counted the surge. They disagree on the number, not the direction.
Every published growth figure for FDE hiring comes from a different source, a different window and a different definition of the title. Quoting any single one as the number is how this field's writing loses credibility. Here they all are.
The institutional signals, in order
a16z's Joe Schmidt called it "the hottest job in startups" in Trading Margin for Moat (4 June 2025), noting OpenAI alone had 22 open FDE and solutions reqs at the time. Google Trends shows a flat decade then a hard spike in August 2025.
Google Cloud's Thomas Kurian began ramping FDE hiring and shortening the loop. Salesforce, EY, PwC, McKinsey and Accenture followed. New York overtook San Francisco as the largest US FDE hub.
In May 2026 OpenAI spun the function into its own company. DeployCo launched with $4B of investment at a $10B pre-money valuation, 19 investors led by TPG with a guaranteed minimum 17.5% return, and immediately acquired London consultancy Tomoro and its ~150 forward deployed engineers and deployment specialists.
DissentAnaplan's CEO calls FDE an effective sales tactic but a poor long-term strategy. The Pragmatic Engineer notes the role may stay unattractive to senior product engineers. Both views belong in any honest guide.
Is this a real FDE role, or a sales job wearing the title?
Because roughly a third of postings are mislabelled, the single most useful thing this guide can do is give you a functional test. Tick what the job description actually says — not what the title says — and watch which role it resolves to.
Role shape
The neighbours, and the exact line between them
Five roles sit next to this one and get confused with it constantly. Hover a row to compare across all of them.
The two-track model, and why it matters
Palantir split the work in two. The Forward Deployed Software Engineer — internally "Delta" — writes the production code: data pipelines, ontology modelling, integrations. The Deployment Strategist — "Echo" — owns scoping, stakeholders and success metrics.
Databricks copied the structure and describes the strategist in its own careers pages as "the product manager for the customer's problem", with FDEs as the partners responsible for the how. Shyam Sankar is generally credited with making the model repeatable. For roughly its first decade Palantir employed more Deltas than product engineers.
The compounding test
What separates an FDE from a consultant is not the work in the room, it is what survives it. PostHog frames the difference as compounding: patterns from one engagement become reusable artefacts and product changes.
Palantir's own framing, from an FDSE on the engineering blog: a product engineer builds one capability for many customers; an FDSE enables many capabilities for a single customer, then feeds what they learned in the field back into the product. If nothing flows back, you are running professional services with a fashionable title.
Four flavours of the same title, wanting four different people
A Palantir FDSE and an Anthropic applied-AI FDE share a job title and almost nothing else in their week. Pick a flavour to see where the skill weight actually sits.
The roadmap: seventy-one skills, five stages, one route through
Not a reading list. Every skill names what to learn, what to build with it, and the artefact that proves you can do it — because these loops test whether you have shipped something to a real user, not whether you finished a course. Click any skill for the detail. Click the dot beside it to track where you are.
Progress
Interview-ready coverage
By branch
The capstone that replaces a CV
One flagship customer-facing system, built end to end and written up in public: discovery notes showing you found the real problem, an architecture decision record, integration reliability under a hostile API, an eval harness with documented failure modes, a live deployment with monitoring, and a case study written for a business reader. Then two mock interviews — one coding and debugging, one customer solution design — and a CV rewritten around ownership and measured outcomes rather than technologies used.
Four interview loops, stage by stage
These loops share a shape: a motivation screen that tests why this role, a practical build rather than a puzzle, an open customer scenario, and — at the labs — a judgement round. Click any stage to see what it is really testing.
What it pays, and which numbers to trust
A week in the field has three shapes
Roughly three quarters of the job is technical work inside somebody else's environment. The rest is the part nobody warns you about. Travel clusters at 25–50% — OpenAI postings cite up to 50%, Anthropic around 25% — but first-hand accounts include four days a week on one customer's site for a year.
The burnout here has a specific shape
It is not volume of work. It is context-switching between your own codebase and a customer's, while being your company's unflappable face for months, while accountable for adoption you do not fully control. The phrase that recurs in first-hand accounts: you can do everything right and still lose, because a stakeholder changed jobs. One FDE on Blind reported $220K total comp against $250–300K for software engineers at the same startup, with less defined levelling. Another called the function "an org smell" if the product needs bespoke work for every customer. Both criticisms are worth taking seriously before you optimise for this role.
Who becomes one, and what they become next
The exit paths are the strongest argument for the job. You spend two years watching how enterprises actually buy, fail and adopt — which is founder training that no product engineering role provides.
The Palantir Mafia is real, and it started in the field
Concept.vc documents over 100 companies founded by Palantir alumni. Anduril's co-founders came directly out of forward deployed roles: Trae Stephens spent 5.5 years as a forward deployed engineer, Matt Grimm 6 years 8 months. Anduril has since raised $3.8B at roughly a $30.5B valuation.
Others in the list: Barry McCardel (Hex), Nick Noone (Peregrine), Rebecca Egger (Little Otter). The pattern is consistent — people who spent years inside customers' problems left to build the product those customers actually needed.
The one exit that punishes you
Going back to pure product engineering is possible but harder than people expect. Field work rewards breadth, speed and judgement under ambiguity; it does not reward depth in one codebase. Two years of integration work against unfamiliar systems can read, on a product engineering loop, as technical atrophy.
The mitigation is boring and effective: keep one deep technical thread alive outside client work, and make sure something you built in the field shipped into the core product with your name on the commit.
Who hires forward deployed engineers
Filter by flavour and constraints. Where a company has not published a figure, this says so rather than guessing — an empty cell is more useful than an invented one.
Titles vary. Sierra calls it Agent Engineer, Anduril calls it Technical Operations Engineer, Databricks splits it into Deployment Strategist and FDE. Search on the work, not the word.
Building this into a hub, in four stages with exit gates
The gap in the market is not more content. Several FDE sites already exist — fde.academy, fdepulse, a10x, two GitHub roadmap repos, a community roadmap.sh entry, several Substacks. Almost all are either thin SEO pages or funnels for a paid course. The unclaimed position is the neutral, primary-sourced, comprehensive one.
Validate
Publish the single best free explainer on the web — what an FDE is, and how to tell a real posting from a relabelled sales role — plus email capture. Post to Hacker News, r/ExperiencedDevs and LinkedIn.
Anchor
Ship the interactive roadmap as an open-source repo plus hosted site. Fork the roadmap.sh Astro and Tailwind stack for the renderer — but write entirely original content, because their content licence forbids redistribution.
Depth
Per-company interview pages, a pay page with proper Levels.fyi attribution, and a company directory filterable by role shape, travel, clearance and remote policy. These are the highest-intent search pages in the niche.
Community and jobs
Discord or Slack, seeded with alumni AMAs, then a curated job board that filters out the pre-sales roles. Role-shape filtering is the feature, not a limitation.
What goes on the site
Stack and cost
Astro plus Tailwind, deployed to Vercel or Cloudflare Pages, is the fastest credible path because the interactive roadmap renderer and the community-contribution model already exist and are proven. Next.js is the alternative if the job board and pay tables become dynamic enough to need server rendering, paired with a headless CMS and React Flow for the roadmap.
An MVP is a few weekends on free tiers and near-zero hosting. The real cost is not the build — it is keeping salary, company and hiring data current in a field that changed three times in eighteen months.
Risks worth designing around
Staleness destroys trust fastest
DeployCo launched in May 2026 and reshaped the field in a month. Date-stamp every figure, automate the job and pay refreshes, and show your sourcing — a visibly maintained page beats a comprehensive stale one.
Trademarks and licences
Palantir, Foundry, OpenAI and Anthropic are trademarks — reference factually and never imply endorsement. Do not clone roadmap.sh's licensed content even if you fork the framework.
The definitional trap
A third of postings are mislabelled. A job board that indexes on title will fill with sales roles and lose the audience. Filter on role shape from day one.
You will not out-rank the labs on their own names
Win on neutrality and cross-company comparison instead — the thing no company careers page can offer.
Course-funnel drift
The credibility failure mode of every existing FDE site. Monetise late, via a job board and sponsorships, after the free content has earned trust.
Where this came from, and what to distrust
Primary sources
- Job postings: Palantir (FDSE), Anthropic (Applied AI FDE), OpenAI (FDE), Anduril (Technical Operations Engineer), Shield AI, Applied Intuition, Decagon, Sierra, Databricks, PostHog.
- Levels.fyi Palantir FDSE page (updated 23 June 2026) and the FDE title page (31 Aug 2026).
- OpenAI's DeployCo announcement, 11–12 May 2026, and Axios coverage of the raise and the Tomoro acquisition.
- a16z, Joe Schmidt, Trading Margin for Moat, 4 June 2025.
- MIT Project NANDA, The GenAI Divide: State of AI in Business 2025, July 2025.
- Business Insider's Palantir Mafia reporting and Concept.vc's alumni founder index.
- Palantir's engineering blog on the FDSE role; Databricks careers pages on the strategist and engineer split.
Treat these with suspicion
- Senior and principal pay figures. The $610K staff and $1.2M principal numbers are modelled from self-reported data where most of the value is private equity. They are not payroll.
- Growth percentages. 729%, 800%, 1,165% and "10x" come from four trackers over four windows with four definitions. Cite them as directional or not at all.
- Round-by-round interview detail. Much of it comes from crowd-sourced prep sites. The shape of each loop is well corroborated; specific questions are not guaranteed to be current.
- Anything titled "FDE". The title is applied inconsistently across the industry. The functional test in section B is more reliable than any posting's headline.