Robotics Software Engineer, Test Infrastructure (SITL/HITL)

Job description

Job responsibilities

• Own and grow our SITL environments: add product variants and scenarios, keep the simulated sensor and video pipelines faithful enough to be trustworthy, and keep whole-system test runtimes short enough to fit inside a…
• Build out functional coverage on the HITL bench across the behavior that matters: motion control and trajectory execution, camera and sensor bring-up, firmware update paths, network failover, and clean recovery from…
• Own the CI integration end to end: scheduling, dependency chaining between test stages, artifact and log capture, result reporting, and the flake triage that keeps a hardware pipeline trusted instead of ignored.
• Grow the test platform continuously as the product line does. New compute generations, new payloads, and new product variants each need coverage, and keeping the framework ahead of the roadmap is the enduring core of…
• Make failures diagnosable without touching the rig. Invest in log capture, serial console capture, and test artifacts so an engineer can root-cause from the CI output alone.
• Partner with hardware and manufacturing engineers to stand up the physical HITL benches, specifying the fixtures, switching, power control, and instrumentation needed to exercise towers unattended.
• Partner with firmware, platform, and business line teams so they can add their own tests against your framework, and support them as their first users.

Job requirements

• 4+ years of professional software engineering, with meaningful time spent building test infrastructure, CI systems, or simulation for systems that involve real hardware.
• Proficiency in Python for test authoring and automation, plus working ability in Rust or C++ to read and debug the services under test.
• Demonstrated experience automating tests against physical hardware: device provisioning, remote power and reset control, serial consoles, network booting, or instrumented benches.
• Strong CI/CD engineering skills, including pipelines with expensive stages, hardware resource contention, and scheduled rather than per-commit execution.
• Experience with declarative configuration and reproducible builds. Nix or NixOS is what we use and what we most want to see;
• Solid Linux systems fundamentals: systemd, networking, filesystems, and boot, since most of what you automate is a Linux system misbehaving.
• The judgment to know which tests are worth their cost, and the discipline to fix or delete a flaky test rather than tolerate it.
• US person status required, with eligibility to obtain and maintain a US security clearance.