FDE, Forward Deployed Engineering, is translated in this book as "forward deployed engineering." To understand the FDE, you cannot start only from the job title, nor can you simply lump it into pre-sales, consulting, implementation, or customer success. The key to the FDE is that "forward deployed" and "engineering" both hold at the same time: engineers enter real business environments, facing incomplete information, legacy systems, permission constraints, organizational processes, and production risks, and push a vague but high-value problem toward a system that is runnable, observable, governable, and reusable.
Palantir's practice brought this role broadly into industry view and described it as a product development paradigm: engineers embed in customer environments, collaborate with core engineering teams, and continuously convert field feedback into platform capabilities. In recent years, the FDE is no longer just one company's organizational vocabulary. OpenAI defines the FDE as a forward AI deployment capability embedded in complex organizations, used to identify high-impact scenarios, restructure workflows, and build sustainable systems; Anthropic's recruiting materials likewise require such roles to embed with strategic customers, deliver AI applications, and feed back repeatable deployment patterns — note that the job titles themselves are drifting: on Anthropic's public job board, positions named Forward Deployed coexist with the Applied AI Architect series, and the named positions at one point dropped to zero before being reposted; readers should compare by responsibilities rather than titles, with verification dates in the fast-changing facts verification table.
This chapter answers five questions: why the FDE emerged; how it changes the boundaries of traditional software delivery; how it divides work with adjacent roles such as Solutions Architect, Sales Engineer, SRE, platform engineer, professional services, and customer success; how to use value loops and success metrics to judge whether an FDE is truly effective; and which common anti-patterns make work that "looks like FDE" actually deviate from the core responsibilities of the FDE.
After reading this chapter, readers should be able to describe the FDE with clear boundaries: it is not a "universal firefighting team," but a high-density engineering role that connects the customer site, engineering systems, product roadmap, and business outcomes.
Last updated