RACE Programming
Audio brief · 2 min
By Pavel Khodalev · · framework · roles · language · 4 min

We Sell the Engineering, Not an Engineer

In RACE Programming, Forward Deployed Engineering is an activity the Pit Wall performs, and the Forward Deployed Engineer is one of the roles that performs it. The role name misleads: it sounds like one engineer who solves everything alone, and that reading drops AI Product out of the picture.

An Activity and a Role

The term is best known from Palantir. Its Forward Deployed Software Engineer postings describe engineers who work directly with customers on their greatest problems and design and implement solutions. That is a fair job title. Read as a job title, it names a person.

A buyer who hears “engineer” pictures one specialist who handles the business, the technology and the delivery. RACE splits the work from the person. The activity has target tasks and a result.

Three roles perform it: AI Product, the Forward Deployed Engineer (FDE) and the Silicon Software Engineer, the AI agent. You buy an outcome from that set of roles, not from a hero.

What Forward Deployed Engineering Does

Forward Deployed Engineering is close contact with the client: take the business problem apart, show technical ways to solve it in prototypes, agree on a plan. Engineering sits at the first conversation with the client, not behind a chain of intermediaries. The tasks:

  1. Take the client’s business problem apart until it is clear what they need and why.
  2. Show ways to solve it: ideation, two or three working prototypes, demos.
  3. Check feasibility against real constraints, and bring in the people and technology the problem needs.
  4. Set the frame: the business and technical answer to the problem.
  5. Lay out the implementation plan by phases, with an indicative estimate of the next phases.
  6. Keep transfer notes from day one, so the work can change hands at any moment.

AI Product brings the business side: the problem, the Executable Product Roadmap with the Team Principal, the Executable User Stories, acceptance. The FDE brings the engineering side. The Silicon Software Engineer builds the prototypes and the code with them. Close contact, prototypes, the frame and the plan belong to the Pit Wall together.

An analyst who takes the business problem apart is doing Forward Deployed Engineering. That analyst is AI Product, not an FDE.

What the FDE Role Brings

The FDE role is real and hard. The step from Pit Crew to FDE adds the client, and talking to the business is a different skill from building. The FDE is a strong developer and a technical lead with people skills who thinks in business terms.

The role owns feasibility and architecture, recorded as Architecture Decision Records. It owns the pipeline: CI/CD and observability for what the Pit Wall and the Pit Crew build. It writes code that writes code, the engagement’s machinery of agents, workflows, guardrails and pipelines. Its senior skill is validation of AI output.

The FDE also knows whom to lean on: other architects, a RACE Engineer, the specialists the problem needs. None of this is the business side. That is why the role is not the whole activity.

Where It Ends

The activity ends when the frame is set. The frame is what used to be called solution architecture. In RACE terms it is the prototype the Team Principal accepted, the Executable Product Roadmap and the architecture decisions behind them.

Then a trigger fires, and a Pit Crew comes in, onboards and builds. The forward deployed people step back. AI Product stays with the engagement and keeps authoring Executable User Stories. The engineering side moves to part-time architectural oversight and can drop into the Pit Crew to execute alongside the AI tools.

There is no handover day. The engineer’s share falls while the Pit Crew’s rises. Holding the top people at full time until production is a poor use of scarce talent. Transfer notes from day one are what make the step back safe: the work can change hands at any moment.

Short engagements can run start to finish on the Pit Wall. The staffing accordion guide covers the people side.

Adopting the Forward Deployed Engineer matched the industry FDE, who stays until the thing runs, to the Pit Wall. The rename was right; the activity ends at the frame, and its people step back.

Roles, Not People

One person can carry both human roles on a small engagement, and several can share them on a large one. The framework does not fix the headcount. The combined responsibility of the Pit Wall is what the client gets. We sell the engineering, not an engineer.

Ask three things of anyone selling you forward deployed work: who carries the business side, when the work ends and what triggers the build, and what the builders receive.

If you want to test those questions against your own engagement, write to hello@raceprogramming.com.

Written by Pavel Khodalev, author of RACE Programming and CTO of First Line Software. Follow new essays via RSS.