Mid-Level or Senior Aerospace Systems Safety Engineer
Boeing · Hazelwood, MO · 3 wk ago
Engineering$107k–$145k/yrFull-time
We need to produce HTML fragment with sections: About the role? The posting includes description paragraphs. We need to use for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, not invent. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, cookie/navigation, etc.
We need to decide sections: We have a job description intro: "At Boeing, we innovate...". Could be "About the role". Then responsibilities list: "Primary responsibilities:" bullet list. Then qualifications: Basic Qualifications (Required Skills and Experience) and Preferred Qualifications (Desired Skills and Experience). Could combine into "Requirements" or "Qualifications". Also we have "Pay & Benefits:" with pay ranges and benefits description. Also "Relocation", "Security Clearance", "Visa Sponsorship", "Shift". Those could be under "Benefits" or separate sections like "Schedule" (shift). But we should only create sections if there is real specific content. Pay range is specific; benefits description is generic but still mentions health insurance etc. Could include Benefits section. Pay section maybe separate? The instruction says use headings for Benefits, Pay, Schedule. We could combine Pay and Benefits into one Benefits section? But they said prefer few substantive sections over many thin ones. Could have sections: About the role, Responsibilities, Qualifications, Pay & Benefits, Additional Info (maybe not needed). However they want headings exactly from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose subset.
We have content for About the role (intro). Responsibilities (list). Requirements/Qualifications (basic and preferred). Skills maybe not separate; we could embed in Qualifications. Benefits: we have description of benefits. Pay: we have specific pay ranges. Schedule: we have shift info (1st shift). So we can include Schedule section.
We must not repeat job title as heading. No Job ID etc.
We must not include boilerplate like Drug Free Workplace, Export Control Requirements, Equal Opportunity Employer, etc. Those are boilerplate/legal; remove them. Also remove "Applications for this position will be accepted until Oct. 23, 2026" (application instruction). Remove "Export Control Details: US based job, US Person required". Remove "Relocation This position offers relocation based on candidate eligibility." That could be considered benefit? Might keep as part of Benefits? But relocation is a benefit; we could include in Benefits section. However we need to preserve ALL substantive information; we cannot drop relocation if it's substantive. But we can incorporate into Benefits section. Similarly Security Clearance requirement is substantive; could be part of Requirements or Qualifications. Visa Sponsorship (employer will not sponsor) is also substantive; could be in Requirements. Shift is schedule.
Thus we need to include all substantive info but can place them under appropriate headings.
We must not include duplicated lines. Ensure we don't repeat same info.
Let's extract substantive content:
Intro: "At Boeing, we innovate and collaborate to make the world a better place. We’re committed to fostering an environment for every teammate that’s welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us. The Boeing Defense Air Dominance Division Systems Safety & Mission Assurance organization is looking for an Aerospace Systems Safety Engineer to join our team in Hazelwood, MO. Our teams are currently hiring for a broad range of experience levels including Experienced (Level 3) or Senior (Level 4) Aircraft Safety Engineers. A successful candidate will perform system software safety engineering work on a Proprietary Air Dominance program, drive hazard analyses, demonstrate compliance to MIL‑STD‑882E and other standards, and influence system architecture to reduce safety risk. The selected candidate will provide technical guidance and perform critical Software System Safety Engineering work. In addition to working with System Safety personnel, the individual will work extensively with design, development, and test to incorporate robust safety features and reduce project safety risk."
That's about the role.
Responsibilities list (Primary responsibilities):
- Analyzes the integration of complex airplane systems and their corresponding airplane-level effects, failure indications, and flight crew actions as part of a system of systems analysis
- Documents safety analyses, hazard mitigation, validation, and verification activities in compliance with relevant customer and regulatory safety standards such as MIL-STD-882E, MIL-HDBK-516C, AC-17-01, DO-178C, and DO-254.
- Demonstrates safety hazard risk mitigation and control methods to the customer and regulators
- Identifies safety issue systemic root causes and recommends corrective actions using industry best practices
- Collaborates with internal and external stakeholders to define, validate, and integrate safety requirements
- Participates in tests and analyses to verify that systems meet the defined safety requirements
- Resolves multi-functional technical issues
Basic Qualifications (Required Skills and Experience):
- Bachelor of Science degree in Engineering, Engineering Technology (including Manufacturing Technology), Computer Science, Data Science, Mathematics, Physics, Chemistry or non-US equivalent qualifications directly related to the work statement
- Level 3: 5+ years of experience working in an engineering, engineering technology, or related technical discipline
- Ability to obtain a U.S. Security Clearance for which the U.S. Government requires U.S. Citizenship
Preferred Qualifications (Desired Skills and Experience):
- Level 4: 9+ years of experience working in an engineering, engineering technology, or related technical discipline
- 3+ years of experience with the design and technical development of hardware, firmware or software for Military, Space, or Commercial airplane systems
- 3+ years of experience in software verification & validation and safety analysis
- 3+ years' experience general working level knowledge of tactical aircraft hydro-mechanical subsystems, and components, including at least one of the following areas of focus: flight controls, landing gear, ejection seats, fuel, hydraulics, power plant (engines & APU's), environmental controls
Pay & Benefits:
- Competitive base pay and variable compensation opportunities.
- Eligible employees can enroll in variety of benefit programs: health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, paid and unpaid time away.
- Specific programs vary by eligibility factors: geographic location, date of hire, collective bargaining agreements.
- Pay based on candidate experience and qualifications, market and business considerations.
- Summary Pay Range: Experienced (Level 3): $107,100 - $144,900; Senior (Level 4): $131,750 - $178,250.
Relocation: This position offers relocation based on candidate eligibility.
Security Clearance: This position requires the ability to obtain a U.S. Security Clearance for which the U.S. Government requires U.S. Citizenship. An interim and/or final U.S. Confidential Clearance Post-Start is required.
Visa Sponsorship: Employer will not sponsor applicants for employment visa status.
Shift: This position is for 1st shift.
We need to avoid duplication: Security Clearance appears both in Basic Qualifications and later; we should include only once. We'll include under Requirements/Qualifications.
We need to output only HTML fragment, no markdown fences.
We'll structure:
for section headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when posting has real specific content. We need to preserve all substantive info, not invent. Remove boilerplate like EEO, legal, etc. Also remove duplicated lines, application instructions, cookie/navigation, etc.
We need to decide sections: We have a job description intro: "At Boeing, we innovate...". Could be "About the role". Then responsibilities list: "Primary responsibilities:" bullet list. Then qualifications: Basic Qualifications (Required Skills and Experience) and Preferred Qualifications (Desired Skills and Experience). Could combine into "Requirements" or "Qualifications". Also we have "Pay & Benefits:" with pay ranges and benefits description. Also "Relocation", "Security Clearance", "Visa Sponsorship", "Shift". Those could be under "Benefits" or separate sections like "Schedule" (shift). But we should only create sections if there is real specific content. Pay range is specific; benefits description is generic but still mentions health insurance etc. Could include Benefits section. Pay section maybe separate? The instruction says use headings for Benefits, Pay, Schedule. We could combine Pay and Benefits into one Benefits section? But they said prefer few substantive sections over many thin ones. Could have sections: About the role, Responsibilities, Qualifications, Pay & Benefits, Additional Info (maybe not needed). However they want headings exactly from list: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can choose subset.
We have content for About the role (intro). Responsibilities (list). Requirements/Qualifications (basic and preferred). Skills maybe not separate; we could embed in Qualifications. Benefits: we have description of benefits. Pay: we have specific pay ranges. Schedule: we have shift info (1st shift). So we can include Schedule section.
We must not repeat job title as heading. No Job ID etc.
We must not include boilerplate like Drug Free Workplace, Export Control Requirements, Equal Opportunity Employer, etc. Those are boilerplate/legal; remove them. Also remove "Applications for this position will be accepted until Oct. 23, 2026" (application instruction). Remove "Export Control Details: US based job, US Person required". Remove "Relocation This position offers relocation based on candidate eligibility." That could be considered benefit? Might keep as part of Benefits? But relocation is a benefit; we could include in Benefits section. However we need to preserve ALL substantive information; we cannot drop relocation if it's substantive. But we can incorporate into Benefits section. Similarly Security Clearance requirement is substantive; could be part of Requirements or Qualifications. Visa Sponsorship (employer will not sponsor) is also substantive; could be in Requirements. Shift is schedule.
Thus we need to include all substantive info but can place them under appropriate headings.
We must not include duplicated lines. Ensure we don't repeat same info.
Let's extract substantive content:
Intro: "At Boeing, we innovate and collaborate to make the world a better place. We’re committed to fostering an environment for every teammate that’s welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us. The Boeing Defense Air Dominance Division Systems Safety & Mission Assurance organization is looking for an Aerospace Systems Safety Engineer to join our team in Hazelwood, MO. Our teams are currently hiring for a broad range of experience levels including Experienced (Level 3) or Senior (Level 4) Aircraft Safety Engineers. A successful candidate will perform system software safety engineering work on a Proprietary Air Dominance program, drive hazard analyses, demonstrate compliance to MIL‑STD‑882E and other standards, and influence system architecture to reduce safety risk. The selected candidate will provide technical guidance and perform critical Software System Safety Engineering work. In addition to working with System Safety personnel, the individual will work extensively with design, development, and test to incorporate robust safety features and reduce project safety risk."
That's about the role.
Responsibilities list (Primary responsibilities):
- Analyzes the integration of complex airplane systems and their corresponding airplane-level effects, failure indications, and flight crew actions as part of a system of systems analysis
- Documents safety analyses, hazard mitigation, validation, and verification activities in compliance with relevant customer and regulatory safety standards such as MIL-STD-882E, MIL-HDBK-516C, AC-17-01, DO-178C, and DO-254.
- Demonstrates safety hazard risk mitigation and control methods to the customer and regulators
- Identifies safety issue systemic root causes and recommends corrective actions using industry best practices
- Collaborates with internal and external stakeholders to define, validate, and integrate safety requirements
- Participates in tests and analyses to verify that systems meet the defined safety requirements
- Resolves multi-functional technical issues
Basic Qualifications (Required Skills and Experience):
- Bachelor of Science degree in Engineering, Engineering Technology (including Manufacturing Technology), Computer Science, Data Science, Mathematics, Physics, Chemistry or non-US equivalent qualifications directly related to the work statement
- Level 3: 5+ years of experience working in an engineering, engineering technology, or related technical discipline
- Ability to obtain a U.S. Security Clearance for which the U.S. Government requires U.S. Citizenship
Preferred Qualifications (Desired Skills and Experience):
- Level 4: 9+ years of experience working in an engineering, engineering technology, or related technical discipline
- 3+ years of experience with the design and technical development of hardware, firmware or software for Military, Space, or Commercial airplane systems
- 3+ years of experience in software verification & validation and safety analysis
- 3+ years' experience general working level knowledge of tactical aircraft hydro-mechanical subsystems, and components, including at least one of the following areas of focus: flight controls, landing gear, ejection seats, fuel, hydraulics, power plant (engines & APU's), environmental controls
Pay & Benefits:
- Competitive base pay and variable compensation opportunities.
- Eligible employees can enroll in variety of benefit programs: health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, paid and unpaid time away.
- Specific programs vary by eligibility factors: geographic location, date of hire, collective bargaining agreements.
- Pay based on candidate experience and qualifications, market and business considerations.
- Summary Pay Range: Experienced (Level 3): $107,100 - $144,900; Senior (Level 4): $131,750 - $178,250.
Relocation: This position offers relocation based on candidate eligibility.
Security Clearance: This position requires the ability to obtain a U.S. Security Clearance for which the U.S. Government requires U.S. Citizenship. An interim and/or final U.S. Confidential Clearance Post-Start is required.
Visa Sponsorship: Employer will not sponsor applicants for employment visa status.
Shift: This position is for 1st shift.
We need to avoid duplication: Security Clearance appears both in Basic Qualifications and later; we should include only once. We'll include under Requirements/Qualifications.
We need to output only HTML fragment, no markdown fences.
We'll structure:
About the role
...
Responsibilities
- ... ...
Qualifications
Maybe split into Required and Preferred? Could have subheadings? But only allowed headings from list; we could useRequirements
andPreferred Qualifications
but those are not in list? Actually list includes Requirements, Qualifications, Skills. We could useQualifications
and inside have twoor
- for required and preferred. Or we could use
- Analyzes the integration of complex airplane systems and their corresponding airplane-level effects, failure indications, and flight crew actions as part of a system of systems analysis
- Documents safety analyses, hazard mitigation, validation, and verification activities in compliance with relevant customer and regulatory safety standards such as MIL‑STD‑882E, MIL‑HDBK-516C, AC-17-01, DO-178C, and DO-254.
- Demonstrates safety hazard risk mitigation and control methods to the customer and regulators
- Identifies safety issue systemic root causes and recommends corrective actions using industry best practices
- Collaborates with internal and external stakeholders to define, validate, and integrate safety requirements
- Participates in tests and analyses to verify that systems meet the defined safety requirements
- Resolves multi-functional technical issues
- Bachelor of Science degree in Engineering, Engineering Technology (including Manufacturing Technology), Computer Science, Data Science, Mathematics, Physics, Chemistry or non-US equivalent qualifications directly related to the work statement
- Level 3: 5+ years of experience working in an engineering, engineering technology, or related technical discipline
- Ability to obtain a U.S. Security Clearance for which the U
Requirements
for required andPreferred Qualifications
for preferred (though not in list). Safer to useQualifications
and then within havefor required and
for preferred. But we also have Skills maybe not needed. We'll also have
Pay
with pay ranges and maybe compensation description.Benefits
with benefits description and relocation.Schedule
with shift. We must not include sections with filler like "commensurate with experience". We have specific content. Now craft HTML. We need to ensure we preserve all substantive info: include mention of Hazelwood, MO location, Proprietary Air Dominance program, etc. Let's write. Check for any duplicated lines: we have security clearance mentioned twice; we will include once under Qualifications. We'll include relocation under Benefits. We'll include visa sponsorship maybe under Requirements? Could be under Qualifications as a note. But we could also put under Benefits? It's not a benefit. Could be under Requirements as a note: "Employer will not sponsor applicants for employment visa status." We'll include under Qualifications as a bullet. Now produce HTML. Be careful to escape any HTML special characters like &, <, >. The text includes "MIL‑STD‑882E" with hyphen and maybe non-breaking hyphen? We'll keep as is. We'll output:About the role
At Boeing, we innovate and collaborate to make the world a better place. We’re committed to fostering an environment for every teammate that’s welcoming, respectful and inclusive, with great opportunity for professional growth. Find your future with us. The Boeing Defense Air Dominance Division Systems Safety & Mission Assurance organization is looking for an Aerospace Systems Safety Engineer to join our team in Hazelwood, MO. Our teams are currently hiring for a broad range of experience levels including Experienced (Level 3) or Senior (Level 4) Aircraft Safety Engineers. A successful candidate will perform system software safety engineering work on a Proprietary Air Dominance program, drive hazard analyses, demonstrate compliance to MIL‑STD‑882E and other standards, and influence system architecture to reduce safety risk. The selected candidate will provide technical guidance and perform critical Software System Safety Engineering work. In addition to working with System Safety personnel, the individual will work extensively with design, development, and test to incorporate robust safety features and reduce project safety risk.
Responsibilities
Qualifications
Required: