Firmware Test Engineer II

We build electric motorcycles. The ride feels simple and alive. The rest should be too.

We are not there yet. You will help us get there.

The Product Experience ( P.Ex ) organization is responsible for how the motorcycle feels to use. We design and build the firmware that runs on the bike, the dash the rider sees, the mobile app they carry, the diagnostic tools used in the field, and the cloud systems that connect them.

The Firmware Products team, within the P.Ex org, is responsible for delivering the behaviour of the motorcycle itself. The team spans firmware development, battery performance engineering, and test engineering, owning the full value chain from firmware requirements to field validation. Every safety decision, performance characteristic, and response the bike makes to the rider runs through this system. Riders love and trust it.

We are looking for a Firmware Test Engineer who will help the team deliver firmware that protects the rider, honours their trust, and preserves the response and thrill that make it worth riding.

What You Will Do

• Build and maintain automated tests that verify firmware behaviour across the battery management system, motor controller, display, and other vehicle subsystems.
• Validate CAN and UART communication used for vehicle behaviour, configuration, and diagnostics. Flag regressions early, and make failures clear enough to reproduce and act on quickly.
• Shorten the feedback loop between a firmware change and confidence in that change. Expand functional, boundary, regression, and failure-mode coverage, and help improve our HIL and SIL environments so more problems are found before firmware reaches a motorcycle.
• Use logs, telemetry, lab equipment, and firmware instrumentation to reconstruct unexpected behaviour. Turn field incidents into reproducible tests and improved coverage so failures become easier to catch.
• Look beyond the immediate bug. Ask what it reveals about our assumptions, test strategy, instrumentation, interfaces, or architecture, and help improve the system that allowed it to escape.
• Work with firmware, BMS, vehicle architecture, service, production, and product teams to understand intended behaviour, rider impact, risk, and the evidence needed before a change is ready.
• Bring a test engineering perspective to requirements, design discussions, and code reviews. Raise unclear behaviour early, challenge assumptions with evidence, and help prevent problems before they are built.
• Communicate directly and respectfully with engineers across the Netherlands, US, and India. Coordinate across time zones, write useful findings, provide the right context, and treat debugging as a shared effort to understand the system rather than assign blame.
• Use AI tools to explore unfamiliar code, generate test ideas, diagnose failures, and identify coverage gaps. Verify their output against the code, the system, and observed behaviour, and apply sound judgment in a safety-critical environment.