What does a Forward Deployed Engineer do?
An FDE takes one narrow use case from a vague idea to a working AI feature inside the customer's product, end to end, and owns every step in between. The deliverable is code in the customer's repository.
A typical engagement runs through:
- Scoping. Turn "we should add AI" into one workflow with a named user, a clear input, and a clear output.
- Architecture and UX. Decide where the workflow lives in the product and how a person actually triggers and reviews it.
- Prompt and context design. Build the model interaction, including the system prompt, the retrieved context, and the guardrails.
- Data integration. Connect the workflow to the customer's real data and systems, often through the Model Context Protocol.
- Implementation. Write production code in the customer's repository, with edge cases, fallbacks, error states, and logging.
- Evaluation. Ship a written rubric that defines what good output looks like and how the team scores it over time.
- Handoff. Hand the team code they can maintain, plus the rubric and a short playbook, so the workflow survives without the engineer.
The output is code in the customer's repo. Not a dashboard. Not a report. Not a Loom.
Why is it called "forward deployed"?
The phrase is military language. Forward deployed units are stationed at the edge, close to the situation, with the autonomy to act without calling headquarters first. Applied to engineers, it means the same thing: you work inside the customer's organization, and you decide on the spot.
Palantir made the term a job. It built its business on engineers who deploy into a customer's organization and deliver outcomes inside that customer's systems. The model spread because it solved a specific failure: software that works in a demo and dies in the customer's real environment.
In May 2026 the term went mainstream. OpenAI and Anthropic each launched a deployment subsidiary within a day of each other, both using the title Forward Deployed Engineer, both aimed at getting frontier models into enterprise products rather than selling API access and hoping. The AI in some job titles marks the shift: the capability being deployed is no longer just software, it is an AI workflow.
What does a Forward Deployed Engineer earn?
The median FDE total package is $238,000, on a median base salary of $174,000, per public compensation data from 2026. Senior packages at the frontier labs go above $500,000.
| Compensation measure | Figure (2026) |
|---|---|
| Median base salary | $174,000 |
| Median total package | $238,000 |
| Senior frontier-lab packages | Above $500,000 |
Figures are from public compensation data collected in 2026. Individual offers vary with seniority, location, and equity.
FDE titles by company
Almost nobody posts this job under one name. The same customer-embedded, ship-into-production role is hired under different titles at different companies, so searching for one string misses most of the market.
| Company | What they call the role |
|---|---|
| Palantir | Echo and Delta, the two halves of its forward deployed practice |
| OpenAI | Forward Deployed Engineer |
| Anthropic | Applied AI |
| Sierra | Agent Engineer |
| Harvey | Implementation Engineer |
| Decagon | Agent builder / agent SWE |
Echo and Delta are defined in the glossary, and the split between them is a core chapter of the book.
How is an FDE different from a solutions engineer?
A solutions engineer works for the vendor and is measured on the sale; an FDE works on the customer's outcome and is measured on what ships. Both are technical and customer-facing, which is why the two roles are so often confused.
| Role | What they ship | Where the work lives | Optimizes for |
|---|---|---|---|
| Forward Deployed AI Engineer | A working AI workflow built into the customer's product | The customer's codebase and product | A shipped outcome the customer's team can run and maintain |
| Solutions engineer | Integrations, demos, and configuration of a vendor's product | The boundary between vendor and customer | Closing and onboarding the customer onto the vendor's platform |
| ML engineer | Models, training pipelines, and inference infrastructure | The model and data platform | Model performance, scale, and reliability |
| AI consultant | Strategy, roadmaps, and recommendations | Documents and meetings | Advice and direction, with execution left to others |
For a side-by-side that goes deeper on the closest comparison, see Forward Deployed AI Engineer vs solutions engineer.
Why did the FDE role explode in 2026?
Because enterprises learned that buying AI is not the same as deploying it. An MIT study cited in the book found that 95% of enterprise AI pilots produce no measurable return. The FDE is the industry's answer to that gap, and in 2026 the money followed.
- May 4, 2026. OpenAI launched a $10 billion deployment subsidiary and Anthropic a $1.5 billion one, on the same day, both hiring under the title Forward Deployed Engineer.
- May 16, 2026. Business Insider reported that Indeed postings for the role grew from 643 in April 2025 to 5,330 in April 2026, more than 700% in a year. The same month, the title returned 55,000+ LinkedIn results in the US and over 100 postings on the YC job board.
- June 30, 2026. AWS announced a $1 billion FDE program.
- July 2, 2026. Microsoft launched Frontier: $2.5 billion and 6,000 embedded experts.
- July 30, 2026. TechCrunch reported a C&T study projecting demand for FDEs to surge 2,100% by the end of 2026, against an estimated 2,000 qualified FDEs in total.
What skills does the role require?
Less model research, more product engineering and judgment. The hard part is usually deciding what to build and proving it works, not calling the API.
- Product engineering. Shipping real features into a real codebase, with the discipline that production demands.
- Prompt and context design. Getting reliable output from frontier models, including retrieval and structured context.
- Data integration. Connecting models to messy customer systems and APIs, often via MCP.
- Evaluation. Defining what good output is and scoring it, so quality is measured rather than asserted.
- Customer-facing judgment. Scoping under pressure, saying no to the wrong workflow, and protecting a fixed timeline.
How do you become a Forward Deployed Engineer?
Most people who do this well arrive from product engineering, solutions or consulting, or a founder background, then prove they can ship one narrow AI workflow end to end.
The fastest credible path is to build and ship a real workflow, write the evaluation rubric for it, and be able to walk someone through the code. For a step-by-step version, see how to become a Forward Deployed AI Engineer.
Forward Deployed AI Engineering for founder-led B2B SaaS
The enterprise version of this role is built for Fortune 500 procurement. The same work, sized for a 5-to-50-person founder-led SaaS team, is the AI Feature Sprint: one narrow AI workflow shipped into the product in 10 business days, fixed scope and fixed price.
That's the work I do. Most patterns I ship into a customer's codebase have already run in Vectig, my own AI-native product and live R&D lab. If you want to see the engagement, start with the AI Feature Sprint or a Discovery Day.
The book
A working guide to the role
Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software is the long-form version of this page: what the role is, where it came from, how it is practiced, and how to do it well. Written from inside the work, in the months after OpenAI and Anthropic put the title on the map. For the wider reading list around the role, see the best Forward Deployed Engineer books.
About the author
Frequently asked questions
Do Forward Deployed Engineers write production code?
Yes. The defining deliverable is working code in the customer's repository, with edge cases, fallbacks, error states, logging, and a handoff the customer's team can maintain. Demos and decks are what the role exists to replace.
Is Forward Deployed Engineer a good career in 2026?
The demand data is unusually one-sided. Indeed postings grew more than 700% in a year per Business Insider, TechCrunch reports projected demand growth of 2,100% by the end of 2026 against an estimated 2,000 qualified FDEs, and the median package is $238,000. The constraint is proving you can do the work, not finding openings.
Do you need a machine learning background to become an FDE?
No. The role applies existing models rather than training them. The core skills are product engineering, prompt and context design, data integration, evaluation, and customer-facing judgment. A research or MLOps background helps in some engagements but is not the entry requirement.
How much travel does the role involve?
More than most software roles. Anthropic's listing puts travel at 25 percent. OpenAI expects its FDEs on customer sites a few days a week during an engagement. At Palantir, Nabeel Qureshi describes four to five days a week at the customer's office as the high end; two to three is more typical.
Is a Forward Deployed Engineer the same as an applied AI engineer?
Functionally, yes. Applied AI is Anthropic's title for the FDE-shaped role, the same way Sierra says Agent Engineer and Harvey says Implementation Engineer. The employer's label changes; the work of shipping AI into a customer's production systems does not.
Sources
- TechCrunch, "Forward deployed engineers are the AI industry's latest talent obsession," July 30, 2026. techcrunch.com
- Business Insider, reporting on Indeed job-posting data for Forward Deployed Engineer roles, May 16, 2026.
- Public compensation data for Forward Deployed Engineer roles, 2026.
- MIT study on enterprise AI pilot outcomes, as cited in Forward Deployed AI Engineering.
- Bob McGrew on the Forward Deployed Engineer role. McGrew spent 11 years at Palantir and later led research at OpenAI.
- Anthropic and OpenAI job listings for the role (travel expectations).
- Nabeel Qureshi on Palantir's forward deployed model, Lenny's Newsletter, May 2025. lennysnewsletter.com
Newsletter
Notes from the edge of building
One email a week on Forward Deployed AI Engineering, building AI-native SaaS solo with Claude Code, and the slow weeks in between. Subscribing also gets you the first two chapters of both my books.
Free. Unsubscribe in one click.