The shortest accurate definition comes from Bob McGrew, who spent eleven years at Palantir and later ran research at OpenAI: a Forward Deployed Engineer is a software engineer who sits at the customer’s site and fills the gap between what the product does and what the customer needs. The brevity hides a lot.
Engineer. This is a real engineering job, not a sales-engineer or customer-success position with technical flavoring. It involves writing production code, debugging integrations against the customer’s real systems, and making architectural decisions the customer’s own engineering team would otherwise have to make alone. Palantir describes the responsibilities as similar to a startup CTO’s, which is the right reference class. In every serious job listing, whether at Anthropic, OpenAI, or Cursor, the artifact the engineer is judged on is working software running in the customer’s environment rather than a slide deck describing what that software would look like.
Deployed. The role is not remote. The engineer works on the customer’s premises, in their meeting rooms, with access to their data, talking to the people whose work the software is supposed to change. Anthropic’s listing puts travel at twenty-five percent. Palantir Deltas have worked on the Airbus final assembly line and in air-gapped intelligence facilities. OpenAI’s head of FDE has flown to Iowa to sit with farmers on a John Deere project. The job is physical because the real problem is only visible at the level of the workflow.
Forward. The military origin is not incidental. A forward-deployed force operates ahead of the main body, with the autonomy to make decisions headquarters cannot. The FDE has the same latitude: commit code, change scope, make trade-offs without waiting for product management back home, because there is no time and no clean information path for headquarters to weigh in.
The Venn diagram
Draw a diagram of the adjacent roles (software engineer, product manager, solutions architect, customer success manager) and the FDE sits in the middle. The contrasts are instructive:
A solutions architect designs the architecture but doesn’t write the production code that lives in the customer’s repositories. The deliverable is a diagram and a recommendation.
An implementation consultant writes production code but can’t influence the vendor’s product roadmap. The code is good but isolated; the lessons of one engagement never feed back into the product.
A sales engineer does demos and answers technical questions but rarely embeds for months. The work serves closing the contract rather than delivering the outcome it promised.
A customer success manager owns the relationship and the renewal but is rarely positioned to ship code. The calendar between identifying a problem and fixing it is measured in quarters.
An FDE does all of these things, sequentially or simultaneously, and having them integrated in one person is what makes the role work. The skills that matter are technical depth, product instinct, commercial fluency, and tolerance for ambiguity. People who have all four are rare, which is why median total compensation sits around $238,000 and senior frontier-lab packages exceed half a million dollars.
The one-question diagnostic
How do you tell whether a company’s FDE model is real? Ask whether the FDEs ship code into the vendor’s own product. If they do, the model is working as intended: the FDE closes the gap for the current customer and, through commits to the core product, closes it a little for every future customer. If they only ship custom integrations for a single account, with nothing flowing back, the model has collapsed into consulting. The work might still be valuable, but it isn’t creating the compounding advantage the motion was designed to create.
The titles vary wildly: Applied AI Engineer at Anthropic, Agent Engineer at Sierra, Agent Product Manager at Decagon, Implementation Engineer at Harvey. Nick Mehta’s aphorism applies here: customer success is a strategy, not a job title. Any role that owns the outcome the customer paid for, and is empowered to ship the change rather than merely advocate for it, is doing this work, whatever the local title says.
Want the full playbook, with the templates, the interview transcripts, and the week-one checklist? It’s all in my book Forward Deployed AI Engineering: A Working Guide to the Hottest Job in Software, available on Amazon.