Chief Software Officer

Synapse works. What it is not yet is a platform able to hold ten times the fleet it holds today. That distance is the job.

You own the whole software layer: the agents, the operating data, the portal and the boundary with the vehicle. Here that boundary is not an API you cannot touch. If an agent is missing a signal, the answer can be to add the sensor to the next production run. Authority from the physics to the cloud.

We do not want you to scale it by hiring. We want you to scale it by orchestrating agents, and we will say the target plainly: multiply what every person on the team produces by a hundred, yourself included. If a team of five delivers like a team of fifty, you have done the job. If you do not believe that is possible today, this is not your role.

When an agent gets it wrong here you do not get odd text. You get a delivery that never happened, with a customer waiting. Agents with physical consequence, on type-approved vehicles that live seven years on the street.

Responsibilities

• Own the architecture of Synapse and take it from a product that works to a platform that scales.
• Design how software gets updated on a type-approved vehicle already on the road.
• Decide what an agent solves and what code solves.
• Build the evaluation and monitoring of the agents: how you know they are right, and what happens when they are not.
• Build and lead the software team, and answer for output per person rather than headcount.
• Own product security by design, with the European cyber resilience regulation on the table.

• You have kept software running in production with customers on top of it. Not only designed it.
• Actually AI native. LLMs and agents in production, with their failures and their cost per call.
• You already use agents to multiply your own work. You will teach the team to do it.
• You know when not to rewrite. There are customers on the road.
• Based in Seville or willing to relocate.

Counts in your favour

• Hardware, telemetry, automotive or industry.
• Product security, over-the-air updates or embedded systems.
• Having built a software team from the first hire to the tenth.

You will fit here if

• You want real authority, not a title. You decide, and you answer for it.
• AI with physical consequence interests you more than AI that writes text.
• Technical debt does not scare you. It is debt we earned: every shortcut behind it closed a sale.
• Here decisions freeze at the production run, and that frustrates a lot of good engineers.

• A product already running customer fleets, and the mandate to turn it into a platform.
• Control from the sensor to the cloud. If the software needs something from the vehicle, the vehicle changes.
• Telemetry from professional fleets in real operation. That data cannot be bought.
• 100% on-site work in Seville.

What the process looks like

1. Intro call with our team, 30 minutes.
2. Technical conversation about your experience and about Synapse as it stands today.
3. A case: how you would take Synapse to ten times the fleet. Discussed, not submitted.
4. A day in Seville with the team and the founders.

These steps can be completed in ten days.