Introduction of FDE
In one sentence: Module 0 Is the map you read before anything else: what a Forward Deployed Engineer is accountable for, how the role differs from its neighbors, and which part of this handbook builds each capability the job needs.
What an FDE is
Section titled “What an FDE is”Lesson 1 defines the role; start with Forward Deployed Engineer.
AI companies have adopted the role because a model does nothing useful for a bank or a hospital until someone connects it to their data, tools, permissions, and workflows. Recent job postings repeat the same words:
| Company | What the role involves (from their postings) |
|---|---|
| Anthropic | “Work within customer systems to build production applications with Claude models” |
| OpenAI | Own “discovery, technical scoping, system design, build, and production rollout” |
| Palantir | Data integration, code reviews, and “maintenance and monitoring of production systems” |
In July 2026 Microsoft launched Frontier Company, a $2.5 billion unit with 6,000 experts who work inside customer organizations, an approach Microsoft describes as going beyond the FDE model.
What Module 0 is for
Section titled “What Module 0 is for”Modules 1–8 cover software systems, AI applications, agents, production engineering, customer delivery, case studies, a practicum and interview preparation. To a reader who has never worked as or with an FDE, that is a long list of topics with no reason attached. Module 0 supplies the reason: every later module builds the capability for one or more stages of an FDE engagement.
There is no engineering in this module. It takes about 1.5 to 3 hours, and it is required for every background, including experienced engineers, because the rest of the handbook assumes its vocabulary.
The three lessons
Section titled “The three lessons”| Lesson | Question it answers | Pages |
|---|---|---|
| 1. What is a Forward Deployed Engineer? | What is the role accountable for? | 4 |
| 2. FDE vs. adjacent roles | How is it different from a software engineer, a solutions engineer, a consultant, an outsourced team and customer success? | 7 |
| 3. The FDE delivery lifecycle and handbook map | What does an engagement look like from start to finish, and where does each module fit? | 3 |
Two things to keep in mind
Section titled “Two things to keep in mind”- The title is not the job. There is no industry standard for what “Forward Deployed Engineer” means. Companies use the same title for very different work, and other titles for the same work. This handbook defines the role by what it is accountable for, so you can place any job description you read.
- Comparisons are about responsibility, not rank. Lesson 2 compares the FDE with neighboring roles to make the boundaries clear, not to rank them. Most real FDE jobs cover only part of the full role, and that is normal.
A note on sources
Section titled “A note on sources”The four-responsibility model (Lesson 1) and the role tests (Lesson 2) are adapted from Xu Liang’s The FDE Handbook (Chinese, 2026), Chapters 1–3, with one deliberate change: this handbook does not treat consulting as “advice without code.” Large technology consulting firms design, build and run production systems; FDE vs Consultant and Systems Integrator explains what actually separates that work from an FDE’s. All Learn more resources are in English.
Learn more
Section titled “Learn more”- Article: Forward Deployed Engineers (The Pragmatic Engineer, partly paywalled)
- Article: A Day in the Life of a Palantir Forward Deployed Software Engineer (Palantir)
- Article: Microsoft Frontier Company announcement (Microsoft, July 2026; also covered by CNBC)