What Is a Forward Deployed Engineer?
A Forward Deployed Engineer (FDE) is a software engineer who works inside one client's real environment and closes the gap between what a product does out of the box and what that client actually needs.
The Delta
Palantir coined the role. The clearest way to understand it is a single idea, the Delta: the gap between generic software and one specific client's reality. An ordinary software engineer builds for millions of anonymous users inside a controlled cloud, optimizing for scale. An FDE builds for one named, high-stakes stakeholder, often inside that client's messy, legacy-heavy infrastructure, optimizing for speed to value before the budget gets pulled.
What an FDE does in a typical week
- Sits with the people who will use the system and maps the workflow nobody wrote down.
- Prototypes a useful slice fast, often against messy, half-documented data.
- Writes production integration code: connectors, pipelines, agents, whatever closes the gap.
- Makes judgment calls about scope, and says no to the wrong work.
- Carries what the client needed back to the product team.
Two kinds of FDE roles today
At AI-native tools companies, FDE work usually means closing the Delta with a narrow agent workflow or a missing integration. At enterprise platforms (the Palantir archetype), it adds real data engineering against decades-old systems, cloud architecture at client scale, and structured business consulting on top of the AI work.
Skills that matter
- Solid backend engineering: Python, APIs, git, SQL.
- How LLMs work, retrieval (RAG), and building agents, by hand before frameworks.
- Evaluation, observability, and guardrails: proving a system is reliable and safe.
- Deployment into environments you do not control.
- Client communication: discovery, scoping, and explaining trade-offs to non-engineers.
Ready for the path? Read how to become a Forward Deployed Engineer, see the 16-week roadmap, or compare FDE vs software engineer.
Frequently asked questions
Is a Forward Deployed Engineer the same as a solutions engineer?
No. A solutions engineer mostly supports pre-sales: demos and technical questions before a deal closes. A Forward Deployed Engineer writes and ships production code inside the client's environment and stays until the system actually works there.
Do Forward Deployed Engineers write code?
Yes, a lot of it. Roughly half is integration and glue code, and the other half is judgment calls about scope, which is what separates the role from pure implementation.
Where did the title come from?
Palantir created the role for customers whose problems and data could not be handled from a distant product team, so it sent engineers to the data. AI companies have widely adopted the model since.
Zero to FDE is a 90-day roadmap that takes AIML graduates to Forward Deployed Engineer (FDE) roles: twelve core weeks plus an optional four-week enterprise track, with one real deliverable every week.
Start the 90-day roadmap