Electronics or Systems Engineering internship

Our vehicles carry a control unit, communication buses, sensors and an HMI, and above them Synapse, which runs maintenance, routing and cost for customer fleets. You will work where those two meet: writing and testing code on the actual electronics, capturing telemetry and helping to work out what it is telling us.

The difference from a coursework project is what happens when it is wrong. Code that behaves perfectly on a bench can fail on a route because of vibration, damp or a connector. You will watch that happen, with a senior engineer next to you, and you will learn to debug something you cannot pause.

Responsibilities

• Write and test code on the vehicle's electronics, on real hardware.
• Help capture, clean and analyse telemetry from vehicles in operation.
• Support the agent team on integration between the vehicle and Synapse.
• Document what you build and what failed, so the next person does not repeat it.

• Studying electronics, telecommunications or computer science, with a university internship agreement in place.
• Fluent programming in at least one language, and an appetite for touching hardware.
• Comfortable with a command line, version control and documentation in English.
• Based in Seville or willing to relocate.

Counts in your favour

• Personal projects with microcontrollers, sensors or robotics.
• Any exposure to C, C++ or Python on embedded hardware.

You will fit here if

• You want your code moving something physical rather than sitting in a repository.
• Debugging interests you more than getting a first version working.
• Here you will be given real work before you feel ready for it, and that unsettles a lot of good students.
• You would rather ask than guess when something is not clear.

• Your code running on vehicles in the city, not sitting in a drawer.
• Direct mentoring from the engineers who built the vehicle and the software.
• A real chance of joining the team afterwards.
• 100% on-site work in Seville.

What the process looks like

1. Intro call with our team, 30 minutes.
2. Technical conversation about something you have programmed, ideally with hardware attached.
3. A morning in Seville with the team and the test rig.

These steps can be completed in ten days.