Pilot · limited independent review. This is practice, not a certificate or a job guarantee. Before you start

DrillHall

Guide · Reviewed 2026-10-18

What is a forward deployed engineer?

A forward deployed engineer (FDE) is a software engineer who works embedded with customer teams, and who also contributes to the core product [1]. The work happens in the customer's own environment, not in a build made for the whole market [3].

What the work looks like

The a16z essay describes FDEs who sit inside the customer's organisation, often for months, to learn the domain, connect systems and build custom workflows on the vendor's platform [2]. One job description likens the responsibilities to those of a startup CTO [1].

For the skills this takes, read forward deployed engineer skills.

Where the title came from

The role was created at Palantir in the early 2010s, where it was called Delta [1]. Other employers now use the title or close variants, including OpenAI, Ramp, Salesforce and Gecko Robotics [1].

Why employers ask for it

One account ties a rise in recruiting to the need to integrate AI solutions [1]. The a16z essay argues that enterprise AI adoption often stalls before production, and that embedded engineers look like a way to close the gap [2]. These are arguments by observers, not measurements.

The same title can mean different jobs

The title is not standardised [3]. One account says every company has its own flavour: some emphasise closing sales, some helping customers, some contributing to the product [1]. Two postings with the same title can therefore ask for quite different work, so read each one for what you would do in the first month.

Common questions

What does FDE stand for?
Forward deployed engineer. It is sometimes written forward deployed software engineer (FDSE), and one explainer also lists "customer-embedded engineer" [3].
Do forward deployed engineers write production code?
The sources describe them as software engineers who contribute to the product as well as working with customers [1]. One account contrasts them with solutions architects at one lab, who rarely write code on customers' infrastructure [1]. Postings differ, so read each one [3].
Is it the same as a solutions architect or a sales engineer?
Not by the sources' account: the difference described is that forward deployed engineers work with customers and also contribute to the product [1]. Some employers weight the sales side more heavily than others [1]. See the comparison guide.
Is it just consulting?
It is a risk the a16z essay names: copying only the embedded-engineer part, without a strong product, can leave a company with many custom deployments that are hard to maintain, a services business rather than a product company [2]. The essay's remedy is to treat forward deployment as scaffolding, with time limits and a plan to turn custom work into reusable product [2].

Is it for you?

Our own prompts, not from the sources. Answer them in a notebook.

  1. Would you rather own a customer's outcome for months than ship features for many users?
  2. Can you explain a technical failure in three plain sentences to someone who must decide what to do next?
  3. When a customer asks for a one-off, how do you decide whether it should become part of a product?
  4. Have you debugged a system you did not write, and found where to look?

Try the work

DrillHall's Atlas project is a 10-stage engagement with a fictional enterprise customer. To see how a mission works without an account, use the free preview. The templates show the documents, and how we assess explains what counts as evidence. To get started, read how to become a forward deployed engineer.

Sources

  1. What are Forward Deployed Engineers, and why are they so in demand? · The Pragmatic Engineer (Gergely Orosz) · 2025-08-12
  2. The Palantirization of everything · a16z (Marc Andrusko) · 2026-01-16
  3. What Is a Forward Deployed Engineer? · DataCamp