Sr. Mission Software Engineer - Undersea Reconnaissance & Strike
Anduril Industries · Quincy, Massachusetts, United States
About this role
## About Anduril Anduril Industries is a defense technology company transforming U.S. and allied military capabilities with advanced technology. Anduril’s family of systems is powered by **Lattice OS**, an AI-powered operating system that turns thousands of data streams into a real-time, 3D command and control center. Anduril Maritime builds autonomous underwater/surface vehicles—**autonomy computers**, **payload computers** (driving sonar and other sensors), **surface integration units**, and **ground control stations**. Vehicles are already in the field, and field-reported bugs are real and immediate. This role’s day-one mission: **pick up field bugs and actually close them**—reproduce, find the real cause, fix it, ship it, and communicate what happened. ## What this is (and isn’t) - **Not** a ticket-triage-and-forward job. - **Not** “junior dev does the boring work while senior devs build features.” You’ll be shipping **real fixes in the real codebase**, entering through “this broke on a vehicle” rather than a clean feature spec. As you build cross-subsystem fluency, you’ll move into **owning subsystems and roadmap work**. ## 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’s actually in**. - **Reproduce** the issue for real by replaying recorded sensor/mission data through the live pipeline and using visualization tooling—**no guessing**. - Use existing **metrics and log infrastructure** (per-service metrics, dashboards, 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 touching real vehicles. - Implement fixes in the subsystem’s language (**Rust, C++, Python, Go, etc.**) with **tests**, through **CI**, and via the normal **versioned rollout**. - Determine whether the root issue is a **bug, bad config, or deployment mismatch**, and fix it at the layer where it truly lives. - Document **root cause and fix** for every issue you close—so the team can track which subsystems keep breaking and which tests are missing, and help build the on-call/triage runbook.
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.