Senior Software Engineer, C++
for each section heading.
We need to use - for any list of duties/requirements/benefits. Use
for prose.
We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them.
We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the transcript request, scam warning, data privacy, etc.
Also remove duplicated lines: maybe some lines repeated? Not seeing.
We must not include Job ID/requisition numbers.
Now craft HTML.
First, About the role: combine company description and About The Team.
Company description 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."
Then About The Team paragraph: "Anduril's Software Engineers excel at developing state-of-the-art algorithms and software that solve scientific problems with real-world applications. Working in small innovative teams, our software engineers build solutions that make a difference. Our research endeavors don't end once we've written a journal or conference paper describing our technology; rather, our work is complete when our technology has been deployed in mission-critical systems and our customers within government and industry are successful. As science fiction writer Arthur Clarke wrote, 'Any sufficiently advanced technology is indistinguishable from magic.' Anduril is seeking talented 'magicians' — experienced engineers who lead by example, mentor others, and stay deeply hands-on in the code — to join in our mission to expand the boundary of what's possible."
We can combine into one
or separate
s. Use
for prose.
Responsibilities: list from "What You Will Do". Each bullet.
Let's extract bullets:
- Help shape the technical direction of a small, high-impact team while remaining deeply hands-on in design, implementation, and code review
- Mentor and uplevel junior and mid-level engineers through pair programming, code reviews, technical guidance, and architectural discussions
- Lead by example by writing production-quality C++ and Python that powers mission-critical systems, while setting the bar for engineering excellence (CI/CD, unit testing, large-codebase collaboration, git workflows)
- Prototype state-of-the-art software solutions in an agile development environment and guide the team through the path from prototype to deployed, tactical implementation
- Implement high-performance software spanning the spectrum from tactical systems to web applications
- Use high-fidelity modeling and simulation environments, innovative analysis tools, and sound analysis techniques to quantify the benefit of our technology
- Drive technical interchange meetings, sprint planning, and customer engagements to ensure successful outcomes for mission-critical needs
- Own all aspects of the software development lifecycle, helping the team navigate ambiguity and complex technical trade-offs
- Communicate complex technical concepts clearly to colleagues, customers, and non-technical stakeholders
We'll put each as
- .
Requirements: Required Qualifications list.
Extract:
- 8+ years of software engineering experience and a Bachelor's degree or equivalent education/work experience
- Demonstrated experience mentoring junior engineers and providing technical leadership on a team, while continuing to contribute as a hands-on individual contributor
- Experience supporting and navigating large, complex codebases as part of a collaborative team
- Strong proficiency in C/C++ and Python
- Direct experience in air and missile defense domains, such as multi-target tracking, sensor fusion, threat classification, kill chain development, or command-and-control systems (e.g., IBCS, Patriot, Aegis, or similar programs)
- Big data/NoSQL/database technologies
- Software engineering: software design, algorithm implementation, and software analysis, testing, and optimization
- Applied mathematics: differential equations, linear algebra, optimization, statistics, and random processes
- Engineering: controls, estimation theory, and digital signal processing
- Eligible to obtain and maintain an active U.S. Top Secret SCI security clearance
We'll put as
- .
Qualifications: Preferred Qualifications list.
Extract:
- Experience leading small teams or technical workstreams while remaining a top individual contributor
- Track record of growing engineers through mentorship, code review culture, and technical coaching
- Experience with asynchronous programming, parallel programming, and GPU programming
- Prior experience deploying software to real-world tactical/edge environments
We'll put as
- .
Skills: maybe we could extract technical skills from Required Qualifications but we already have them there. Could create a Skills section summarizing technical proficiencies: C/C++, Python, big data/NoSQL, modeling/simulation, applied math, controls, etc. But we must not invent or summarize away detail; we need to preserve all substantive info. If we create a Skills section, we need to ensure we are not omitting any info from elsewhere. The Required Qualifications already contain those details; we could keep them there and not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine Required Qualifications and Skills into one section? But they ask to use headings for sections like Requirements, Qualifications, Skills. We need to decide which sections to include based on content. We have content for Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Skills could be derived from Required Qualifications but that would be duplicative. Better to not create a Skills section if it would be thin or duplicate. However, the instruction says "include a section ONLY when the posting has real, specific content for it". The posting does have specific content about skills (proficiency in C/C++ and Python, etc.) but that's already under Required Qualifications. If we make a Skills section, we would need to extract those specifics and maybe remove them from Required Qualifications to avoid duplication. But we must preserve ALL substantive information; we can keep them in both places? That would be duplication, which is not prohibited but might be considered redundant. The instruction says "Do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid duplication of content across sections, but we should avoid unnecessary duplication. Better to keep skills within Requirements (or Qualifications) and not create a separate Skills section unless there is a distinct list of skills separate from qualifications. The posting does not have a separate "Skills" heading; it's embedded. So we should not create a Skills section.
Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay.
Check Benefits: list from "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."
That's vague; no specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It does state they offer top-tier benefits, but no specific list. It says "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." That's not specific; it's generic. Should we include Benefits section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they offer benefits, but not specific. Might be considered stating them, albeit vague. However, we should include only if there is real, specific content. The phrase "comprehensive, competitive benefits package" is not specific. I'd argue it's not specific enough to warrant a Benefits section. But we could include a
summarizing that they offer comprehensive benefits, but that might be considered filler. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is similar to vague benefits. So better to omit Benefits section.
Pay: we have US Salary Range $190,000—$252,000 USD. That's specific. So include Pay section.
Schedule: not mentioned, omit.
Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Pay.
Now format.
We need to output only HTML fragment, no /, no markdown.
We'll start with
About the role
then ... maybe two paragraphs.
We'll combine company description and About The Team into maybe two
s.
Let's craft:
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
for prose. We must preserve ALL substantive information; do not invent or summarize away detail. So we need to keep all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out the transcript request, scam warning, data privacy, etc. Also remove duplicated lines: maybe some lines repeated? Not seeing. We must not include Job ID/requisition numbers. Now craft HTML. First, About the role: combine company description and About The Team. Company description 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." Then About The Team paragraph: "Anduril's Software Engineers excel at developing state-of-the-art algorithms and software that solve scientific problems with real-world applications. Working in small innovative teams, our software engineers build solutions that make a difference. Our research endeavors don't end once we've written a journal or conference paper describing our technology; rather, our work is complete when our technology has been deployed in mission-critical systems and our customers within government and industry are successful. As science fiction writer Arthur Clarke wrote, 'Any sufficiently advanced technology is indistinguishable from magic.' Anduril is seeking talented 'magicians' — experienced engineers who lead by example, mentor others, and stay deeply hands-on in the code — to join in our mission to expand the boundary of what's possible." We can combine into one
or separate
s. Use
for prose. Responsibilities: list from "What You Will Do". Each bullet. Let's extract bullets: - Help shape the technical direction of a small, high-impact team while remaining deeply hands-on in design, implementation, and code review - Mentor and uplevel junior and mid-level engineers through pair programming, code reviews, technical guidance, and architectural discussions - Lead by example by writing production-quality C++ and Python that powers mission-critical systems, while setting the bar for engineering excellence (CI/CD, unit testing, large-codebase collaboration, git workflows) - Prototype state-of-the-art software solutions in an agile development environment and guide the team through the path from prototype to deployed, tactical implementation - Implement high-performance software spanning the spectrum from tactical systems to web applications - Use high-fidelity modeling and simulation environments, innovative analysis tools, and sound analysis techniques to quantify the benefit of our technology - Drive technical interchange meetings, sprint planning, and customer engagements to ensure successful outcomes for mission-critical needs - Own all aspects of the software development lifecycle, helping the team navigate ambiguity and complex technical trade-offs - Communicate complex technical concepts clearly to colleagues, customers, and non-technical stakeholders We'll put each as
- .
Qualifications: Preferred Qualifications list.
Extract:
- Experience leading small teams or technical workstreams while remaining a top individual contributor
- Track record of growing engineers through mentorship, code review culture, and technical coaching
- Experience with asynchronous programming, parallel programming, and GPU programming
- Prior experience deploying software to real-world tactical/edge environments
We'll put as
- .
Skills: maybe we could extract technical skills from Required Qualifications but we already have them there. Could create a Skills section summarizing technical proficiencies: C/C++, Python, big data/NoSQL, modeling/simulation, applied math, controls, etc. But we must not invent or summarize away detail; we need to preserve all substantive info. If we create a Skills section, we need to ensure we are not omitting any info from elsewhere. The Required Qualifications already contain those details; we could keep them there and not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine Required Qualifications and Skills into one section? But they ask to use headings for sections like Requirements, Qualifications, Skills. We need to decide which sections to include based on content. We have content for Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Skills could be derived from Required Qualifications but that would be duplicative. Better to not create a Skills section if it would be thin or duplicate. However, the instruction says "include a section ONLY when the posting has real, specific content for it". The posting does have specific content about skills (proficiency in C/C++ and Python, etc.) but that's already under Required Qualifications. If we make a Skills section, we would need to extract those specifics and maybe remove them from Required Qualifications to avoid duplication. But we must preserve ALL substantive information; we can keep them in both places? That would be duplication, which is not prohibited but might be considered redundant. The instruction says "Do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." It doesn't forbid duplication of content across sections, but we should avoid unnecessary duplication. Better to keep skills within Requirements (or Qualifications) and not create a separate Skills section unless there is a distinct list of skills separate from qualifications. The posting does not have a separate "Skills" heading; it's embedded. So we should not create a Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Check Benefits: list from "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." That's vague; no specific benefits listed. The instruction: never create Benefits section unless posting actually states them. It does state they offer top-tier benefits, but no specific list. It says "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." That's not specific; it's generic. Should we include Benefits section? The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state they offer benefits, but not specific. Might be considered stating them, albeit vague. However, we should include only if there is real, specific content. The phrase "comprehensive, competitive benefits package" is not specific. I'd argue it's not specific enough to warrant a Benefits section. But we could include a
summarizing that they offer comprehensive benefits, but that might be considered filler. The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". This is similar to vague benefits. So better to omit Benefits section. Pay: we have US Salary Range $190,000—$252,000 USD. That's specific. So include Pay section. Schedule: not mentioned, omit. Thus final sections: About the role, Responsibilities, Requirements, Qualifications, Pay. Now format. We need to output only HTML fragment, no /, no markdown. We'll start with
About the role
then... maybe two paragraphs. We'll combine company description and About The Team into maybe two
s. Let's craft:
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
- .
Skills: maybe we could extract technical skills from Required Qualifications but we already have them there. Could create a Skills section summarizing technical proficiencies: C/C++, Python, big data/NoSQL, modeling/simulation, applied math, controls, etc. But we must not invent or summarize away detail; we need to preserve all substantive info. If we create a Skills section, we need to ensure we are not omitting any info from elsewhere. The Required Qualifications already contain those details; we could keep them there and not duplicate. The instruction: "Prefer a few substantive sections over many thin ones." So maybe we can combine Required Qualifications and Skills into one section? But they ask to use headings for sections like Requirements, Qualifications, Skills. We need to decide which sections to include based on content. We have content for Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). Skills could be derived from Required Qualifications but that would be duplicative. Better to not create a Skills section if it would be thin or duplicate. However, the instruction says "include a section ONLY when the posting has real, specific content for it". The posting does have specific content about skills (proficiency in C/C++ and Python, etc.) but that's already under Required Qualifications. If we make a Skills section, we would need to extract those specifics and maybe remove them from Required Qualifications to avoid duplication. But we must preserve ALL substantive information; we can keep them in both places? That would be duplication, which is not prohibited but might be considered redundant. The instruction says "Do NOT repeat the job title as a heading" and "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short