The full answer
A forward deployed engineer (FDE) works inside a customer's world to make the product solve that customer's real problem, end to end: understanding the workflow, connecting the product to their data and systems, building what is missing, and staying until it delivers results in production. At AI companies the product is usually a model or an agent platform, so the FDE turns "we have access to a powerful model" into "our claims team closes cases 30% faster", and feeds what they learn back to the product team.
Where the role comes from
Palantir made it famous. Its blog describes two big engineering roles: software engineers ("Devs") who build one capability used by many customers, and forward deployed software engineers ("Deltas") who deliver many capabilities for one customer, measured by the impact on that customer's goals. AI labs and AI startups adopted the model because their products only create value once fitted to each customer's data, workflows and risks.
What the work looks like
- Discovery: sit with the people doing the work, find the costly, repetitive or slow steps, and pick a problem worth solving.
- Scoping: define a pilot with a measurable target and an evaluation set.
- Building: prompts, retrieval, tools and integrations; often a working prototype within days.
- Deploying: security reviews, access to data, connecting to real systems, monitoring.
- Driving adoption: training users, fixing what gets in their way, showing results to sponsors.
- Feeding back: turning repeated custom work into product features, and reporting gaps and bugs.
How it differs
| Role | Focus | Success means |
|---|---|---|
| Software engineer | Product features for all customers | Features shipped, quality, scale |
| Solutions or sales engineer | Showing the product can fit, before the sale | Deals won |
| Forward deployed engineer | Making it work in one customer's production, after (or during) the sale | Measured customer outcome, renewal and expansion |
| Consultant | Advice and delivery for a client | Delivered project |
An FDE writes production-quality code like a software engineer, talks to executives and end users like a solutions engineer, and owns outcomes. Unlike a consultant, they represent a product and push the lessons back into it.
What interviews test
- Technical depth: LLM apps, RAG, agents, integration, data, debugging.
- Customer skills: discovery, scoping, managing expectations, explaining trade-offs to non-engineers.
- Judgement: when to build something custom, when to say no, when to escalate to the product team.
A good one-liner: "I own the outcome at the customer, not just the code, and I make the product better with what I learn there."
Last updated 16 October 2026
Sources