Embedded Software Test Engineer
✓
Which company are you aiming at?
To generate precise rejection-prevention feedback and application strategy, tell us where you're targeting.
2
Send your application
You need an account so we know where to send the feedback.
The job description
Tech stack. Python, C test hooks, HIL test rigs, pytest, CI for firmware, fault injection, code coverage (gcov/lcov), protocol simulation
About the role
You will join an electric vehicle charging company where firmware bugs strand drivers and damage expensive hardware. The embedded test team owns the test strategy that stands between the firmware team and the field: HIL rigs, automated regression, and the fault injection that proves the system handles the worst day, not just the best. This role matters because charging hardware operates at lethal voltages in public spaces, and the test team is the last line of defense.
What you will achieve
- Ship an automated HIL regression suite covering 90% of the charger's firmware behavior, running on every commit with results in under 30 minutes, and flaky-test tracking that keeps the suite trustworthy
- Drive escaped-defect rates down 50% year over year by building fault-injection campaigns (CAN errors, sensor failures, power glitches) into the release gate
- Reduce manual test time per release from two weeks to two days through automated protocol conformance testing (OCPP, ISO 15118) with machine-readable reports
- Build a fleet telemetry feedback loop that converts field anomalies into regression tests within one sprint, closing the loop between the field and the lab, with coverage reviewed in the release retrospective
- Own the test coverage strategy, holding the firmware team to 85% line coverage on safety-relevant modules with trend reporting reviewed at every release
What you will bring
Must-haves
- 2-5 years testing embedded software: writing test plans, building automation, or operating HIL rigs for shipping products
- Strong Python for test automation, plus enough C to read firmware and add test hooks where needed
- Experience with hardware-in-the-loop testing: real-time simulation, signal injection, and fault insertion
- Familiarity with CI systems adapted for firmware: artifact flashing, target farms, and result triage at scale
- Knowledge of test design for embedded: boundary values, state machine coverage, and timing/concurrency testing
- Experience with protocol testing and simulation for CAN, Modbus, or application-layer protocols
- A skeptical mindset: you assume the code is guilty until the test proves otherwise, and you write the test that proves it
Nice-to-haves
- Experience with property-based or model-based testing applied to firmware
- Knowledge of functional safety testing expectations, even without formal certification
- Familiarity with power electronics test safety practices for high-voltage test setups
Apple
NVIDIA
Tesla
Qualcomm
Bosch
Garmin