What is a forward deployed engineer?

A forward deployed engineer is a software engineer who works inside a customer's organization, builds against that customer's real data and real systems, and stays responsible for the software until it is running in production.

That is the whole definition. Everything else people say about the role is either an implication of it or a description of one company's version.

The three tests

The title gets applied loosely, so it helps to have tests that do not depend on what a job advert calls the role.

Does the person write code that reaches production? Not a proof of concept somebody else hardens. Not an architecture document. Code that gets merged and runs. If the answer is no, the role is design or presales, whatever the title says.

Do they work in the customer's environment? The customer's data, their authentication, their approval process, their staging environment that does not match production. Working from outside means working from a description of the environment, and the description is always wrong in the places that matter most.

Are they accountable for the outcome? The deployment either runs or it does not, and the forward deployed engineer cannot hand the failure to an implementation team. This is the test that cannot be faked and the fastest way to tell a genuine forward deployed engineering function from a professional services team with a new name.

Two out of three is a real job and a useful one. It is a different job.

Where the name comes from

The term is borrowed from the military, where a forward deployed unit is stationed in the field, close to the problem, rather than at home base. The software version keeps the same idea: the engineer moves to where the work is instead of receiving a description of it.

Wikipedia's entry on the forward deployed engineer records that Palantir popularised the role and that its responsibilities overlap with solutions architects, sales engineers, customer engineers, professional services engineers, systems integrators and IT consultants. That overlap is real. The tasks look similar from the outside and the accountability is different, which is why this guide spends six pages on the comparisons.

Why the role exists at all

Palantir's early customers had problems nobody could specify in advance. The customer could not write a requirements document, because the customer did not know what the software should do until they saw something working against their own data.

A normal delivery model breaks on that. You cannot run discovery, write a specification, leave for six months and return, when the discovery itself is only possible inside the environment. So the engineer moved. Not an analyst who observes and reports, and not a consultant who writes a recommendation. An engineer who commits code, sits in the customer's standups, and finds out what is true by building against the systems that actually exist.

The Palantir model covers the origin properly, including why that original condition still decides whether the model works for anyone copying it.

FDE, FDSE, and the other names

FDE is forward deployed engineer. FDSE is forward deployed software engineer, which is the title Palantir and OpenAI both use for the same kind of work. Some companies say deployment engineer, forward deployed AI engineer, or deployment strategist for the less code-heavy variant.

The names matter less than what the person does, and here the industry is genuinely inconsistent. An analysis of 1,000 job postings carrying the title, published by Henley Wing Chiu in November 2025 using Revealera data, found the title covers three different jobs: a production engineer embedded with customers (60 percent of postings), a sales engineer with implementation duties (30 percent), and an internal tools builder facing no customer at all (10 percent).

That is worth knowing before you accept a job with the title or buy a service that claims it. We take it apart in the three jobs hiding behind the FDE title.

What a forward deployed engineer is not

Not a consultant. A consultant takes the specification and delivers the agreed scope. A forward deployed engineer questions the specification, because in this model the specification is one of the outputs rather than an input.

Not a sales engineer. A sales engineer works before signature and is measured on whether the deal closes. In the 1,000 postings analysed, none of the forward deployed roles carried a sales quota.

Not a support engineer. Support fixes what is broken in software that already works. A forward deployed engineer builds the thing that does not exist yet.

Not a permanent fixture. This is the one people get wrong most often, and it matters most. An engagement with no end date has stopped being a deployment and become a dependency. When AWS announced its own forward deployed engineering organization in June 2026, it named customer self-sufficiency after the engagement as a design goal, and that is the right test to hold any vendor to, including us.

Who hires them

Palantir has used the model since the mid-2000s. In June 2026 AWS announced a Forward Deployed Engineering organization backed by a $1 billion investment, embedding thousands of engineers with customers to build production AI systems. OpenAI, Anthropic and Google all post the title. Beyond the large names, 58 percent of the postings analysed came from companies with 11 to 200 employees, which says the model is being adopted by growth-stage companies selling into large ones rather than only by the giants.

The customer side skews to industries where the environment is the hard part: financial services in 24 percent of postings that named an industry, government and defence 18 percent, healthcare 17 percent, insurance 17 percent.

Why anyone should care

If you are selling AI into large companies, this role is the difference between a pilot that impresses people and a system that runs. If you are buying, it is the difference between a vendor who hands you a working demo and one who is still there when it meets your real data.

Read what a forward deployed engineer does next for the week-by-week version, or when forward deployed engineering is the wrong answer if you want the case against it first.