Principal Technical Program Manager, Infrastructure Engineering
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need sections: About the role, Responsibilities, Requirements (maybe Qualifications), Benefits, Pay (if present). The posting includes "US Salary Range $220,000—$292,000 USD". That's pay info. Also includes "Benefits" section with description. Also includes "Required Qualifications" and "Preferred Qualifications". We can combine Required and Preferred under Requirements or Qualifications. The instruction says use headings like Requirements, Qualifications, Skills. We can choose "Requirements" for required qualifications, maybe also include preferred as part of same section? Could separate but better to have one Requirements section containing both required and preferred? The instruction: "Prefer a few substantive sections over many thin ones." So we can have Requirements covering both required and preferred. Also we have "What You'll Do" which is responsibilities. So sections: About the role, Responsibilities, Requirements, Benefits, Pay.
We must not include schedule (none). Must not include Skills separate if not explicit. There's no explicit Skills list; we can omit.
We must preserve all substantive info: need to include the paragraphs about Anduril mission, about the role, what you'll do (broken into subparts), required qualifications, preferred qualifications, benefits description, salary range.
We must remove boilerplate: the "Protecting Yourself from Recruitment Scams", "Data Privacy", etc. Also remove "Explore Our Benefits." link? The benefits section includes: "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. For more information, Explore Our Benefits." We need to keep the substantive benefits description but can drop the "For more information, Explore Our Benefits." as it's basically a link instruction; but it's not boilerplate? It's a call to action; maybe we can keep it as part of benefits description? The instruction: remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "For more information, Explore Our Benefits." is like a link instruction; could be considered application instruction? It's not exactly application instruction but it's a directive to explore benefits. Might be considered navigation. Safer to omit that sentence. Keep the description of benefits: "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 also need to keep the "US Salary Range $220,000—$292,000 USD". Also note that the benefits section earlier says: "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." That's substantive about salary; we should keep that as part of Pay section.
Thus Pay section will include that paragraph plus the salary range.
Now we need to format using for each section heading, and - for any list of duties/requirements/benefits, and
for prose.
We need to decide what constitutes a list. The "What You'll Do" includes bullet-like paragraphs but not explicit bullet list. It has subheadings: Chief of Staff Function & Strategic Leadership (~15%), Operational Excellence (OE) & Resilience (~25 - 35%), Flagship Special Programs (~50%). Under each there are multiple sentences describing duties. Could we turn each duty into
- ? The instruction: Use
- for any list of duties/requirements/benefits. If the content is not already a list, we could still convert to list if it's a series of items. The "What You'll Do" sections have multiple duties; we could treat each bullet as list items. However we must preserve all substantive information; converting to list is fine as long as we don't lose info. The original text includes paragraphs; we can break them into list items.
Similarly, Required Qualifications and Preferred Qualifications are each a list of items (each line starts with a bold phrase?). We can make
- for each qualification.
Benefits: we have a description; not a list; we can keep as
.
Pay: we have prose; keep as
.
About the role: we have introductory paragraph about Anduril and then "About The Role" heading. We'll put that as
.
Now we must not repeat job title as heading. The job title is "Principal Technical Program Manager (TPM)". We must not use that as heading.
Now produce HTML fragment.
Let's extract content.
First, introductory paragraph before "About The Role":
"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."
We'll put that in
under About the role section? Actually the About the role section should contain that plus maybe the "About The Role" heading? The heading is "About The Role". We'll use
About the role
then with that intro paragraph.
Now Responsibilities: heading
Responsibilities
. Then we need to list duties.
We have three main areas with percentages and details.
We could create a with each main area as - containing further detail maybe as
inside? But we can just make each duty as
- with the full description.
Let's list:
- 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 all info; we can flatten into list items.
Now Requirements: heading
Requirements
. We'll combine required and preferred.
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 list:
- 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.
We'll put all in a single - list.
Now Benefits: heading
Benefits
. Then with the benefits description (excluding the "For more information, Explore Our Benefits.").
Benefits description: "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
- for any list of duties/requirements/benefits, and
for prose. We need to decide what constitutes a list. The "What You'll Do" includes bullet-like paragraphs but not explicit bullet list. It has subheadings: Chief of Staff Function & Strategic Leadership (~15%), Operational Excellence (OE) & Resilience (~25 - 35%), Flagship Special Programs (~50%). Under each there are multiple sentences describing duties. Could we turn each duty into
- ? The instruction: Use
- for any list of duties/requirements/benefits. If the content is not already a list, we could still convert to list if it's a series of items. The "What You'll Do" sections have multiple duties; we could treat each bullet as list items. However we must preserve all substantive information; converting to list is fine as long as we don't lose info. The original text includes paragraphs; we can break them into list items.
Similarly, Required Qualifications and Preferred Qualifications are each a list of items (each line starts with a bold phrase?). We can make
- for each qualification.
Benefits: we have a description; not a list; we can keep as
. Pay: we have prose; keep as
. About the role: we have introductory paragraph about Anduril and then "About The Role" heading. We'll put that as
. Now we must not repeat job title as heading. The job title is "Principal Technical Program Manager (TPM)". We must not use that as heading. Now produce HTML fragment. Let's extract content. First, introductory paragraph before "About The Role": "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." We'll put that in
under About the role section? Actually the About the role section should contain that plus maybe the "About The Role" heading? The heading is "About The Role". We'll use
About the role
thenwith that intro paragraph. Now Responsibilities: heading
Responsibilities
. Then we need to list duties. We have three main areas with percentages and details. We could create a- with each main area as
- containing further detail maybe as
inside? But we can just make each duty as
- with the full description.
Let's list:
- 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 all info; we can flatten into list items.
Now Requirements: heading
Requirements
. We'll combine required and preferred. 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 list: - 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. We'll put all in a single- list.
Now Benefits: heading
Benefits
. Thenwith the benefits description (excluding the "For more information, Explore Our Benefits."). Benefits description: "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
- list.
Now Benefits: heading
- containing further detail maybe as
- for each qualification.
Benefits: we have a description; not a list; we can keep as
- for any list of duties/requirements/benefits. If the content is not already a list, we could still convert to list if it's a series of items. The "What You'll Do" sections have multiple duties; we could treat each bullet as list items. However we must preserve all substantive information; converting to list is fine as long as we don't lose info. The original text includes paragraphs; we can break them into list items.
Similarly, Required Qualifications and Preferred Qualifications are each a list of items (each line starts with a bold phrase?). We can make