Forward deployed engineer
The one who goes and writes the code at the customer’s
A forward deployed engineer is an engineer a vendor places inside a customer’s own systems to write the code the standard product cannot, like a chef a caterer sends into your kitchen instead of delivering trays.
- Floor 3The Agent
- P2Writes the application
- Emerging titleIt appeared recently. What it covers is not yet stable from one employer to the next.
What they answer for
The deliverableA system running at a named customer, and the pieces of that system that make their way back into the standard product. If they leave, the integration stops.
The profile
Five activities, scored 0 to 3- ResearchProducing knowledge that does not yet exist.
- BuildShipping a system that runs, deploys and breaks.
- OperateKeeping it in production: cost, incidents, drift, on-call.
- VerifyMeasuring, testing, attacking. Producing a verdict that holds.
- LeadDeciding, persuading, driving adoption, answering to others.
What the work is
The journey
A vendor selling an AI product to a large organisation almost never sells the product alone. The customer’s data has a shape no connector anticipated. Their internal rules forbid things nobody had written down. And their definition of "it works" exists nowhere on paper. Someone has to make the journey, and that someone writes code.
The two repositories
The distinction that matters is a count of repositories. An integration engineer works in the customer’s; a product engineer works in the vendor’s. The forward deployed engineer writes in both, and that dual membership is the whole of their value: what they have had to write by hand at three customers in a row becomes a product feature. The role is a sensor as much as a building site.
The trap
The trap is that the title spread faster than the trade. It now covers both an engineer who ships code and a pre-sales specialist who runs demonstrations, and the two adverts read word for word alike. The only reliable sign is the repository: an advert naming no language, no codebase and no deployment is not describing a role that builds.
A week in the role
- Two or three days inside the customer’s systems: access, real data, compliance constraints nobody had written down.
- Code, in two repositories that look nothing alike.
- Trade-offs settled in meetings, because half the blockers are not technical.
- A report back to the product team: whatever has been written by hand twice in a row becomes a feature request.
Ways in
- From a software engineering role. Tolerance for the unknown counts for more here than technical depth.
- From technical consulting, provided you have kept your hands on production code.
- What the role does not require, whatever the advert says: training a model. You integrate a model you did not build.
Reading an advert
3 signs- The advert talks about workshops, pre-sales and presentations, and names neither a repository nor a language.
- This is a pre-sales role under an engineering title. The real profile is Lead 3, not Build 3.
- The role reports to the sales organisation, with a variable share tied to signature.
- Not disqualifying, but informative: the deliverable becomes the contract, not the system.
- The advert promises "no travel".
- The word forward means precisely the journey to the customer. Without it, the role is that of an integration engineer, which is a different trade.