What is a forward deployed engineer (FDE)?

Explained

A forward deployed engineer (FDE) is a software engineer embedded with a client rather than working on a product from a distance. The role mixes engineering with direct contact with the people who use the system: the FDE learns the client's processes, connects the platform or model to its real data and systems, writes the code that is missing and stays until the solution works in daily operation. The model was popularised by Palantir, where these engineers are called Deltas, and is now common at AI companies, because AI is easy to demo and hard to deploy.

What an FDE actually does

• Sits with the client's teams to understand the process, the data and the constraints before writing code.
• Connects the platform or model to the client's systems: ERP, CRM, document repositories, identity and permissions.
• Writes the integration code, workflows and evaluations that a generic product does not include.
• Takes the solution from pilot to production and stays through the first weeks of real use.
• Brings back to the product team what the field teaches: gaps, recurring requests and what breaks.

FDE, consultant or in-house team?

A consultant usually advises and documents; an FDE builds and ships. A solutions engineer supports the sale before the contract; an FDE works after it, on delivery. An in-house team knows the business best but often lacks experience of taking AI to production several times over.

In practice the FDE model sits in the middle: someone external with deep technical skills, working as part of the client's team for a defined period, with the goal of leaving something running and the internal team able to own it.

When it makes sense

• The value depends on connecting AI to messy, real systems and data, not on the model alone.
• Several pilots have worked in a demo but none has reached production.
• The internal team knows the business but has not yet run AI in production.
• There is a clear owner on the client side who will take over once the solution runs.

Frequently asked questions

Decision guides that use this term

• In-house team, AI consultancy or platform: who should build your AI?
• Forward deployed engineers or a project-based consultancy: how should you bring in outside AI help?

Further reading

• Multi-Agent AI Systems: From Costly Prototypes to Production Reality

Related terms

• Platform Shared infrastructure that brings models, agents, data connections, workflows and governance together in one place, so teams build AI use cases on a common base.
• Production The live environment where an AI system serves real users and real data, as opposed to development, testing or a pilot.
• Acceptance Criteria Testable conditions that define when a feature or a model's output is complete and correct, so that 'done' can be checked rather than argued.
• AI Bill of Materials A machine-readable inventory of everything an AI system is built from: models, datasets, dependencies, licences and their lineage.
• AI Governance The policies, processes and controls an organisation uses to make sure its AI is safe, lawful, ethical and worth what it costs.
• AI Native Systems, products and processes designed from the start with AI as a core part, rather than with AI added afterwards.