"Plan F, Max. Plan F." When Guillaume Rocquelin said those words to Max Verstappen on the final lap of the 2021 Abu Dhabi Grand Prix, it was not a casual suggestion. It was the product of hours of preparation, a pre-agreed shorthand for a specific set of actions that the driver could execute without thinking. That is what a race engineer does: compress complex information into language that a driver can act on at 300 km/h.
The race engineer is the voice in the driver's ear for every session of a race weekend. They are the translator between raw data and human decision, the strategist who must think three moves ahead while the driver is focused on the next braking zone, and the coach who must know when to push and when to calm down.
What a Race Engineer Does Across a Weekend
The race engineer's responsibilities span the entire event, from the first installation lap to the chequered flag:
Before the weekend: The race engineer works with the strategy team to develop the race plan — pit stop windows, tyre compound choices, safety car probabilities, and contingency scenarios. They also review the driver's notes from previous years at the same circuit and coordinate with the performance engineer on baseline setup.
Practice sessions: The race engineer manages the run plan, deciding which setup options to test and in what order. They translate the driver's subjective feedback — "the rear is nervous on entry" — into specific setup changes that the performance engineer can implement. They also begin building the tyre data that will underpin the strategy.
Qualifying: The race engineer manages the out-lap timing, track position, and tyre preparation. Getting the driver onto a clear track at the right moment with tyres at the right temperature is as important as the lap itself. They also decide which compound to use in each session — sometimes a harder compound that guarantees two runs is preferable to a softer compound that may only allow one.
The race: This is where the race engineer earns their salary. They monitor every data channel — tyres, fuel, engine health, gaps to competitors — and make real-time decisions about when to pit, what compound to fit, and whether to attack or defend. They also manage the driver's emotional state: calming frustration, reinforcing confidence, and providing just enough information without overwhelming.
The Communication Challenge
F1 team radio is limited in bandwidth and frequently delayed. The driver may be in a high-G braking zone when a message arrives, unable to process it. The race engineer must therefore be selective about what to say and when to say it.
The best race engineers follow a few principles:
- Signal over noise: Only communicate what the driver cannot figure out themselves. The driver knows they are slow; the useful information is why and what to do about it.
- Pre-agreed codes: Shorthand like "Plan F" or "Mode 4" allows complex instructions to be transmitted in two words. These codes are agreed in pre-race briefings.
- Timing matters: Deliver strategy calls during a relatively calm section of the track, not during a braking zone or a high-speed corner.
- Tone carries meaning: A calm voice under pressure reassures the driver. An urgent voice signals that immediate action is needed. The engineer's tone is as much a communication tool as their words.
Famous Driver-Engineer Partnerships
The best driver-engineer partnerships are built over years of shared experience:
Peter Bonnington and Lewis Hamilton: "Bono" and Hamilton worked together through Mercedes' dominant era, developing a communication style that balanced Hamilton's instinctive driving with Bonnington's data-driven approach. Their exchanges — from "Hamilton, it's lap 37" to "Get in there, Lewis!" — became part of F1's soundtrack.
Guillaume Rocquelin and Max Verstappen: "Rocky" and Verstappen built a partnership based on directness and trust. Rocquelin's calm analytical style complemented Verstappen's aggressive driving, and their pre-race preparation was meticulous enough that critical moments like Abu Dhabi 2021 could be handled with pre-agreed codes.
Adami and Charles Leclerc: At Ferrari, the race engineer-driver relationship carries additional weight because of the team's history and the intensity of the tifosi. The partnership has navigated strategic complexity, reliability issues, and the pressure of Ferrari's expectations.
What these partnerships share is trust built through repetition. A driver who trusts their engineer can execute a strategy call without hesitation. A driver who does not will second-guess, which costs time and sometimes positions.
The Skills Required
The race engineer needs a combination that is rare in any profession:
Technical depth: They must understand the car's systems at a level deep enough to diagnose problems from telemetry data and recommend solutions. This requires engineering training and usually years of experience in other roles within the team first.
Strategic thinking: The race engineer must process multiple variables simultaneously — tyre life, fuel status, track position, competitor behaviour — and make decisions that optimise the overall result, not just the next lap.
Communication skill: The ability to translate complex data into simple, actionable language is what separates good race engineers from great ones. "The rear left is at 120 degrees" is data. "You need to manage the rear tyres in sector three" is direction. "Plan B, now" is a decision.
Emotional intelligence: The driver is under enormous physical and psychological stress during a race. The race engineer must read the driver's tone of voice, recognise when frustration is building, and adjust their communication style accordingly.
What to Listen For
On the team radio broadcast, the race engineer's calls reveal the strategy underneath the racing:
- "Box, box, box" — the pit stop call. The timing of this call relative to competitors reveals whether the team is undercutting or reacting.
- "We need to save fuel" or "lift and coast" — the driver is being asked to manage a resource constraint.
- "You have pace in hand" — the engineer believes the driver can go faster if needed, usually to defend against a pursuing car.
- "Plan A is still active" — the pre-race strategy is on track. If the engineer says "switching to Plan B" or "Plan C," something unexpected has happened.
- Long silences — often mean the engineer is letting the driver concentrate, or they are working through a complex strategy calculation before communicating.
The race engineer does not drive the car, but they shape how the driver drives it. In a sport where decisions are measured in tenths of a second, that influence is decisive.