What Is an FDE?
Everyone agrees the role is hot. Almost nobody agrees what it is. This module gives you a definition precise enough to argue with — and a test you can run against any real job posting.
A definition precise enough to argue with
A Forward Deployed Engineer is a software, data, machine-learning or systems engineer who is assigned close to a customer or mission environment and is accountable for turning a vendor's product or technical capability into a working production outcome.
Read that twice, because every clause is load-bearing. Engineer — not adviser. Close to a customer — not to a codebase. Accountable — not contributing. Working production outcome — not a proof of concept, not a demo, not a recommendation deck.
This is consistent with the actual language in official postings. OpenAI measures FDE success through production adoption, workflow impact and evaluation-driven feedback. Google describes the position as an embedded builder responsible for the connective tissue between AI products and customer infrastructure — and pointedly notes the role is not advisory. Scale AI expects daily customer interaction, full-stack delivery and product-roadmap influence.
The eight tests
A role should satisfy most of these to count as a substantive FDE position. Tick the ones that apply to a job you're actually looking at — the verdict updates as you go.
Six or more is a substantive role. Four to five means it's a hybrid — go and check the decision rights before you accept. Three or fewer and you're looking at an adjacent role wearing the title.
Origins and evolution
Palantir popularised the contemporary model. Internally it uses three names: Delta for forward-deployed software engineering, Dev for core software engineering, and Echo for the deployment-strategy function.
Their own comparison is the cleanest one-liner in the whole field: a conventional developer builds capabilities that can serve many customers, while a Delta enables many capabilities for a particular customer or mission.
Deployment Strategists tend to lead problem framing and operational adoption. Palantir itself notes that the boundaries between strategist, product manager and engineer blur in practice — which is honest, and worth remembering whenever someone tells you the categories are crisp.
Evolution of the model
What it is not
Eight roles get confused with FDE. Here's the one-line version — Module 02 turns it into a game you can lose.
| Adjacent role | Typical distinction from a strong FDE |
|---|---|
| Solutions engineer | More pre-sales, demonstration and technical validation oriented |
| Solutions architect | Concentrates on architecture and recommendations rather than direct implementation |
| Implementation engineer | Executes a defined configuration or migration with less product influence |
| Professional-services consultant | Scoped by statements of work, utilisation and billable delivery |
| Customer-success engineer | Supports adoption, health and retention after deployment |
| Site-reliability engineer | Owns reliability of a platform, not the customer's complete business outcome |
| Field engineer | Deploys physical or industrial systems — an FDE equivalent when substantial software development is involved |
| Sales engineer | Supports revenue acquisition; generally does not own long-lived production code |
Databricks' FDE-labelled opening is explicitly billable and housed in Professional Services. Google's posting stresses the FDE must move prototypes to production-grade agentic workflows. Same title, two genuinely different jobs. The title alone cannot determine the operating model — which is why you need the eight tests.