Mission Autonomy Lead

We need to output HTML fragment with sections: About the role? Actually the posting includes "About The Team", "About The Job". We need to use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include only sections where posting has real specific content. We have content about role (About The Job) describing responsibilities. We have qualifications (Required Qualifications, Preferred Qualifications). We have Benefits described. We have Pay (US Salary Range). No schedule info. So we should include sections: About the role (or About The Job?), Responsibilities (maybe we can combine), Requirements (maybe Required Qualifications), Qualifications (maybe Preferred?), Skills? Could combine. But we must follow instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can choose which to include. We need to preserve all substantive info. We'll create sections: - About the role: summary of role (maybe from About The Job intro). Could include description: "You will own the Autonomy software stack within Mission Systems for a maritime autonomous vehicle..." etc. - Responsibilities: list of duties from bullet points under "Mission Autonomy Lead, Thunder". Those are responsibilities. - Requirements: Required Qualifications list. - Qualifications: Preferred Qualifications list (or could be Skills). But we have both Required and Preferred. Could map Required to Requirements, Preferred to Qualifications. Or we could have Skills section for technical skills. But we can just have Requirements and Qualifications. - Benefits: list benefits. - Pay: salary range. We must not include schedule. We must not repeat job title as heading. No Job ID. We must remove boilerplate: cookie/navigation/legal/EEO etc. Remove recruitment scams, data privacy, etc. We must preserve all substantive info: keep details about role, responsibilities, qualifications, benefits, salary. We must not invent or summarize away detail. So we need to keep the exact bullet points? We can keep them as list items. We need to output only HTML fragment, no /, no markdown fences. Let's extract content. About The Team and About The Job: The substantive description: "Anduril Industries is a defense technology company..." That's company overview maybe not needed for role? But we can include in About the role? The instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to keep that company overview? It's part of posting but not specific to role. Might be considered substantive. However we need to avoid filler. It's okay to include as part of About the role description. But we must not repeat job title as heading. The job title is "Mission Autonomy Lead, Thunder". Not to be used as heading. We'll create:

About the role

[company overview + role description]

Then responsibilities as

• ... each bullet. Then Requirements as
  • ... required qualifications. Then Qualifications as
    • ... preferred qualifications. Then Benefits as
      • ... benefits list. Then Pay as

        US Salary Range $190,000—$250,000 USD

        We need to ensure we don't include filler like "commensurate with experience". Not present. Now extract details. Company overview 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: "The Maneuver Dominance team is building Thunder - an autonomous attack rotorcraft built to fight alongside crewed combat aviation to deliver overwhelming mass effects deep beyond the front lines. The team in London builds the Mission System and the autonomy that makes aircraft like Thunder work. Autonomy is only as good as the link that carries it. Thunder is a compact airframe with weapons, sensors and radios competing for the same antenna real estate, flying low and in formation, in a spectrum that is actively contested. That is the problem you would own." Then About The Job: "You will own the Autonomy software stack within Mission Systems for a maritime autonomous vehicle, owning the software that enables autonomous mission execution. Reporting to the Mission Systems Lead, you will cover system design, mission planning, mission operations, perception, debrief, and software development infrastructure. You will define how the vehicle plans, executes, perceives, and learns from missions autonomously across long ranges of open ocean beyond line of sight. Your spectrum of support will be diverse in nature and require you to leverage your technical expertise as well as leadership skills to set objectives, build cross-functional teams, and rapidly drive to completion. The ability to leverage your intuition and prior experience will be key in making sure the right design, analysis, and test steps are completed to ensure success. The ideal candidate will leverage their experience executing and successfully completing prior highly optimized multi-disciplinary projects." Then responsibilities list (starting after "Mission Autonomy Lead, Thunder"): - Own the autonomy software architecture — planning, execution, perception, and debrief — using open, modular architecture standards (MOSA/WOSA where applicable) - Drive design of mission planning systems for autonomous aviation operations - Drive mission execution software that manages vehicle behavior during missions - Own perception systems that enable the vehicle to sense and interpret its environment - Develop mission debrief capabilities for post-mission analysis and continuous improvement - Build and maintain software development infrastructure (CI/CD, simulation, SITL/HITL) - Define interfaces between the autonomy stack and vehicle management system in accordance with Modular Open Systems Approach (MOSA) principles - Manage autonomy deliverables across development phases, including MBSE artifacts (e.g., SysML models, requirements traceability) as required by program systems engineering practices - Provide technical mentorship to software and systems engineers - Drive development of test and simulation fixtures for autonomy validation - Represent the autonomy subsystem in technical and customer meetings - Interface with Mission Systems Lead and Vehicle Systems on integration - Travel up to 25% to test sites and customer locations Now Required Qualifications list: - Bachelor's degree in Computer Science, Robotics, Aerospace Engineering, or equivalent - 5+ years of experience in autonomous systems, robotics, or AI/ML - Experience delivering software through full product development cycles - Demonstrated experience with autonomous navigation, planning, or perception systems - Experience with modeling, simulation, and SITL/HITL testing - Experience developing safety-critical or high-assurance software - Proficiency in C++ and/or Python for real-time and mission-critical software systems - Experience with Linux-based embedded or real-time operating systems - Experience with version control and CI/CD tooling (e.g., Git, Jenkins, GitLab CI) - Ability to obtain and maintain a U.S. Secret security clearance Preferred Qualifications list: - Experience with autonomous aviation systems (UAS, UAV, or manned-unmanned teaming) - Working knowledge of ROS/ROS2, behavior trees, or mission planning frameworks - Experience with computer vision, EO/IR sensor processing, or airborne perception - Familiarity with distributed software architectures and edge computing - Experience designing to open systems architecture standards (MOSA/WOSA) for defense acquisition programs - Familiarity with MBSE tooling and digital engineering practices (SysML, Cameo, Jama, or similar) - Familiarity with containerization and deployment tooling (Docker, Kubernetes) for edge/embedded deployment - Experience with simulation environments relevant to aviation/flight dynamics (e.g., Gazebo, JSBSim, X-Plane, or custom digital-twin sims) - Experience with real-time middleware/pub-sub frameworks (DDS, ZeroMQ, or similar) for distributed autonomy systems - Familiarity with cross-compilation and toolchains for embedded/resource-constrained compute (e.g., NVIDIA Jetson or other SWaP-optimized edge hardware) - Experience with static analysis, formal verification, or certification-adjacent tooling (e.g., MISRA C++, DO-178C-adjacent practices) Benefits paragraph: "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. For more information, Explore Our Benefits." We need to list benefits as bullet points? The posting only gives a generic description, not specific benefits list. It says "top-tier benefits ... 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 not a concrete list. According to rule: never create Benefits section unless posting actually states them. It does state benefits exist but not specific. Might be considered vague. However we could include a

        describing benefits as given. The rule: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state benefits exist, but not specific. I'd include a Benefits section with a

        containing that description. Pay: we have salary range. Now we must not include recruitment scams, data privacy, etc. Now produce HTML. Structure:

        About the role

        ... company overview + team + job description ...

        Responsibilities

        • ... each responsibility

        Requirements

        • ... each required qualification

        Qualifications

        • ... each preferred qualification

        Benefits

        ... benefits description ...

        Pay

        US Salary Range $190,000—$250,000 USD

        Make sure to preserve all details exactly as in text, including punctuation, hyphens, etc. Let's craft the About the role paragraph: combine company overview, team, job description. We'll write: 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. The Maneuver Dominance team is building Thunder - an autonomous attack rotorcraft built to fight alongside crewed combat aviation to deliver overwhelming mass effects deep beyond the front lines. The team in London builds the Mission System and the autonomy that makes aircraft like Thunder work. Autonomy is only as good as the link that