Vehicle Software Engineer

Own the architecture, implementation, and maintenance of vehicle software capabilities across onboard computers and ground systems, with clear contracts for commands, telemetry, state, and failure behavior.  

Build operator interfaces and ground-station workflows for vehicle preparation, preflight checks, mission control, health monitoring, and intervention. Make vehicle state, command outcomes, and required operator actions clear.  

Develop mission planning and execution software that turns operational goals into validated flight paths and geofences, accounts for vehicle endurance, coordinates flight and seeding activity, and supports mission changes as conditions evolve.  

Design and validate arming checks, interlocks, and failsafe behaviors for communication loss, degraded sensing, low power, process failures, and unexpected vehicle states, including clear transitions between autonomous behavior and operator control.  

Integrate sensors, cameras, and seeding payloads with onboard software and flight-control systems. Ensure measurements, calibration, timestamps, device health, and payload commands are reliable and observable.  

Develop autonomy that uses sensing and vehicle state to execute missions within operating limits, handle contingencies, and reduce operator workload.  

Build dependable communication between vehicles and ground stations, accounting for intermittent links, stale telemetry, and commands that may be delayed, duplicated, or unacknowledged.  

Build automated tests, software-in-the-loop simulation, and hardware-in-the-loop coverage that catch regressions and exercise failure modes before releases reach the fleet.  

Partner with hardware engineers and flight operations to validate new capabilities on the bench and in flight, and make deployment, configuration, calibration, and diagnostics repeatable.  

Investigate field failures using logs, telemetry, and mission replay; resolve root causes and turn what you learn into better software, tests, and operator workflows.

3+ years of hands-on experience developing software for vehicles, robotics, or other systems that interact with the physical world, including deployment into production or field use.  

Demonstrated ownership of a software capability from design through integration, release, and ongoing support, including making technical decisions independently and resolving failures in real operating conditions.  

Strong systems programming skills in Rust or C/C++, with the willingness to work primarily in Rust and contribute to TypeScript-based operator interfaces. Our stack includes Rust onboard services and ground-station backends, React/TypeScript interfaces in Electron, and PX4 flight-control integration over MAVLink.  

Experience developing and debugging software on Linux, including concurrent processes, network communication, and interfaces to hardware or flight-control systems.  

Practical experience in one or more of the following: operator interfaces and ground stations, mission planning, autonomy, sensing, or payload integration, with the willingness to work across these boundaries.  

The ability to reason about distributed system state, timing, and failures, and implement robust state machines, fault detection, failsafes, and recovery paths.  

A practical approach to operator-facing software: you can turn field workflows into clear controls, useful feedback, and predictable system behavior.  

Experience building maintainable software with version control, reproducible builds, automated testing, and disciplined release practices.  

Evidence of high agency: you surface problems without waiting to be assigned, make sound decisions with incomplete information, ask for help when it matters, and close the loop on results.  

Clear communication and the ability to work closely with hardware engineers and operators, explain tradeoffs, and document decisions so others can operate and support what you ship.

Experience deploying drones or autonomous robots and supporting real-world flight or field operations.  

Familiarity with PX4, MAVLink, ground-control systems, or flight-critical software.  

Experience building operator interfaces with React, TypeScript, or Electron, particularly mapping tools or geospatial mission-planning workflows.  

Experience with sensor fusion, state estimation, path planning, or autonomous mission execution.  

Experience integrating payloads, sensors, or embedded controllers over interfaces such as CAN, serial, or Ethernet.  

Experience validating safety-related behaviors through simulation, hardware-in-the-loop testing, fault injection, and field testing.