Chief Digital Systems Engineer

What You'll Do Architectural Vision & Coherence 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 Ensure decisions in one workstream don't create debt in another -- hold the full picture across 8+ concurrent milestones Make the hard architectural calls: technology selection, accreditation-driven design constraints, build vs. buy, when to diverge from common baseline Drive the "build once, deploy per nation" model -- common baseline infrastructure with intentional, late divergence Engineering Standards & Quality Define and enforce the engineering bar: IaC practices, security baselines, deployment patterns, documentation requirements, peer review process Establish RFC-governed decision processes so architectural choices are deliberate, recorded, and reviewable Own reliability and quality improvement -- set measurable targets and drive the team toward them Translate national accreditation requirements (DCSA, IRAP/ISM, NCSC) into engineering work, not paperwork Scale & Reuse Build the common infrastructure patterns that let MDI expand to new nations and classification levels without proportional engineering effort Each subsequent national deployment should be faster than the last -- configuration over engineering Own the module library, deployment templates, and accreditation frameworks that make this possible Prevent the bespoke/incompatible pattern that every other defense company falls into at scale Team Leadership Technical leader for MDI's distributed engineering team across US, UK, and AUS Set direction, mentor IC3-IC5 engineers, review work, raise the bar Define the technical hiring bar and skills framework for MDI engineering roles Establish cross-timezone collaboration patterns that function without requiring you as a bottleneck Division Interface Represent MDI's technical capabilities and constraints to Maritime and (2027+) Maneuver Dominance leadership Shape what's technically possible -- translate engineering reality into program decisions Interface with adjacent technical teams (InfoSec, CorpTech, MTOC, Enabling Technology) on shared concerns What You Bring Required Deep experience designing and building classified network infrastructure across multiple nations or accreditation frameworks Hands-on with sovereign cloud architecture -- not just design, but implementation (IaC, module development, deployment automation) Experience with COMSEC integration, HAIPE/KG-175X, and the intersection of network sovereignty and cryptographic key management Demonstrated ability to set engineering standards for a distributed team and drive adoption without micromanagement Track record of building reusable infrastructure patterns that scale -- not one-off builds that require re-engineering for each deployment Understanding of multinational compliance and accreditation (at least 2 of: DCSA/NIST 800-53, IRAP/ISM, NCSC Cyber Essentials+/OFFICIAL-SENSITIVE) Experience operating as the architectural decision-maker -- not waiting for direction, but setting it Ability to hold both tactical delivery and strategic architecture simultaneously without sacrificing either Preferred Experience in the AUKUS or Five Eyes defense industrial context Familiarity with bilateral/multilateral classified data sharing mechanisms (CDS, policy-controlled release) Background in both network engineering and cloud infrastructure (not just one) Experience with defense accreditation processes from the engineering side -- building systems that pass, not just documenting compliance Prior experience working with or within allied Defence organizations (US DoD, Australian Defence, UK MOD) What Success Looks Like First 90 Days Document MDI's architectural strategy: current state, target state, and gaps Establish RFC/review process for architectural decisions across the team Identify the top 3 reuse opportunities across current national builds and begin codifying them Build relationships with adjacent technical leaders (InfoSec, CorpTech, MTOC, Enabling Technology) First 6 Months Common baseline infrastructure pattern proven across at least 2 nations -- deployment to a new nation demonstrably faster than the first Engineering standards documented and adopted by the team with measurable quality improvement Accreditation engineering approach established -- national frameworks translated into repeatable engineering controls Sovereign cloud and classified network architectures aligned under a single coherent technical strategy First 12 Months MDI's infrastructure model is the reference architecture for how Anduril builds sovereign systems globally Expansion to new divisions scoped and technically ready -- an extension of proven patterns, not a new engineering effort Reliability and quality metrics trending in the right direction with clear ownership Engineering team operating at a higher standard -- evidenced by faster deployments, fewer rework cycles, stronger accreditation posture Technical career path established for MDI engineers with clear growth trajectory How This Role Fits This role works in partnership with the MDI Lead. The MDI Lead owns what we build and why -- stakeholder relationships, program prioritization, BD pipeline, team growth strategy, and cross-division influence. The Principal Systems Engineer owns how it's built and how it scales -- architecture, engineering standards, technical feasibility, capability roadmap, hiring bar, and accreditation engineering. Why This Role Matters Every nation MDI expands to should get faster -- not harder. The Principal Systems Engineer builds the infrastructure once, codifies the pattern, and ensures each subsequent deployment is a configuration change, not a new engineering effort. That's how one team supports multiple divisions and multiple nations without breaking. The salary range for this role is an estimate based on a wide range of compensation fa