Mission Software Engineer - Undersea Reconnaissance & Strike
Anduril Industries · Quincy, Massachusetts, United States
About this role
## Anduril Industries — Mission Software Engineer (Undersea Reconnaissance & Strike) Anduril is a defense technology company transforming U.S. and allied military capabilities with advanced technology. Anduril’s systems are powered by **Lattice OS**, an AI-powered operating system that turns thousands of data streams into a real-time, 3D command and control center. ### About the role Anduril Maritime builds autonomous underwater/surface vehicles, including autonomy computers, payload computers (e.g., sonar and other sensors), surface integration units, and ground control stations. This role is focused on **closing real field bugs**—starting day one. You’ll pick up anomalies reported from vehicles, reproduce them, identify the true root cause, implement fixes, validate them (including hardware-in-the-loop where needed), and ship them through normal CI/versioned rollout. > Not a ticket-triage-and-forward job. Not “junior dev does boring work.” You’ll ship real fixes in the real codebase. ### What you’ll actually be doing - Take a **field-reported anomaly** (e.g., sensor stopped publishing, mission faulted mid-track, data stream drifted) and determine **which subsystem** it truly belongs to. - **Reproduce it for real** by replaying recorded sensor/mission data through the live pipeline and using visualization tooling. - Use existing **metrics, dashboards, and centralized logs** to reconstruct system state at the moment things went wrong. - Confirm fixes in a **simulated environment first**, and use **hardware-in-the-loop** where it matters before deploying to real vehicles. - Write fixes in the **actual language** used by the subsystem (**Rust, C++, Python, Go,** etc.), with tests through **CI** and out via normal versioned rollout. - Determine whether the issue is a **bug, bad config, or deployment mismatch**, and fix it at the correct layer. - Document **root cause and the fix** for every issue you close—so the team can track recurring subsystem failures and improve missing tests and runbooks.
Listing freshness
CronJobs last confirmed this listing 1d ago. If its source stops confirming the opening for seven days, this page is removed from active inventory.