SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Anduril Industries is a defense technology company building autonomous underwater and surface vehicles powered by Lattice OS, an AI-driven command and control system. The Maritime division develops autonomy computers, payload computers for sonar and sensors, surface integration units, and ground control stations. These systems are already deployed in the field, and this role focuses on closing real bugs discovered during field operations.
As a Mission Software Engineer, you'll own the full lifecycle of field-reported anomalies: reproduce sensor failures or mission faults, use existing metrics and logging infrastructure to reconstruct system state, confirm fixes in simulation and hardware-in-the-loop environments before deployment, and write fixes across the codebase (Rust, C++, Python, Go) with proper tests and CI/CD. You'll determine whether issues are bugs, configuration problems, or deployment mismatches, and fix them at the correct layer rather than patching symptoms. You'll document root causes and help build the on-call and triage runbooks the team currently lacks, pushing back when subsystems need architectural changes rather than quick workarounds.
This is positioned as a genuine entry point into the broader codebase. Success here builds cross-subsystem fluency faster than greenfield feature work, leading to subsystem ownership and roadmap responsibilities. The role requires 25%+ travel on average.
You need real experience debugging unfamiliar code under time pressure with incomplete information. Proficiency in at least two of Rust, modern C++, Python, or Go is required; you don't need to be expert in all four but must be comfortable reading and fixing bugs across languages. Systems-debugging instincts are essential: pull logs and metrics, reconstruct what happened, replay recorded data offline. You should already know observability tooling (Prometheus/Grafana, Loki/ELK). Linux and systems fluency are required; NixOS-style declarative OS experience is a bonus. Clear technical writing is non-negotiable. Willingness to work close to hardware and sensors is required, though maritime or robotics domain background is not.
Nice-to-have skills include robotics middleware, sensor drivers, real-time data pipeline experience (sonar, radar, lidar), simulation-in-the-loop or hardware-in-the-loop test setups, CI/CD and versioned deployment for embedded or fleet software, and on-call or field-support experience for shipped hardware.
