Senior System Safety Engineer
Odyssey · Dayton, OH · 1 mo ago
Information Technology$22/hrFull-time
We need to output HTML fragment with sections only if content present. Use for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to include sections for content present.
Let's parse posting:
Position Summary: description about Odyssey recruiting for Senior System Safety Engineer... That's about the role. So we can have
for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title. We need to include sections for content present.
Let's parse posting:
Position Summary: description about Odyssey recruiting for Senior System Safety Engineer... That's about the role. So we can have About the role
with paragraph(s) summarizing.
Responsibilities: list of duties. Use - .
Qualifications: includes citizenship, clearance, education, etc. Could be under Requirements? The posting has "Qualifications" with Minimum Required Qualifications and Preferred Qualifications. Also "Technical Skills". We need to decide sections: maybe "Requirements" for minimum required qualifications, "Qualifications" for preferred? But spec says use headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map:
- About the role: position summary.
- Responsibilities: duties list.
- Requirements: Minimum Required Qualifications (citizenship, clearance, education, experience).
- Qualifications: Preferred Qualifications (experience with USG aircraft certification, Airworthiness course).
- Skills: Technical Skills list.
- Benefits: Not mentioned explicitly; there is no benefits info. So we should NOT include Benefits section.
- Pay: Not specified (they mention final compensation determined by factors but no actual pay). So we should NOT include Pay section because no specific pay.
- Schedule: Not specified (maybe location, travel 10%, onsite). There's location and travel info. Could be considered schedule? Not really. The spec says only include Schedule if posting actually states them. It mentions Travel: 10% Remote, Onsite, or Hybrid: Onsite. That's about work arrangement, not schedule. Could be considered schedule? Probably not. Safer to omit Schedule.
Thus we output sections: About the role, Responsibilities, Requirements, Qualifications, Skills.
We must preserve all substantive information, not invent or summarize away detail. Need to include all details from posting.
Let's extract:
About the role: "Odyssey is recruiting for a Senior System Safety Engineer to support the Attack Systems Division, Foreign Military Sales (FMS), at Wright Patterson AFB, OH. WID is part of the ISR/SOF Directorate (AFLCMC/WI), who is responsible for equipping our warfighters to win the fight. The Directorate executes a $22 billion acquisition portfolio developing, producing, testing, modifying, fielding, and supporting Air Force ISR and SOF platforms, and related sub-systems."
We can keep as paragraph.
Responsibilities: list bullet points from "Duties include, but not limited to:" then many items. We'll need to capture each bullet.
Let's list them:
- Apply common engineering/scientific principles, processes and procedures to improve performance and sustainability of existing and future joint service weapon systems.
- Support the acquisition program management of full life cycle requirements, subsystems, and equipment.
- Apply knowledge of Airworthiness Certification Criteria, to aircraft systems and subsystems.
- Assist in translating and developing user requirements into weapon system requirements.
- Perform technical/mission analyses of existing and future operational requirements, assist in developing system concepts and perform technological/trade-off assessments of proposed designs/modifications.
- Support the system safety engineering program, including mishap risk assessments; evaluate weapon system contractor safety proposals and safety analyses; evaluate safety concerns and assist with resolution of high priority safety issues.
- Produce, or support development of draft documentation and presentation materials as requested or necessitated by programmatic limits based on cost, schedule, and performance.
- Provide support to produce or review products to include: technical evaluations/plans; engineering studies, reports and analyses; acquisition strategies/plans; System Specification; SEPs; TEMPs; PESHE; Technology Assessment/Control Plan (TA/CP); Information Assurance Strategy (IAS); Test and Evaluation Plan; airworthiness inputs, and other program/technical documents as required.
- Perform system safety management services in support of the acquisition of Government approved system or sub-system production, sustainment, modifications, maintenance, upgrades, and modernization.
- Performing analysis of or recommending changes to the following: technical guidance; test plans; specification data; safety critical function processes; critical safety item listing; subject matter related reports; safety assessment reports; hazard worksheets and memos; hazard analysis; system safety program plan; mishap guide; USAF mishap reports; mishap recommendations; and technical input for program requirements (e.g., specifications).
- Provide consistent and reliable guidance to leadership on system safety matters.
- Ensure requirements of individual items of equipment, subsystems, and support equipment are integrated and established in such a manner that adequate, complete, and effective safety requirements are met within the constraints imposed by cost, schedule, and performance.
- Execute other functional duties as assigned by the directorate system safety manager, division chief engineers, or their delegated authority.
- Develop and collect technical data and inputs for eSSS packages and executive briefings.
- Support and provide assistance to project team meetings, working groups, and reviews: SRRs, PDRs, CDRs, TRRs, TCMs, TIMs, FCAs, PCAs, PRRs, PMRs, risk management meetings, and other meetings/working groups/reviews as applicable.
- Assist in the engineering evaluation of prime weapon system contractor and subcontractor recommendations for operational and support issues such as: evaluations of ACSNs, ECPs, CCPs, FAA Bulletins, modification proposals, DMSMS, program risk, and related documents.
- Support performance of disciplined engineering activities to assure Occupational Safety, Suitability and Effectiveness (OSS&E) for all products.
- Interface with other technical/management directorates and/or IPTs to ensure safety policy, requirements, and objectives are met.
- Assist in monitoring and working incident reports within the program.
- Assist in identifying and managing the hazard tracking and risk resolution process and advise leadership of high/serious.
That's a lot. We'll keep them as
- .
Requirements (Minimum Required Qualifications):
- Citizenship: Must be a US citizen
- Clearance: Secret
- Education: Master’s or Doctorate Degree in a related field and 10 years of experience in the respective technical / professional discipline being performed, 5 years of which must be in the DoD. OR bachelor’s degree in a related field and 12 years of experience in the respective technical/professional discipline being performed, 5 of which must be in the DoD.
We need to preserve that exactly.
Qualifications (Preferred Qualifications):
- Minimum of 1 year experience with the USG aircraft and project certification process, including familiarity with the MIL-HDBK-516.
- Have completed or can complete Airworthiness course completions within 18 months (DAIR 116, DAIR 216, WKSP 0691, DAIR 316)
Skills (Technical Skills):
List:
- Ability to translate user needs into system-level requirements, perform system concept development, evaluate design trade‑offs, and ensure requirements traceability across the weapon system lifecycle
- Proficiency in applying Airworthiness Certification Criteria (e.g., MIL‑HDBK‑516) to aircraft systems and subsystems, identifying compliance gaps, and supporting airworthiness approval packages
- Skilled in performing hazard analyses, developing and managing hazard tracking systems, evaluating contractor safety proposals, conducting mishap investigations, and preparing formal safety documentation (e.g., SARs, PESHE, TA/CP)
- Experience in conducting mission/technical analyses for current and future operational requirements, assessing technological alternatives, evaluating modifications (ACSNs, ECPs, CCPs), and analyzing sustainment and modernization impacts throughout the system life cycle
- Ability to support acquisition program management by producing and reviewing engineering deliverables such as System Specifications, SEPs, TEMPs, Test and Evaluation Plans, Technology Assessments, Information Assurance Strategies, and other programmatic documentation tied to cost, schedule, and performance constraints
We should preserve bullet points.
Also there is Additional Information: Location: WPAFB Travel: 10% Remote, Onsite, or Hybrid: Onsite Company Overview ... This is extra info but not under defined headings. Should we include? The spec says we should preserve ALL substantive information; do not invent or summarize away detail. So we need to include location and travel info somewhere. Could be part of About the role or a separate section? There's no heading for location/travel. Could add a paragraph under About the role after the summary. Or we could create a section "Location and Travel" but not in allowed headings. The allowed headings list does not include location/travel. However we must not create extra headings beyond those? The instruction: "use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings for sections. It also says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid other headings, but likely they expect only those headings. However we need to preserve location and travel info. Could we embed it in About the role paragraph? That would preserve info. Let's do that: after the summary, add a sentence: "The position is located at Wright Patterson AFB, OH (WPAFB) with approximately 10% travel; work arrangement is onsite."
That preserves.
Company Overview: also substantive. Could we include in About the role as well? Might be too much but we can add a paragraph about company overview. The spec says preserve ALL substantive information. So we need to include company overview details. We can add another paragraph under About the role after location/travel.
Thus About the role will contain multiple paragraphs: position summary, location/travel, company overview.
We must not include boilerplate like EEO etc. The posting ends with compensation note. We already omitted Pay because no specific pay. The compensation note is about final compensation determined by factors; that's not a specific pay range, so we omit Pay section.
Now produce HTML fragment.
Structure:
About the role
...
...
...
Responsibilities
- ...
...
Requirements
- Citizenship: Must be a US citizen
- Clearance: Secret
- Education: Master’s or Doctorate Degree in a related field and 10 years of experience in the respective technical / professional discipline being performed, 5 years of which must be in the DoD. OR bachelor’s degree in a related field and 12 years of experience in the respective technical/professional discipline being performed, 5 of which must be in the DoD.
Qualifications
- Minimum of 1 year experience with the USG aircraft and project certification process, including familiarity with the MIL-HDBK-516.
- Have completed or can complete Airworthiness course completions within 18 months (DAIR 116, DAIR 216, WKSP 0691, DAIR 316)
Skills
- Ability to translate user needs into system-level requirements, perform system concept development, evaluate design trade‑offs, and ensure requirements traceability across the weapon system lifecycle
- Proficiency in applying Airworthiness Certification Criteria (e.g., MIL‑HDBK‑516) to aircraft systems and subsystems, identifying compliance gaps, and supporting airworthiness approval packages
- Skilled in performing hazard analyses, developing and managing hazard tracking systems, evaluating contractor safety proposals, conducting mishap investigations, and preparing formal safety documentation (e.g., SARs, PESHE, TA/CP)
- Experience in conducting mission/technical analyses for current and future operational requirements, assessing
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but we should use those headings for sections. It also says "include a section ONLY when the posting has real, specific content for it". It doesn't forbid other headings, but likely they expect only those headings. However we need to preserve location and travel info. Could we embed it in About the role paragraph? That would preserve info. Let's do that: after the summary, add a sentence: "The position is located at Wright Patterson AFB, OH (WPAFB) with approximately 10% travel; work arrangement is onsite."
That preserves.
Company Overview: also substantive. Could we include in About the role as well? Might be too much but we can add a paragraph about company overview. The spec says preserve ALL substantive information. So we need to include company overview details. We can add another paragraph under About the role after location/travel.
Thus About the role will contain multiple paragraphs: position summary, location/travel, company overview.
We must not include boilerplate like EEO etc. The posting ends with compensation note. We already omitted Pay because no specific pay. The compensation note is about final compensation determined by factors; that's not a specific pay range, so we omit Pay section.
Now produce HTML fragment.
Structure:
About the role
...
...
...
Responsibilities
- ... ...
Requirements
- Citizenship: Must be a US citizen
- Clearance: Secret
- Education: Master’s or Doctorate Degree in a related field and 10 years of experience in the respective technical / professional discipline being performed, 5 years of which must be in the DoD. OR bachelor’s degree in a related field and 12 years of experience in the respective technical/professional discipline being performed, 5 of which must be in the DoD.
Qualifications
- Minimum of 1 year experience with the USG aircraft and project certification process, including familiarity with the MIL-HDBK-516.
- Have completed or can complete Airworthiness course completions within 18 months (DAIR 116, DAIR 216, WKSP 0691, DAIR 316)
Skills
- Ability to translate user needs into system-level requirements, perform system concept development, evaluate design trade‑offs, and ensure requirements traceability across the weapon system lifecycle
- Proficiency in applying Airworthiness Certification Criteria (e.g., MIL‑HDBK‑516) to aircraft systems and subsystems, identifying compliance gaps, and supporting airworthiness approval packages
- Skilled in performing hazard analyses, developing and managing hazard tracking systems, evaluating contractor safety proposals, conducting mishap investigations, and preparing formal safety documentation (e.g., SARs, PESHE, TA/CP)
- Experience in conducting mission/technical analyses for current and future operational requirements, assessing