SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Anduril Industries is seeking a Mission Software Engineer to join the Maritime division, which builds autonomous underwater and surface vehicles. This role focuses on field-driven debugging and root-cause resolution for production systems already deployed in real-world conditions.
You will own the full lifecycle of bug investigation and resolution: taking field-reported anomalies (sensor failures, mission faults, data drift), reproducing them using recorded sensor and mission data, leveraging existing metrics and logging infrastructure to reconstruct system state, and shipping real fixes through the normal CI/CD pipeline. You'll work across multiple subsystems written in Rust, C++, Python, and Go, confirming fixes in simulation and hardware-in-the-loop environments before deployment to real vehicles.
Key responsibilities include diagnosing whether issues are bugs, configuration problems, or deployment mismatches; writing clear root-cause documentation to identify systemic gaps; and pushing back to owning teams when subsystems need architectural changes rather than symptom patches. You'll help build the on-call and triage runbooks the team currently lacks.
This is positioned as a genuine entry point into the codebase and organization. Success here—building cross-subsystem fluency through production debugging—leads to subsystem ownership and roadmap work. The role explicitly rejects the "junior does boring work" model; you ship real fixes in the real codebase from day one.
Required: proven experience debugging unfamiliar code under time pressure with incomplete information; comfort reading and fixing bugs in at least two of Rust, modern C++, Python, or Go; systems-debugging instincts (logs, metrics, offline reproduction); hands-on experience with observability tools (Prometheus/Grafana, Loki/ELK); Linux and systems fluency; clear technical writing; willingness to work close to hardware and sensors; 25%+ travel availability.
Nice-to-have: robotics middleware, sensor drivers, real-time data pipeline experience, simulation-in-the-loop or hardware-in-the-loop testing, CI/CD and versioned deployment for embedded/fleet software, on-call or field-support experience.
