Firmware Test Automation Engineer

Firmware Test Automation Engineer

What You'll Do

• Integrate production embedded firmware into a Python-based test framework, building the interfaces and harnesses that drive firmware on target hardware.

• Design and implement automated test execution — replacing manual, ad-hoc validation with repeatable, scriptable flows.

• Build and maintain regression test suites that catch defects early and run reliably across firmware changes and ECU variants.

• Develop full telemetry data acquisition pipelines — capturing signals over CAN, Ethernet, and diagnostic interfaces — and the analysis tooling to turn that data into clear pass/fail and performance insight.

• Implement fault detection, reporting, and logging in the test layer, including capturing DTCs and error indications raised by the firmware and presenting them for triage.

• Manage test control flow — sequencing power-up/shutdown, self-test, load-generation, and fault-injection scenarios, and coordinating state across the device under test and the test bench.

• Exercise firmware diagnostic and self-test functions from the framework — POST, memory/logic BIST, CPU and bus load generation, and voltage-fault handling — by triggering them over CAN, Ethernet, or the diagnostic interface and validating the results.

• Build tooling and utilities that make the test infrastructure faster, more observable, and easier for the wider team to use.

• Collaborate with firmware, hardware, and platform engineers to translate firmware requirements into automated test coverage at unit, integration, and system levels.

What You'll Bring

• 3–8 years of experience in embedded software test automation, firmware integration, or closely related work.

• Strong, hands-on Python development skills — the primary language for this role — including building test frameworks, automation, and data-analysis tooling.

• A solid working understanding of embedded systems: 32-bit microcontrollers (e.g., ARM Cortex-M; automotive processors such as NXP S32G / S32K), RTOS behavior (e.g., FreeRTOS), and how production firmware is structured.

• Practical familiarity with communication protocols used for both firmware operation and test instrumentation — SPI, UART, I2C, CAN at the low level, TCP/UDP at the high level, and UDS diagnostics.

• Experience acquiring, logging, and analyzing telemetry or signal data from embedded targets.

• Working knowledge of C or C++ — enough to read production firmware and reason about its behavior when designing and debugging tests.

• Hardware-in-the-loop or bench experience, including basic use of standard test equipment (oscilloscope, multimeter, power supply) for low-level debugging.

• A structured, quality-first mindset and the ability to work closely with firmware and hardware engineers.