Chief Digital Systems Engineer

About the role

<div class="content-intro"><p>Anduril Industries is a defense technology company with a mission to transform U.S. and allied military capabilities with advanced technology. By bringing the expertise, technology, and business model of the 21st century’s most innovative companies to the defense industry, Anduril is changing how military systems are designed, built and sold. Anduril’s family of systems is powered by Lattice OS, an AI-powered operating system that turns thousands of data streams into a realtime, 3D command and control center. As the world enters an era of strategic competition, Anduril is committed to bringing cutting-edge autonomy, AI, computer vision, sensor fusion, and networking technology to the military in months, not years.</p></div><h2>The Role</h2> <p>Anduril's Multi-National Digital Infrastructure (MDI) team builds and sustains the sovereign cloud, classified networks, edge compute, and coalition interoperability layer that Anduril's products depend on across nations and classification levels. The Principal Systems Engineer is MDI's chief engineer -- owning the technical vision, architectural coherence, and engineering standard for this infrastructure globally.<br><br>This is not a staff role that writes architecture docs and advises. You build. You ship. You set the standard by doing the work and then codifying the pattern so it scales without you in the room.</p> <hr> <h2>What You'll Do</h2> <h3>Architectural Vision &amp; Coherence</h3> <ul> <li>Own the MDI technical architecture end-to-end: sovereign cloud (IL5/IL6), classified bilateral networks, maritime C2 patterns, edge-to-cloud pipelines, and coalition interoperability</li> <li>Ensure decisions in one workstream don't create debt in another -- hold the full picture across 8+ concurrent milestones</li> <li>Make the hard architectural calls: technology selection, accreditation-driven design constraints, build vs. buy, when to diverge from common baseline</li> <li>Drive the "build once, deploy per nation" model -- common baseline infrastructure with intentional, late divergence</li> </ul> <h3>Engineering Standards &amp; Quality</h3> <ul> <li>Define and enforce the engineering bar: IaC practices, security baselines, deployment patterns, documentation requirements, peer review process</li> <li>Establish RFC-governed decision processes so architectural choices are deliberate, recorded, and reviewable</li> <li>Own reliability and quality improvement -- set measurable targets and drive the team toward them</li> <li>Translate national accreditation requirements (DCSA, IRAP/ISM, NCSC) into engineering work, not paperwork</li> </ul> <h3>Scale &amp; Reuse</h3> <ul> <li>Build the common infrastructure patterns that let MDI expand to new nations and classification levels without proportional engineering effort</li> <li>Each subsequent national deployment should be faster than the last -- configuration over engineering</li> <li>Own the module library, deployment templates, and accreditation frameworks that make this possible</li> <li>Prevent the bespoke/incompatible pattern that every other defense company falls into at scale</li> </ul> <h3>Team Leadership</h3> <ul> <li>Technical leader for MDI's distributed engineering team across US, UK, and AUS</li> <li>Set direction, mentor IC3-IC5 engineers, review work, raise the bar</li> <li>Define the technical hiring bar and skills framework for MDI engineering roles</li> <li>Establish cross-timezone collaboration patterns that function without requiring you as a bottleneck</li> </ul> <h3>Division Interface</h3> <ul> <li>Represent MDI's technical capabilities and constraints to Maritime and (2027+) Maneuver Dominance leadership</li> <li>Shape what's technically possible -- translate engineering reality into program decisions</li> <li>Interface with adjacent technical teams (InfoSec, CorpTech, MTOC, Enabling Technology) on shared concerns</li> </ul> <hr> <h2>What You Bring</h2> <h3>Required</h3> <ul> <li>Deep experience

Skills