SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Anduril Maritime is seeking a Senior Mission Software Engineer to own field-reported bugs and anomalies in autonomous underwater and surface vehicles. This is not a junior triage role—you'll reproduce issues, diagnose root causes, and ship real fixes in the production codebase across multiple subsystems (Rust, C++, Python, Go).
Day-to-day responsibilities include: taking field-reported anomalies (sensor failures, mission faults, data drift) and determining which subsystem is actually responsible; reproducing issues using recorded sensor/mission data and live pipelines; leveraging existing metrics, dashboards, and centralized logs to reconstruct system state; validating fixes in simulation and hardware-in-the-loop before deployment; writing fixes through normal CI/CD and versioned rollout processes; determining whether issues are bugs, misconfigurations, or deployment mismatches and fixing at the correct layer; documenting root causes and fixes to identify systemic gaps and improve on-call runbooks; and pushing back to owning teams when subsystem changes are needed rather than patching symptoms.
You'll 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. Strong systems-debugging instincts are essential: pulling logs and metrics, reconstructing what happened, reproducing offline from recorded data. Prior exposure to observability tooling (Prometheus/Grafana, Loki/ELK) is required. Linux and systems fluency are mandatory; NixOS-style declarative/immutable OS experience is a bonus. You must write clear, concise root-cause analyses without padding. Willingness to work close to hardware and sensors is expected, though maritime or robotics domain background is not required. Travel 25%+ of the time on average.
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/fleet software, and on-call or field-support experience for hardware shipped to real users.
This role is a genuine entry point into broader system ownership. Success here builds cross-subsystem fluency faster than greenfield feature work, positioning you to own subsystems and roadmap work.
