Principal Technical Program Manager, Infrastructure Engineering

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must not include Job ID etc. Remove boilerplate like EEO, scam warnings, legal, navigation, cookie, etc. Must preserve all substantive info. We need to parse the posting. Content: - Intro paragraph about Anduril (mission). That's about the company, maybe part of About the role? The instruction: "About The Role" heading. So we can put that intro under About the role. - Then "About The Role" section: description of role, three primary capacities. - Then "What You'll Do" with subsections: Chief of Staff Function & Strategic Leadership (~15%), Operational Excellence (OE) & Resilience (~25 - 35%), Flagship Special Programs (~50%). Those are responsibilities. - Then "Required Qualifications" list bullet points. - Then "Preferred Qualifications" bullet points. - Then "US Salary Range $220,000—$292,000 USD". That's Pay. - Then "Benefits" paragraph: description of benefits, equity grants, top-tier benefits, link to Explore Our Benefits. So we have Benefits. - No explicit Schedule info. So we should not create Schedule section. - Skills? Not explicitly listed; maybe we can infer from qualifications but we should not invent. So we may omit Skills section if no explicit skills list. The instruction: "Prefer a few substantive sections over many thin ones." So we can combine Requirements and Qualifications? Actually they said use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have: - About the role: includes intro and role description. - Responsibilities: we have What You'll Do with subpoints. - Requirements: maybe Required Qualifications. - Qualifications: maybe Preferred Qualifications? Or we could treat Required as Requirements and Preferred as Qualifications. Or combine both under Qualifications? The instruction says we can include sections only when posting has real specific content. So we can have both Requirements and Qualifications if they have content. - Skills: not explicit; maybe we could omit. - Benefits: yes. - Pay: yes. - Schedule: none. Thus output sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use

for each section heading. Inside each section, use

for prose,

• for lists. We must preserve all substantive information; do not invent or summarize away detail. We need to include the details exactly as given, but we can format. We must not include boilerplate like "Protecting Yourself from Recruitment Scams", "Data Privacy", etc. Also remove "Explore Our Benefits" link? That's part of benefits description; we can keep the sentence but maybe drop the link? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Explore Our Benefits" is a link; it's not boilerplate but could be considered navigation? It's a link to benefits page; maybe we keep it as part of benefits description? It's not application instruction. It's a reference. Might be okay to keep. However, the phrase "For more information, Explore Our Benefits." is like a call to action; could be considered application instruction? It's not exactly applying. Might be safe to keep but maybe better to drop as it's a navigation link. The instruction says remove navigation. So we should drop that line. Also remove "Protecting Yourself from Recruitment Scams" etc. Also remove "Data Privacy" section. Also remove "By submitting your application..." etc. Also remove "Use of this provider helps to ensure compliance..." etc. Also remove "Highly competitive equity grants are included in the majority of full time offers; and are considered part of Anduril's total compensation package." That's part of benefits; we keep. Also remove "At Anduril, we invest in our people. Our comprehensive, competitive benefits package (available at little to no cost to employees) ensures you’re supported in health, recovery, and whatever comes next." That's benefits description; keep. Now let's extract substantive content. Intro paragraph: "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." That's about the company; we can put under About the role. Then "About The Role" heading: we already have About the role section; we can include the role description: "We are seeking a Principal Technical Program Manager (TPM) reporting to the Head of Infrastructure Engineering to lead mission-critical, high-visibility engineering initiatives across the company. In this role, you will operate at the intersection of technical depth, executive leadership, and operational execution. Specifically, you will function in three primary capacities as Chief of Staff (~15%) to the department head—driving strategic planning, org-wide operating cadences, executive alignment, and unblocking critical internal engineering efforts. Simultaneously, you will own InfraEng’s Operational Excellence (OE) charter (~25 - 35%) across Cloud, Platform, Networking, and Datacenter/On-Prem functions, driving rigor throughout the organization to ensure enterprise-grade reliability and QOS paces our audacious expansion and growth. You will also directly quarterback high-visibility flagship programs (~50-60%) —ranging from critical reliability and resilience efforts, cross-cutting architectural migrations, and manufacturing enablement." That's the role description. Then "What You'll Do" with subsections. We need to turn that into Responsibilities section with list items maybe. We can break into three bullet groups: Chief of Staff Function & Strategic Leadership (~15%), Operational Excellence (OE) & Resilience (~25 - 35%), Flagship Special Programs (~50%). Each with subpoints. We need to preserve all detail. Let's extract each subsection content. Chief of Staff Function & Strategic Leadership (~15%): - Curating the rhythm that produces speed, accuracy, executive sponsorship and trust: Partner directly with the Head of Infrastructure Engineering to translate organizational vision into prioritized technical roadmaps, resource allocations, and cross-team execution plans. - Execute and continuously tune the department's operational rhythm, including executive business reviews, operational reviews, and C-level briefings spanning complex engineering initiatives. - Drive cross-functional alignment and unblock dependencies across InfraEng in order to deliver value greater than the sum of individual teams/capabilities. - Spearhead strategic initiatives, vendor and service provider restructurings, and cost-optimization programs to maximize efficiency without compromising security or deployment velocity. Operational Excellence (OE) & Resilience (~25 - 35%): - Defining, measuring and continuously improving the processes and technologies that achieve unreasonably high SLOs, SLAs and QoS. - Define, launch, scale and measure Operational Excellence (OE) processes and mechanisms across all networking, cloud, platform, and datacenter functions. - Identify and scope tooling and automation opportunities that continuously lessen human intervention as a success dependency. - Institute systemic availability frameworks, observability and incident recovery strategies, and automated zonal failure detection and mitigation standards. - Lead high-leverage operational forums (e.g., Weekly Infrastructure Operations Reviews), engineering rigor inspections, post-incident reports and root-cause remediations. - Design and implement (organization and/or enterprise-wide) process, standards, common ways of working where none exist today. Flagship Special Programs (~50%): - Single Threaded Owner (STO) and organizational API for initiatives such as: - Directly execute high-stakes, time-critical engineering programs spanning hybrid infrastructure, Factory Systems and Manufacturing networks, sovereign defense enclaves, multi-cloud user enablement. - Quarterback strategic responses to systemic, enterprise-wide risks, orchestrating cross-functional technical remediations at scale. - Drive technical readiness and architecture validation for complex customer scenarios and rapid Department of Defense / warfighter scenario builds on modern infrastructure. - Champion foundational modernization programs, including Infrastructure as Code (IaC) and Software Defined Networking (SDN), least-privilege automation. We need to preserve the bullet points exactly. Now Required Qualifications: List: - 10+ years of technical program management, engineering or engineering leadership experience driving complex, high-impact programs across distributed systems, cloud infrastructure, and enterprise platforms. - Demonstrated experience acting as a strategic advisor, Principal TPM, or Chief of Staff counterpart to executive engineering leaders, managing cross-organizational strategy, headcount/resource prioritization, and executive reporting. - Deep hands-on expertise building and running Operational Excellence (OE), Site Reliability (SRE), or High Availability (HA) frameworks across multi-region cloud (AWS/Azure/GCP) and hybrid/datacenter environments. - Proven track record leading large-scale incident mitigation, failure testing, and automated resilience initiatives with aggressive recovery time objectives. - Broad technical literacy spanning core IT/infrastructure domains: cloud computing architectures, networking (LAN/WAN/routing/SD-WAN), compute/virtualization/Kubernetes, and enterprise security/IAM. - Exceptional communication skills with the ability to translate deep technical risk and architectural trade-offs into actionable executive-level business decisions. - Ability to thrive in high-tempo, ambiguous, mission-critical environments with complete autonomy. - Must be a U.S. Person and be eligible to obtain and maintain a U.S. Government Top Secret security clearance. Preferred Qualifications: - Direct experience supporting defense technology, aerospace operations, mission control/constellation reliability, or government contracts. - Experience designing and executing enterprise-wide security, IAM/ABAC modernization, or agentic AI/autonomous workflow controls at scale. - Background in streamlining regulated SDLC/CI-CD workflows, compressing deployment cycles through risk-based engineering automation. - Active U.S. Secret or Top Secret/SCI clearance. Pay: US Salary Range $220,000—$292,000 USD Benefits: 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 Anduril's 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 you’re supported in health, recovery, and whatever comes next. We need to preserve that exactly, but we may remove the "For more information, Explore Our Benefits." line as navigation. Also remove the sentence about "The salary range for this role is an estimate..." that's part of benefits? Actually it's under Benefits heading in the original. It's substantive; we keep. Now we need to output HTML fragment. Structure:

  About the role

  ... intro + role description ...

  Responsibilities

  • Chief of Staff Function & Strategic Leadership (~15%)
    • ...
    ...
  ...
  But we need to use
  • for any list of duties/requirements/benefits. So we can have nested lists