> Markdown version of [/jobs/ext/4604274-autonomy-embedded-engineer](https://www.wearedevelopers.com/jobs/ext/4604274-autonomy-embedded-engineer). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Autonomy Embedded Engineer

- **Company:** Joby Aviation
- **Location:** Santa Cruz, CA, United States
- **Experience:** Expert
- **Salary:** $136,100.0 - $202,600.0
- **Contract:** Permanent contract
- **Skills:** Automation of Tests, Unit Testing, C++ (Programming Language), Computer Engineering, Continuous Integration, Software Debugging, Linux, Linux on Embedded Systems, Ethernet, Github, Hardware-In-The-Loop Simulation, Python (Programming Language), Universal Asynchronous Receiver/Transmitter, Serial Peripheral Interface, Software in the Loop, Information Technology, Jenkins
- **Published:** November 6, 2026
- **Apply:** https://www.juju.com/job/7_9134B70D868AC2384DA991F7EB18F82A

## About the Role

University degree in computer science, computer engineering, electrical engineering, mechatronics, or a similar field; or a strong portfolio of embedded / test-automation software and 5+ years relevant industry experienceStrong C++ and Python, and fluency with GitExperience building or maintaining hardware in the loop or comparable automated test infrastructure that runs real embedded hardware in CIWorking knowledge of embedded communication buses (CAN, UART/RS-485, I2C, SPI, or similar) at the level needed to debug them with a scope or logic analyzerUnderstanding of real-time and safety-critical software concepts: deterministic fixed-rate execution, timing budgets, redundancy, and what makes a test of such a system trustworthyExperience with a hermetic build system (Bazel or equivalent) and a CI system (Buildkite, Jenkins, GitHub Actions, or equivalent)Experience with Linux, including remote deployment and debugging on embedded Linux targetsA passion for clean, long-lived, and
readable object-oriented software architecture. Not just working code, but code built to survive years of extension by other engineersThis position must meet US export control compliance requirements, therefore a candidate must qualify as a "US Person" as defined by 22 C.F.R. § 120.15. "US Person" includes US Citizens, lawful permanent residents, refugees, or asylees.

## Description

Joby's Advanced Development group is looking for an engineer to own and grow our hardware-in-the-loop and test-automation capability for novel aircraft and flight automation systems.This role is responsible for the fidelity, coverage, and reliability of the pipeline that allows us to test all new changes to our redundant compute system ahead of deployment.You will work closely with the core software team, flight controls, avionics, and flight test engineers who depend on this infrastructure.We're looking for someone who thrives in fast-paced environments, takes full ownership of infrastructure the whole flight software org relies on, and consistently delivers high-impact results., Develop and maintain the test infrastructure, fault injection frameworks and annunciation mechanisms required for in-the-loop testingDevelop software in the loop, hardware in the loop and aircraft in the loop simulation infrastructure: in-the-loop scenario runner, simulated peripherals, and per mode configurationBring up, debug, and maintain the physical HITL rigs, and keep rig hardware and configuration matched to the real aircraft they stand in forBuild and extend hardware-CI pipelines that deploy flight software to rig hardware and run pass/fail, timing, and platform-log checks automatically, with results stored for trend trackingWrite and maintain Bazel-based C++ and Python scenario and unit tests, including property-based tests, that exercise the flight software against realistic sensor, actuator, timing, and network-transport conditionsIntegrate new sensors and actuators into both the simulated and hardware-in-the-loop environments over their native buses (CAN, UART/RS-485, I2C, SPI,
ARINC 429, Ethernet)Triage rig and CI failures: separate simulation-fidelity gaps from rig hardware faults from real flight-software bugs, and drive each to the right owner with a reproducible caseWork with flight test and controls engineers to convert observed flight behavior into repeatable in-the-loop scenarios, closing the loop between flight data and pre-flight validation