Barcelona, Spain
Motorsport Engineer & Software Developer.
Master's in Motorsport EngineeringMBA
Motorsport engineering taught me to understand the car and the driver, and software development gave me a way to build the tools a team needs rather than wait for someone else to make them. What ties the two together is the structure my master's degrees gave me for the people, the processes and the priorities behind the work, and it is in combining all three that I try to do this job as well as it can be done.
Experience
Chief Engineer at RPM in the FIA Formula Regional European Championship, through the 2026 season. Before that, race and performance engineer from Formula Renault 3.5 to FIA F3, and five years as Head of Sim Racing Engineering at Williams Esports.
Career
Race programmes, sim racing and teaching, often running at the same time.
Vision
Every step connected to the next, each with its own tools.
Everything connected, in a loop that starts again at every event.
Scroll to walk through it: each step shows what happens on the ring and the software behind it.
Lap simulation and set-up sweeps in Canopy, vehicle dynamics models in MATLAB / Simulink, simulator sessions with the driver, and CAD / CAE for anything that needs designing before the event.
The driver's lap against the reference, corner by corner, read together with what the real car is doing on track. Coaching and set-up decided as one.
Set-up evolution, tyre strategy, weather radar and live timing, all in Pinion, to process the information as it arrives and extract the most from the package every time we go out on track.
Data analysis corner by corner and lap by lap, across different data acquisition packages: were the tyres ready, was the energy from weaving and the brakes enough to start the push lap, what the car did, what the driver did, and why.
Track data fed back into Canopy, with AI adjusting the vehicle model until simulation and car agree. The next event starts from a better model and a better understanding of the car.
Everything connected, in a loop that starts again at every event.
Leadership
Good results come from teams that know how they work. Leading RPM's engineering since the team's first day, and groups of up to 15 engineers at Williams Esports, has shaped how I do it.
Shared processes and methods for the whole department, so an event runs the same way whichever engineer is on the car and nothing depends on one person's memory.
Four years teaching vehicle dynamics showed me that people perform when they understand the reasons behind a decision, so I explain the physics before I hand over the task.
Every technical decision, on and off track, has one owner. Everyone knows who decides, who gets asked and when, and the team moves faster for it.
When a task costs the team time at every event, I build the tool that takes it away, so the engineers spend their weekend on engineering.
Built for motorsport
Much of a race team's daily work still happens across separate tools. Pinion covers the needs of every department in the team and brings them together in one cross-platform app, built to be visual and intuitive to use. Designed by me.
Set-ups, run plans, tyres, ballast and session sheets for every car, in one place.
The championship timing feed collected around the clock, cleaned and stored lap by lap.
Lap data turned into automatic, corner-by-corner coaching notes for each driver.
Telemetry shared live between the simulator and the engineers.
Canopy simulation tools, suspension calculations and a data bridge between Canopy and WinTAX. In beta: an AI that imports the real car's data directly and runs and correlates the simulations on its own, explained step by step below.
Every session kept, comparable and ready to replay.
Travel coordination and event timetables for the whole team.
An AI assistant for the championship regulations.
Everything unified in one app. Designed and coded by me, with AI to build faster.
Pinion · Canopy tools · beta
One of the tools I built inside Pinion, now in beta. The AI imports the real car's data directly from the track, runs the simulation in Canopy and adjusts the vehicle model until it correlates, with nobody touching Canopy. This is how it works.
The AI takes the real car's data from the last run, straight from Pinion, launches the simulation in Canopy and lines the simulated lap up against the real one: speed trace, lap time and the difference between them, metre by metre.
The model is checked against what the real car did on track. Aero load matches, but the g-g diagram shows the model carrying more lateral grip than the car.
The tyre's Magic Formula parameters are tuned automatically, iteration by iteration, until the lateral force curve fits the data measured on the car.
| Parameter | Value | Change |
|---|
The adjusted model runs again. The error in the slow corner disappears, and the simulated lap now follows the real car. The correlated model goes back into Pinion, ready for the next run.
Illustrative data, not team telemetry
Drivers
From rookies stepping into single-seaters to Formula 1 and IndyCar.
Teo Martín · Formula V8 3.5 · 2017
Now: five-time IndyCar champion
RPM · FRECA · 2024
FRECA rookie champion 2024 · FIA Formula 2 with Invicta in 2027
DR Formula · FRECA · 2021
Went on to FIA Formula 3
Pons Racing · Formula Renault 3.5 · 2015
Former Formula 1 driver
RPM · FRECA · 2022–2023
Went on to FIA Formula 3
Teo Martín · Euroformula Open · 2018
Van Amersfoort · FRECA · 2019
Background
Mechanical engineering and motorsport engineering, four years teaching vehicle dynamics, and an MBA for the management side of the job.
Barcelona, Spain
Open to conversations about race engineer and chief engineer roles.