21. Forward-Deployed Engineer (FDE)
Evidence label: Role family. Current official postings at OpenAI, Anthropic, ServiceNow, and other AI vendors use Forward-Deployed Engineer or a close variant.
What they do
Own the technical deployment of an AI system inside a customer's real environment. FDEs work between the customer's domain and the vendor's product, taking a problem through discovery, architecture, implementation, evaluation, production rollout, adoption, and handoff. Field evidence then feeds back into reusable product capabilities and deployment standards.
OpenAI's current FDE description measures the role through production adoption, workflow impact, and eval-driven feedback rather than prototype delivery. Anthropic also lists FDE positions in the United States, France, and Germany as of August 2026. Current vacancies establish that the title is real; they do not establish how common it is across the broader market.
Responsibilities
- Translate ambiguous customer workflows, data constraints, and domain rules into technical requirements and measurable outcomes
- Design and build the integration, evaluation, security, and production architecture
- Work directly with customer engineers, operators, and domain experts through rollout and adoption
- Make scope, speed, and quality trade-offs while retaining launch evidence and rollback paths
- Turn one deployment's lessons into reusable tools, playbooks, evals, or product improvements
Distinction from adjacent roles
| Role | Primary boundary |
|---|---|
| Solutions engineer | Proves technical fit, often before or during a sale |
| Forward-deployed engineer | Owns hands-on technical delivery and production adoption in the customer's environment |
| Product engineer | Owns a reusable product surface for many customers |
| AI architect | Defines reference architecture and standards across deployments |
The boundary varies by employer. OpenAI's general posting explicitly separates technical solution ownership from the commercial or executive relationship, while domain-specific FDE roles can require regulated-industry knowledge and substantial travel.
Required skills
Senior software or AI engineering, systems architecture, API and data integration, eval design, production operations, customer discovery, domain modeling, and clear communication under ambiguous requirements.
Entry paths
Senior software engineer with customer-facing delivery experience, solutions architect who still writes production code, implementation engineer moving into end-to-end ownership, technical consultant with strong product and AI depth.
Field example: a useful system needs an adopted interaction
In IFTTD episode 373, Léa Buendé, an FDE at Adobe, recounts a field engagement with engineers accustomed to paper manuals. Her proposed chatbot did not match their habits; they used it like a search box, and the interaction did not supply the context it needed. The account spans her career and does not establish that this engagement occurred at Adobe.
The delivery lesson is to observe representative users completing their actual task before treating a working integration as successful adoption. Record whether they find the answer, what help they need and whether the interaction fits the work setting. This is a practitioner case, not a comparison proving that chat or search is generally superior.