SlipstreamJobs tracks this role from the company's public career site. Apply directly on the employer's site.
Salary: USD 166,000 - 220,000 / annual
Anduril Industries is a defense technology company building advanced military systems powered by Lattice OS, an AI-powered operating system for real-time command and control. The Imaging team develops state-of-the-art camera and sensor systems deployed across the full stack—from bare-metal hardware and firmware to networked services and cloud integrations.
As a Mission Software Engineer on the Imaging Interfaces team, you will own the health and uptime of deployed imaging systems in the field. This is not a pure product development role. You will spend meaningful time keeping fielded systems alive, triaging issues across the full stack, and serving as a technical representative for products in integrations with external teams and customers.
Key responsibilities include:
• Own fielded system success: You are responsible for the health and uptime of deployed imaging systems. When issues arise—whether in code, firmware, network, or hardware—you triage, diagnose, and drive resolution.
• Build and maintain production services: Develop and extend modular software services running on edge-compute devices in austere environments. Services must be reliable, observable, and maintainable by engineers who didn't write them.
• Support field operations: Work directly with field operators and non-technical users to diagnose and resolve issues on deployed hardware. Clear communication under pressure is essential.
• Represent the team externally: Serve as a subject matter expert in integrations with other products and teams, sometimes remotely and sometimes on-site. Speak credibly across the full system stack.
• Maintain end-to-end system understanding: Develop broad fluency across hardware, firmware, networking, and software. Apply this knowledge to optimize how services interact and degrade gracefully when components fail.
• Collaborate across teams: Plan, build, and test complex functionality alongside firmware, hardware, and platform engineers. Work effectively across team and organizational boundaries.
The work is varied and sometimes ambiguous. You might spend a morning extending a gRPC service, an afternoon diagnosing a time sync issue on a deployed device over the phone with a field operator, and a week traveling to support a customer integration. Travel is expected approximately 25% of the time for field testing and customer integrations.
Successful engineers in this role close loops (owning problems until resolved), communicate proactively, are comfortable with ambiguity at the stack boundary, and represent the team well externally.
**REQUIREMENTS**
Required:
• 3+ years of software development with meaningful production ownership—not just shipping features, but owning systems after they ship (their health, uptime, and behavior in users' hands)
• Deep proficiency in at least one of C++, TypeScript (Node.js/React), or Python, and the ability to work effectively across the stack boundary in a second language (reading, debugging, and modifying code outside your primary). Work spans TypeScript/React operator-facing UI and growing C++ services on edge hardware; C++ depth is increasingly central.
• Comfort ramping quickly into unfamiliar languages, tools, and deployment systems. Language and tooling mix varies by product and shifts over time.
• 3+ years working in Linux-based environments, including hands-on work with bare-metal hardware
• Demonstrated ability to diagnose and resolve issues across system boundaries (networking, services, hardware interaction) without always having full visibility into every component
• Strong written and verbal communication skills, including the ability to explain technical problems clearly to non-technical audiences, including field operators
• Eligibility to obtain and maintain a U.S. Secret clearance
Preferred:
• Strength with performance-sensitive, real-time, or resource-constrained systems (edge or embedded)
• Experience with gRPC or similar RPC frameworks
• Familiarity with systemd service management and observability practices on Linux
• Familiarity with Nix or NixOS (uncommon but genuinely valuable; used daily on the stack)
• Experience supporting fielded or deployed systems, not just development environments
• Experience with imaging, EO/IR, ISR, or command-and-control (C2) systems
