Eupraxic

Articles

What a forward deployed engineer actually does

It isn't a sales engineer, a consultant, or a CSM with a GitHub account. Every word in the title is doing work.

By Nasser Ghanemzadeh · · 3 min read

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.

That sentence is short, and it hides a lot. The easiest way to unpack it is one word at a time.

Engineer

This is a real engineering job. It isn't sales engineering or customer success with technical flavoring. It means 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 engineer is judged on working software running in the customer's environment. A slide deck doesn't count.

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 engineers 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 only shows up at the level of the workflow, and you can't see a workflow from a video call.

Forward

The military origin matters. A forward deployed force operates ahead of the main body, with the autonomy to make decisions headquarters can't. The FDE has the same latitude: commit code, change scope, and make trade-offs without waiting for product management back home, because there's no time and no clean information path for headquarters to weigh in.

Where it sits among the roles you already know

Draw a diagram of the adjacent roles and the FDE lands in the middle:

  • 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 roadmap. The lessons of one engagement never feed back into the product.
  • A sales engineer runs demos and answers technical questions but rarely embeds for months. The work aims at closing the contract, not delivering what it promised.
  • A customer success manager owns the relationship and the renewal but is rarely positioned to ship code. The gap between spotting a problem and fixing it is measured in quarters.

An FDE does all of these, sometimes in sequence and sometimes in the same afternoon. The integration in one person is the point. 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 the broad-market median base sits around $174,000 and senior packages at the frontier labs run past half a million dollars.

The one-question diagnostic

How do you tell whether a company's FDE model is real? Ask whether its FDEs ship code into the vendor's own product.

If they do, the model is working as designed. The FDE closes the gap for the current customer and, through commits to the core product, closes it a little for every future customer too. 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. It just isn't building the compounding advantage the motion exists to build.

Ignore the title, look at the work

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 line about customer success applies here too: it's 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 business card says.

About the author

Nasser Ghanemzadeh is a former CEO and CPO with 17 years of product leadership. He exited Nivo, a B2B fintech with 200K+ users, after growing revenue 450%, was founding head of product at Pangouan, and co-founded the Iran Startups community and the Finnova accelerator. He builds Vectig with Claude Code and MCP every day and runs every Eupraxic Sprint himself. Eupraxic is one engineer for now; the method is written down so it will not stay that way.

This article draws on his book, Forward Deployed AI Engineering.

Want one useful AI workflow in your product?

Score your workflow in two minutes, then book a 15-minute Scoping Call. If it fits, you leave the call with a Brief draft and a kickoff date.