Mission Software Engineer Undersea Reconnaissance & Strike

Anduril Maritime builds autonomous underwater/surface vehicles: autonomy computers running control and mission logic payload computers driving sonar and other sensors surface integration units and ground control stations. Were past the does it work in the lab phase - vehicles are in the field and field vehicles find bugs the lab never does. We need someone whose job starting day one is to pick up those bugs and actually close them: reproduce it find the real cause fix it ship it tell the team what happened.

To be clear about what this isnt: its not a ticket-triage-and-forward job and its not junior dev does the boring work while senior devs build features. Youll be shipping real fixes in the real codebase. Youre just entering the codebase through this broke on a vehicle instead of heres a clean feature spec. Once youve built up cross-subsystem fluency - which this role forces faster than sitting in one subsystem ever would - you move into owning subsystems and roadmap work like anyone else.

What youll actually be doing

• Take a field-reported anomaly (sensor stopped publishing mission faulted mid-track data stream drifted for no obvious reason) and figure out what subsystem its actually in - not just where it was reported.
• Reproduce it for real. Replay recorded sensor/mission data through the live pipeline pull it into visualization tooling dont guess.
• Use the metrics and log infrastructure that already exists (per-service metrics dashboards centralized logs) to reconstruct system state at the moment things went wrong instead of re-running until you get lucky.
• Confirm the fix in a simulated environment first hardware-in-the-loop where that matters before it goes anywhere near a real vehicle.
• Write the fix in whatever language the subsystem actually uses - Rust C Python Go whatever with tests through CI out through the normal versioned rollout. No special triage shortcut path.
• Figure out whether the actual problem is a bug a bad config or a deployment mismatch and fix it at the layer where it actually lives instead of patching around it one level up.
• Write down root cause and fix for every issue you close. Not for the paperwork so we can see over months which subsystems keep breaking and which tests were missing. Help build the on-call/triage runbook this team doesnt have yet.
• Push back to the owning team when the real fix is this subsystem needs to change not patch the symptom and move on.

What you need to already have

• Real experience debugging code you didnt write under time pressure with incomplete information. This matters more than which language you know best.
• Enough comfort in at least two of Rust modern C Python Go to read and fix bugs in them. You dont need to be an expert in all four - you need to not freeze up when youre dropped into one you know less well.
• Systems-debugging instincts: pull logs and metrics reconstruct what happened reproduce offline from recorded data instead of only live.
• Some real exposure to observability tooling (Prometheus/Grafana-class metrics Loki/ELK-class logs) you should already know how to use this stuff not learn it here.
• Linux and systems fluency. Bonus if youve touched declarative/immutable OS setups (NixOS-style).
• The ability to write up what actually happened clearly without padding it out or burying the cause. The vehicle did something weird is not an acceptable final answer from you.
• Willingness to work close to hardware and sensors even if youve never touched maritime or robotics before. Were not looking for domain background were looking for the debugging instinct.
• Willingness to travel 25% of the time on average

Nice to have not required

• Robotics middleware sensor drivers or real-time data pipeline experience (sonar radar lidar whatever).
• Time in simulation-in-the-loop or hardware-in-the-loop test setups.
• CI/CD and versioned deployment experience for embedded or fleet software.
• Actual on-call or field-support experience for hardware that ships to real users not just internal tools.

Where this goes

• This is a real entry point not a holding pen. Do this well and youll know more of the stack than most people who joined doing greenfield feature work and thats exactly who ends up owning subsystems and driving roadmap next.

The salary range for this role is an estimate based on a wide range of compensation factors inclusive of base salary only. Actual salary offer may vary based on (but not limited to) work experience education and/or training critical skills and/or business considerations. Highly competitive equity grants are included in the majority of full time offers; and are considered part of Andurils total compensation package. Additionally Anduril offers top-tier benefits for full-time employees including:

At Anduril we invest in our people. Our comprehensive competitive benefits package (available at little to no cost to employees) ensures youre supported in health recovery and whatever comes next.For more information Explore Our Benefits.

To view Andurils candidate data privacy policy please visit submitting your application you consent to Anduril Industries using a third-party service provider to conduct pre-employment risk integrity and due diligence screening and assessing potential risks as part of your application process. This third-party service provider provides risk-intelligence services that may include analysis of sanctions and watchlists adverse media public-record information and other lawful open-source or commercial data sources. This third-party service provider does not act as a consumer reporting agency. Use of this provider helps to ensure compliance with applicable laws and protect technology intellectual property and organizational security.