What is a Forward Deployed Engineer?

The activity and the role

The industry term is an engineer's job title, so it is easy to read it as one person who goes to the client and solves everything alone. The role name does not mean that. In RACE, forward deployed work is done by the Pit Wall roles together: AI Product, the Forward Deployed Engineer and the Silicon Software Engineer, the AI agent. Roles are not people. On a small engagement one person can carry both human roles; on a larger one several people share them.

What Forward Deployed Engineering does

• Close contact. The Pit Wall talks to the client from the first conversation. Engineering sits at that table instead of waiting behind a chain of intermediaries.
• The business problem. Take it apart until it is clear what the client needs and why.
• Ways to solve it. Show technical solutions, not questionnaires: ideation, two or three working prototypes, demos. Seeing a prototype helps the client find out what they need.
• Feasibility. Check that what the prototypes promise can be built, against real constraints, and bring in the people and technology the problem needs.
• The frame. Set the business and technical answer to the problem, 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.
• The plan. Lay out how the frame will be implemented, phase by phase.
• Ready to hand over. Keep transfer notes from day one, so the work can change hands at any moment. This is an engineering practice, not a personal talent.
• The handover. Bring in the Pit Crew, onboard it, and step back. AI Product stays with the engagement and keeps authoring Executable User Stories; the engineering side moves to part-time oversight.

Short engagements can run start to finish on the Pit Wall. Longer ones move to a Pit Crew once the frame is set, because holding the people who did the forward deployed work at full time until production is a poor use of scarce talent.

What the Forward Deployed Engineer brings

The FDE is a strong developer and a technical lead with people skills, and thinks in business terms: every build answers why this client needs it. They work in the client's context, colocated or remote as the engagement requires, beside AI Product, who owns the product side of the specification and the acceptance tests.

• Feasibility and architecture, recorded as Architecture Decision Records, and the engineering quality of the Executable User Story.
• The pipeline: CI/CD and observability for what the Pit Wall and the Pit Crew build.
• Code that writes code: the engagement's delivery machinery, the agents, workflows, guardrails and pipelines. RACE scales by raising the share of the backlog that machinery clears, not by adding people.
• Validation of AI output, the senior skill of the role: judging what the agent produced beats producing it.
• Knowing whom to lean on: other architects, a RACE Engineer, specialists the problem needs.

Most of the FDE's time goes into the engagement while the frame forms. After the handover the FDE stays part-time, mostly on architecture and oversight, and can drop into the Pit Crew to execute alongside the AI tools.

Pit Crew Software Engineer, FDE, RACE Engineer

The step from Pit Crew to FDE adds the client, and it is the hard step: talking to the business is a different skill from building. The RACE Engineer is the most senior form of the FDE. It does not replace the FDE: each engagement keeps its own, and the Pit Wall still tunes the machinery to its client.

From Palantir to an industry term

The term is best known from Palantir, whose Forward Deployed Software Engineer postings describe engineers who work directly with customers to understand their greatest problems and design and implement solutions, with responsibilities that resemble those of a startup CTO (posting checked October 21, 2026).

RACE Programming kept the substance and first used a different name, the ACE Software Engineer, because the literal reading of forward deployed suggested a promise to be on site that the framework did not make. When the industry's use of the term settled on an engineer embedded in the customer's context, on site or remote, the framework adopted it. Adopting the Forward Deployed Engineer explains the rename.

What RACE adds to the common definition is the split between the work and the person. Forward Deployed Engineering is done by the Pit Wall roles, not by one engineer alone, and it ends with a frame a Pit Crew can build. The FDE brings the engineering side, including the machinery that clears the engagement's backlog.