A Forward Deployed Engineer (FDE) is a software engineer who works directly with a customer, often inside the customer's own environment, to turn a product into a working deployment that solves that customer's problem. FDEs scope the problem, write the integration code, and own the result in production.
What does a Forward Deployed Engineer do?
Most FDE work falls into five loops that repeat through an engagement:
- Discovery. Find the workflow that hurts, who owns it, and what a wrong answer costs, before any code.
- Scoping. Agree the smallest integration that proves value, with a success number the customer signs.
- Integration. Connect the product to the customer's systems: APIs, databases, identity, inside their network.
- AI delivery. Ship LLM features such as retrieval (RAG), agents and tool use, and prove them with evals.
- Handover and feedback. Leave runbooks and dashboards the customer can run alone, and take repeated needs back to the product team.
OpenAI describes its FDEs as leading complex end-to-end deployments of frontier models alongside its most strategic customers (OpenAI careers).
What skills do FDE jobs ask for?
An analysis of 1,000 Forward Deployed Engineer job postings (Revealera data, January to October 2025) found these technologies most often (Bloomberry):
| Skill | Share of postings |
|---|---|
| Python | 66% |
| AI agents | 35% |
| TypeScript | 35% |
| AWS | 32% |
| LLM experience | 31% |
| GCP | 22% |
| Azure | 18% |
| Kubernetes | 14% |
| RAG | 12% |
The same analysis found that 55% of postings name working directly with customers as a core responsibility, 37% building and deploying AI systems, and 32% integrating systems and APIs. Among postings that state experience, 60% ask for three to five years.
Forward Deployed Engineer vs software engineer
Palantir, which popularised the role, puts the difference simply: a product engineer builds one capability for many customers; a forward deployed engineer delivers many capabilities for one customer (Palantir, Dev versus Delta).
- Starting point: a software engineer usually starts from a ticket; an FDE often starts from a vague request and has to find the real problem.
- Environment: FDEs work inside someone else's cloud, network and security rules.
- Success: measured by the customer's outcome, not only by the code shipped.
What is the FDE interview like?
Alongside coding, many FDE loops test decomposition: you get a vague, real-world problem and break it into parts out loud, usually with little code. Prep guides and candidate reports describe Palantir's version as a 60-minute round (Exponent). Practise asking about the workflow, the owner and the cost of failure before proposing a design.
How to become a Forward Deployed Engineer
Most FDEs come from software engineering. The path adds field skills on top:
- Discovery and scoping: find the pain and agree a success number.
- Production integrations: timeouts, rate limits, safe retries and searchable logs.
- LLM delivery: model routing, RAG, agents and evals.
- Enterprise boundaries: identity (OAuth, SSO), MCP servers and AI security.
- Communication: lead with the answer for executives.
FDE Forge teaches this as a 12-week roadmap of 3-minute lessons, each building one part of a real customer project.
Frequently asked questions
What is a Forward Deployed Engineer?
A Forward Deployed Engineer (FDE) is a software engineer who works directly with a customer, often inside the customer's own environment, to turn a product into a working deployment that solves that customer's problem. FDEs scope the problem, write the integration code, and own the result in production.
What does a Forward Deployed Engineer do day to day?
FDEs run discovery with customer stakeholders, build integrations and data pipelines against the customer's systems, deploy AI features such as RAG and agents, measure them with evals, and feed recurring needs back to the product team.
What is the difference between a Forward Deployed Engineer and a software engineer?
A product software engineer builds one capability for many customers. A Forward Deployed Engineer combines many capabilities for one customer. Palantir, which popularised the role, describes it as one capability, many customers versus one customer, many capabilities.
What skills do Forward Deployed Engineer jobs ask for?
In an analysis of 1,000 FDE job postings, 66% asked for Python, 35% for AI agents, 35% for TypeScript, 32% for AWS and 31% for LLM experience, and 55% named working directly with customers as a core responsibility.
How do I become a Forward Deployed Engineer?
Start from software engineering, then add the field skills: customer discovery and scoping, production-grade integrations, LLM features with RAG, agents and evals, enterprise identity and security, and clear executive communication. Practise on realistic customer projects and prepare for decomposition interviews.
Try the first lesson: three minutes, no sign-up.