SME Systems Engineer

We need to output HTML fragment with sections: h3 for headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. Must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Must preserve all substantive information. We need to parse the posting. Key content: - Position Description & Qualifications: intro about cutting-edge DoD programs, Serco opportunity. As a SME Systems Engineer specializing in aircraft sub-system integration, airworthiness, and electronic warfare, supporting Special Programs Division (AFLCMC/WAG) at Wright Patterson AFB, OH. Contingent upon ability to maintain/transfer active Department of War (DoW) Top Secret security clearance with ability to obtain TS/SCI. (Note: Department of War? Probably DoD.) - Description of Fighters and Advanced Aircraft Directorate, Special Programs Division: develops, tests, and rapidly fields classified USAF aeronautical capabilities. AFLCMC/WAG conducts studies to identify new capabilities; transitions laboratory technologies to operational platforms; executes demonstrations; and develops, tests, rapidly fields, sustains, and demilitarizes capabilities for the warfighter. - In This Role, You Will Be a Subject Matter Expert in electronic warfare and systems engineering supporting classified programs utilizing DoD, USAF and common engineering/scientific principles, and procedures. Then bullet list of duties: - Translate operational user requirements into contract system requirements documents. - Apply systems engineering expertise for modification improvements, hardware/software development, configuration management, data rights, and quality assurance. - Provide technical and programmatic feedback, develop and present technical briefings, and develop engineering strategies/analyses and technical program documents. - Interface with weapons system contractors, vendors, and Government representatives on engineering activities; independently apply engineering principles to investigate, analyze, plan, oversee, and evaluate weapons system development and sustainment. - Assess AFRL technology initiatives to guide investments and shape transition strategies to keep a viable technology base available to support systems development. - Develop system-of-systems architectures and digital transformation strategies for programs. - Implement aircraft airworthiness, risk management, and obsolescence tracking processes. - Evaluate Contractor proposed design changes and solutions, perform systems analyses and technological/trade-off study assessments, and oversee the correction of deficiencies. - Support all phases of subsystem component and system-level integration and testing: develop and review test plans/procedures, test activities oversight, and test result analysis. - Assess contractor product capabilities in achieving system design requirements and specifications - Perform technical risk assessments and develop mitigation plans. - Develop request for proposal (RFP) technical documents and conduct technical evaluations of contractor proposals to include design feasibility and system compatibility. - To Be Successful In This Role, You Will Have: - An active TOP-SECRET security clearance with the ability to obtain and maintain Sensitive Compartmented Information (SCI) and access to Special Access Programs (SAP) and have a background investigation current within the past 5 years or under Continuous Vetting - Masters Degree in an Engineering discipline with a minimum of 20 years relevant experience with the DoD, other government agency, or DoD contractor - Minimum 3 years of SAP or SCI experience within the last 5 years - Ability to travel up to 10% (CONUS) - Additional Desired Experience And Skills: - In-depth knowledge of DoD acquisition engineering and test support - Electronic warfare engineering experience - Expertise in airworthiness, avionics and other aircraft systems and host platform integration - Defense Acquisition Workforce Improvement Act (DAWIA) certification in Systems Planning, Research, Development and Engineering - Company Overview: description of Serco, etc. Might be considered "About the company" but not required heading? Could be "About the role" maybe includes role description. The instructions: use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections we have content for. We have: - About the role: could be the introductory paragraph describing the role, mission, etc. Could include the first paragraph about cutting-edge DoD programs, supporting Special Programs Division, etc. That seems appropriate. - Responsibilities: the bullet list under "In This Role, You Will Be a Subject Matter Expert..." (the duties). That is responsibilities. - Requirements: the mandatory qualifications: active TS/SCI clearance, Masters degree + 20 years experience, 3 years SAP/SCI experience, travel up to 10%. That's requirements. - Qualifications: maybe overlapping with requirements; but we could treat "To Be Successful In This Role, You Will Have" as Requirements. Then "Additional Desired Experience And Skills" could be Skills or Qualifications (desired). The instructions: we can have Qualifications and Skills separate. We could put mandatory qualifications under Requirements, and desired skills under Skills. - Benefits: The posting includes a Pay Transparency section and Benefits section later. There's a paragraph about Pay Transparency: "Our Total Rewards package includes competitive pay, performance-based incentives, and benefits that promote well-being and work-life balance..." Then details about benefits: medical, dental, vision, vacation, 401(k), tuition reimbursement, life insurance, disability, optional coverages, parental leave, Employee Assistance Plan. Also mention to review Serco benefits at URL. So we have benefits content. - Pay: The posting includes "Salary range: The range for this position can be found at the top of this posting. This range is provided as a general guideline..." It does not give actual numbers. It says range can be found at top of posting (but we don't have that). It says actual base salary determined by factors. This is vague; we should not create a Pay section unless posting actually states them. It does mention salary range but not actual numbers; it says range can be found at top of posting (which we don't have). The instruction: "never emit a heading followed by filler/placeholder text (e.g. 'commensurate with experience', 'not specified', 'N/A', 'varies', 'TBD')". The Pay section would be placeholder if we don't have actual numbers. So we should NOT include Pay section. - Schedule: Not mentioned. No schedule info. So omit. - Also we might include an "About the company" section? Not in allowed headings list. Could include under "About the role"? Probably not. The allowed headings are limited to those; we should not add others. So we stick to About the role, Responsibilities, Requirements, Skills, Benefits. We need to preserve all substantive information; do not invent or summarize away detail. So we need to include all details from the posting, but we can format as

prose or

• for lists. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. So we need to cut out: - "If you are interested in supporting and working with our Air Force and airmen and a dedicated Serco team, then submit your application now for immediate consideration. It only takes a few minutes!" (application instruction) -> remove. - Company Overview: Might be considered not boilerplate but descriptive of Serco; it's substantive? It's about the company, not the role. The instructions didn't forbid company overview; but we only have allowed headings. Could we include it under "About the role"? Probably not appropriate. Might be considered filler? It's not about the role. The instruction: "Prefer a few substantive sections over many thin ones." We could omit company overview if not fitting headings. However, we must preserve ALL substantive information; but if we cannot fit it under allowed headings, maybe we should still include it as a

  without heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for section headings. It might be okay to include other headings? The instruction: "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we could still use other headings but they'd be non-standard. Safer to stick to those. Company overview could be placed under "About the role"? Not really. Could be omitted as it's not directly about the role but still substantive. However, the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. If we omit company overview, we are losing substantive info. But maybe it's considered boilerplate? It's a generic description of Serco; could be considered boilerplate but it's specific to Serco. The instruction to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company overview is not listed as boilerplate to remove. So we should keep it. We could create a section "About the company" but not in allowed headings. However, we could treat it as part of "About the role"? Might be a stretch. Perhaps we can include a heading "About the company" using

  even though not listed; the instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). The "e.g." suggests those are examples, not an exhaustive list. So we can use other headings as needed, as long as we use

  . So we can add "About the company". That seems fine. Similarly, we could have "Pay Transparency" but we decided not to include Pay because no concrete numbers. But we could include a Pay section with the description about total rewards, but that is more benefits. The Pay Transparency paragraph mentions competitive pay etc. It's vague; but we could still include a Pay section with that prose, as it's substantive (they talk about total rewards). However, the instruction says never emit a heading followed by filler/placeholder text like "commensurate with experience", "not specified", "N/A", "varies", "TBD". The Pay Transparency paragraph does not contain those; it's a description of total rewards. It does mention "competitive pay, performance-based incentives". That's not a specific number but it's not filler. It's okay to include Pay section with that description. However, they also have a separate Benefits section later. The Pay Transparency paragraph is more about total rewards; we could combine with Benefits. But we have separate Benefits heading allowed. We could put the Pay Transparency content under Benefits? It mentions pay and benefits. Might be better to have a Pay section with that paragraph, and Benefits section with the list of benefits. But the instruction: "Prefer a few substantive sections over many thin ones." Having both Pay and Benefits may be thin if they overlap. However, the Pay Transparency paragraph is short; Benefits list is longer. Could combine them under Benefits? But the Benefits heading is allowed; we could include pay description there as part of benefits. However, the Benefits heading is for benefits; pay is not a benefit but compensation. The instruction says we can create Pay section only if posting actually states them. It does state something about pay (competitive pay, performance-based incentives). So we can include Pay section. Thus sections: About the role, Responsibilities, Requirements, Skills, Benefits, Pay. Possibly also About the company. We need to ensure we don't repeat job title as heading. Not needed. Now we need to extract content for each section. Let's parse: **About the role**: Could be the introductory paragraph(s) that describe the role and its context: "If you want to work on cutting-edge DoD programs, Serco has a great opportunity for you! As a SME Systems Engineer specializing in aircraft sub-system integration, airworthiness, and electronic warfare, you will be supporting the Special Programs Division (AFLCMC/WAG) at Wright Patterson AFB, OH. This position is