The RACE Engineer Owns the Machine
When the goal is software built without a human Pit Crew in the loop, the system that builds the software becomes the product that matters. Somebody has to own it as a product, and in RACE Programming that person is the RACE Engineer.
The role is now on the framework page. It sits in a section of its own, across engagements, above the Forward Deployed Engineer on the ladder.
The machine is an asset
The machine is the agents, workflows, guardrails, pipelines and evals that turn intent into running software. The Google essay named its working units. One is a role-based teammate with one job, an ownership boundary and a named reviewer. The other is a slice of workflow automated from start to finish.
This asset has a horizon measured in years. It changes as models, harnesses and team capability change. Yesterday’s necessary guardrail can become tomorrow’s waste. A machine that is never finished needs an owner.
Wider than DevOps
The closest analog is DevOps, with a much wider span. DevOps owns the path from commit to production. The RACE Engineer owns the path from intent to production. That is everything DevOps covers, plus the part before the commit: specification, agents, workflows, guardrails and evals.
The Google essay said the RACE Engineer automates the path from intent to commit. The two statements agree: intent to production is intent to commit plus commit to production.
The senior form of the FDE
The Forward Deployed Engineer now builds delivery machinery too. The FDE sits in the client’s business context and turns business intent into an AI-executable spec. They own the full pipeline for that engagement, and they build and keep evolving its agents, workflows, guardrails and pipelines. There is one FDE per Pit Crew.
The RACE Engineer keeps evolving that machinery across engagements, part-time and on request, the way DevOps works today. It rolls the machinery out into engagements and helps each Pit Wall adopt, tune and improve it.
The RACE Engineer does not replace the FDE. It is the most senior form of the FDE. Each engagement still has its own FDE, and the Pit Wall still tunes the machinery to its client. So the machine has one owner across engagements, the way the path from commit to production has DevOps today.
Why the role exists
Machinery built inside one engagement stays in that engagement. Without an owner across engagements, every Pit Wall rebuilds the same agents, guardrails and evals from scratch. What one engagement learns does not reach the next.
The FDE cannot close that gap from inside one client. The gap sits between engagements, so the owner has to sit there too.
The Google essay listed the owner’s work: automate the path, install the machinery in the project environment, and qualify the people working beside it. Done across engagements, each install starts from what the last one learned.
The profile and the path
The RACE Engineer has architect-level skills plus senior FDE skills. They design systems, not just build them. They work across engagements and are not counted in a single Pit Crew.
The ladder runs Pit Crew SWE, then Forward Deployed Engineer, then RACE Engineer.
The Pit Crew SWE implements against the Executable User Story with AI tools, inside the Quality Engineer’s guardrails. The step to FDE adds the client. The FDE is a strong developer and technical lead with people skills. They own requirements, architecture, CI/CD and observability, and the engagement’s machinery.
Validation is the senior skill at this step: judging AI output beats producing it. The FDE essay explains why the framework took the industry’s term for this role.
The step to RACE Engineer adds architecture and span. One engagement becomes all of them, and the machinery becomes a product: never finished, owned from intent to production, and carrying what one engagement learns into the next.
If you run several AI-native engagements, look at who owns what they share.
Written by Pavel Khodalev, author of RACE Programming and CTO of First Line Software. Follow new essays via RSS.
