Staff Systems Engineer (R5982)

We need to output HTML fragment with sections for headings: 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. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Also must not include sections with filler like "commensurate with experience". Must include Pay if posting actually states them: yes they have salary range $144,000 - $210,000 a year. Also mention bonus, benefits, equity, temporary benefits after 60 days. So we can include Pay section with that info. Benefits: they mention benefits, equity, bonus, temporary benefits after 60 days. So we can include Benefits section summarizing those. Schedule: they mention Full-time regular employee offer package, Temporary employee offer package. So schedule: Full-time regular, Temporary (maybe mention full-time). We can include Schedule section with that info. About the role: we have a paragraph describing mission and role. Could be "About the role". Use

About the role

then

with description. Responsibilities: list of duties from "What You'll Do:" bullet points. Use

• . Requirements: maybe combine Required Qualifications and Preferred Qualifications? The instruction: sections: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide what goes where. Typically "Required Qualifications" could go under Requirements or Qualifications. "Preferred Qualifications" maybe under Qualifications. Skills could be extracted from required qualifications like proficiency in MBSE etc. But we must not invent or summarize away detail. We need to preserve ALL substantive information; we can place content under appropriate headings but must not lose info. We can put Required Qualifications under Requirements, Preferred Qualifications under Qualifications, and maybe Skills under Skills (like proficiency in MBSE, DOORS, SysML, etc). However we must avoid duplication. Let's parse the posting: Job Description paragraph: "As a Staff Systems Engineer on Shield AI’s next gen UAS program, you will play a pivotal role..." That's about role. "What You'll Do:" list of duties. "Required Qualifications:" list. "Preferred Qualifications:" list. Then salary and benefits info. We need to map to headings: - About the role: the introductory paragraph. - Responsibilities: the "What You'll Do:" list. - Requirements: maybe the Required Qualifications. - Qualifications: maybe the Preferred Qualifications. - Skills: could be extracted from both required and preferred? But we might avoid duplication by putting specific skill items under Skills. However the instruction says "Prefer a few substantive sections over many thin ones." So maybe we combine Required and Preferred into Qualifications and skip Skills. But we have to include sections only when posting has real specific content. If we omit Skills, that's fine. But we need to decide where to put the skill-related info (like proficiency in MBSE, DOORS, SysML, etc). Those are part of Required Qualifications. So we can keep them under Requirements (or Qualifications). Let's decide: Option: Use Requirements for Required Qualifications, Qualifications for Preferred Qualifications, and omit Skills. Pay: include salary range and mention bonus, equity, benefits. Benefits: mention benefits, equity, bonus, temporary benefits after 60 days. However we already mentioned benefits in Pay section; we could combine but instruction says prefer few sections. Could combine Pay and Benefits into one? But they are separate headings allowed. We could have Pay section with salary range, bonus, equity, benefits. Benefits section maybe redundant. Better to have Pay section include salary, bonus, equity, benefits. Then Benefits section could be omitted. But we need to include Benefits only if posting has real specific content for it. The posting mentions benefits, equity, bonus, temporary benefits after 60 days. That's substantive. If we put all that under Pay, we still have Benefits content covered. But we might still need a Benefits section if we want to follow headings. However we can omit Benefits if we consider Pay covers it. The instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It doesn't forbid having overlapping content across sections, but we should avoid duplication. Safer to have Pay section with salary, bonus, equity, benefits. Then Benefits section could be omitted. Schedule: mention Full-time regular employee offer package, Temporary employee offer package. So we can include Schedule. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Pay, Schedule. Now we need to format. We must not include markdown code fences. Just raw HTML. Let's extract content. About the role paragraph: "Shield AI is a venture-backed defense-tech company with the mission of protecting service members and civilians with intelligent systems. Its products include Hivemind autonomy software, V-BAT and X-BAT aircraft, and Aechelon simulation and synthetic reality technologies. With offices and facilities across the U.S., Europe, the Middle East, and Asia-Pacific, Shield AI’s technology actively supports operations worldwide. For more information, visit www.shield.ai . Follow Shield AI on LinkedIn , X , Instagram , and YouTube . Job Description: As a Staff Systems Engineer on Shield AI’s next gen UAS program, you will play a pivotal role in designing, developing, and integrating cutting-edge autonomous aircraft systems for national defense. You will lead the technical execution of system architecture, ensuring seamless integration of avionics, autonomy, propulsion, sensor payloads, and mission-critical systems. This position requires a deep understanding of aerospace systems engineering, autonomy, and complex system integration. You will work cross-functionally with teams in hardware, software, autonomy, flight operations, and manufacturing to develop a scalable, mission-ready platform capable of operating in contested environments. Your expertise will be critical in defining system requirements and architectures through model-based systems engineering, conducting trade studies, ensuring compliance with military and aviation standards, and supporting the aircraft through flight testing and operational deployment." We need to remove navigation/footer like "For more information, visit www.shield.ai . Follow Shield AI on LinkedIn , X , Instagram , and YouTube ." That's boilerplate? It's not cookie/navigation/legal/EEO etc but it's like social media links. Might be considered navigation? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Social media links maybe navigation; but they are not essential job description. Safer to remove them. Also remove "For more information, visit www.shield.ai ." That's like a link. Probably considered navigation. We'll remove those lines. Thus About the role paragraph should start with "Shield AI is a venture-backed defense-tech company..." and end before the social media. We'll keep the mission description and then the Job Description sentence. Let's craft:

  Shield AI is a venture-backed defense-tech company with the mission of protecting service members and civilians with intelligent systems. Its products include Hivemind autonomy software, V-BAT and X-BAT aircraft, and Aechelon simulation and synthetic reality technologies. With offices and facilities across the U.S., Europe, the Middle East, and Asia-Pacific, Shield AI’s technology actively supports operations worldwide. As a Staff Systems Engineer on Shield AI’s next gen UAS program, you will play a pivotal role in designing, developing, and integrating cutting-edge autonomous aircraft systems for national defense. You will lead the technical execution of system architecture, ensuring seamless integration of avionics, autonomy, propulsion, sensor payloads, and mission-critical systems. This position requires a deep understanding of aerospace systems engineering, autonomy, and complex system integration. You will work cross-functionally with teams in hardware, software, autonomy, flight operations, and manufacturing to develop a scalable, mission-ready platform capable of operating in contested environments. Your expertise will be critical in defining system requirements and architectures through model-based systems engineering, conducting trade studies, ensuring compliance with military and aviation standards, and supporting the aircraft through flight testing and operational deployment.

  Now Responsibilities: list from "What You'll Do:" bullet points. We need to capture each bullet. Original bullets: - Perform System Architecture & Design: Develop and refine the system architecture for the next gen UAS, ensuring seamless integration of avionics, autonomy, propulsion, sensor payloads, and mission systems. - Define and document system-level behavior, including modes, states, transitions, and fault responses - Support safety analyses (FHA, FMEA, FTA) by defining behavior under fault conditions - Define and Manage System Requirements: Establish top-level requirements, decompose them into subsystems, and maintain traceability across the development lifecycle. - Autonomy & AI Integration: Work closely with autonomy and software teams to integrate AI-driven flight control, decision-making, and mission execution capabilities. - Model-Based Systems Engineering (MBSE): Utilize SysML, DOORS, or other MBSE tools to create digital system models, conduct trade studies, and optimize system performance. - Risk Management & Trade Studies: Conduct trade studies to evaluate design alternatives, assess technical risks, and ensure the best engineering solutions for mission effectiveness. - Stakeholder & Customer Engagement: Work closely with DoD stakeholders, industry partners, and government agencies to align system capabilities with operational requirements. - Cross-Functional Collaboration: Partner with hardware, autonomy, software, propulsion, and flight operations teams to drive seamless system integration and rapid development cycles. We need to preserve all. We'll put each as
• . Now Requirements: Required Qualifications list. Original: - Typically requires a minimum of 7 years of related experience with a Bachelor’s degree - Demonstrated experience defining system behavior logic and operational modes - Deep expertise in system architecture, avionics integration, and autonomy-driven flight systems. - Proficiency in MBSE, DOORS, SysML, CAMEO, or similar system modeling tools for complex systems design and analysis. - Experience with Group 4 or Group 5 UAS, military aircraft, or autonomous airborne platforms. - Strong background in flight testing, system integration, and performance validation. - Knowledge of DoD acquisition processes, MIL-STDs, FAA airworthiness certification, and airborne system safety standards. - Demonstrated ability to lead cross-functional teams and drive complex projects to successful completion. - Ability to work in a fast-paced, agile development environment with shifting priorities. - Worked on developmental program from clean sheet to first flight - Ability to obtain a S//SAR level security clearance desired. We'll put each as
• under Requirements. Now Qualifications: Preferred Qualifications list. Original: - Experience developing AI-driven autonomy for unmanned aircraft. - Expertise in ISR, EW, and advanced sensor integration for airborne platforms. - Familiarity with modular open system architectures (MOSA) and Government Reference Architectures (GRA) for defense applications. - Prior experience working with defense primes, DoD stakeholders, or government R&D programs. - Active Secret or Top Secret clearance (or ability to obtain one). We'll put each as
• under Qualifications. Now Pay: includes salary range and bonus, benefits, equity, temporary benefits after 60 days. Original: "$144,000 - $210,000 a year #LE Full-time regular employee offer package: Pay within range listed + Bonus + Benefits + Equity Temporary employee offer package: Pay within range listed above + temporary benefits package (applicable after 60 days of employment) Salary compensation is influenced by a wide array of factors including but not limited to skill set, level of experience, licenses and certifications, and specific work location. All offers are contingent on a cleared background and possible reference check. Military fellows and part-time employees are not eligible for benefits. Please speak to your talent acquisition representative for more information." We need to remove application instructions like "Please speak to your talent acquisition representative for more information." That's application instruction; remove. Also remove "#LE" maybe not needed. Keep salary range and description. We'll craft a

  with that info. Now Schedule: includes Full-time regular employee offer package, Temporary employee