ICBM Minuteman Flight Control Systems Engineer (Senior or Expert)

We need to output HTML fragment with sections: About the role? The description includes introductory paragraph about Boeing, mission, etc. That could be "About the role" or maybe "About the role" is generic. The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use

• for any list of duties/requirements/benefits, and

  for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. We need to decide which sections to include based on content. Content: - Intro paragraph: "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." This is generic company description. Could be "About the role"? Might be better as "About the role" or maybe "About Boeing". The instruction says we can use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use "About the role" for that intro. - Then: "Boeing is seeking enthusiastic and skilled Senior or Expert Engineers to help sustain the ICBM Minuteman III Weapon System, which is a land-based strategic nuclear deterrent for the United States. As part of the Propulsion Integrated Product Team (IPT), you’ll work with flight control systems to include flight control hardware, flight batteries, raceway cables, and automated test equipment. You’ll work alongside other engineers and technical teammates at Hill Air Force Base, UT in a collaborative work environment where your ideas and talents will make a positive impact." This is also role description; could be part of About the role. - Then "Position Responsibilities:" followed by bullet list (though not bullet but sentences separated by line breaks). We need to convert to

  • . List items: - Develop requirements for hardware or software using Model Based Systems Engineering (MBSE) and modern software tools such as DOORS and MSOSA - Develop and execute test procedures and conduct test data analysis to validate system requirements and objectives - Troubleshoot, diagnose, and resolve issues with flight control systems - Support maintenance of automated test equipment - Prepare technical reports and briefings to convey technical information to stakeholders - Collaborate with stakeholders to implement corrective actions and improve system reliability - Review, update, and maintain technical documentation including drawings and processes - Apply engineering principles to identify opportunities for design improvement, test efficiency, and long-term system sustainment - Then "Basic Qualifications (Required Skills and Experience):" followed by bullet list: - 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 4: 9+ years of related work experience and a bachelor’s degree or an equivalent combination of related work experience and technical education - Level 5: 14+ years of related work experience and a bachelor’s degree or an equivalent combination of related work experience and technical education We could treat Basic Qualifications as Requirements or Qualifications. The instruction includes headings Requirements, Qualifications, Skills. We need to decide which to use. Probably "Requirements" for basic qualifications, and "Preferred Qualifications" could be "Skills" or "Qualifications". But we should avoid duplication. Perhaps we have sections: About the role, Responsibilities, Requirements (basic qualifications), Preferred Qualifications (maybe as Skills). Also we have Pay & Benefits section with pay ranges and benefits description. That is substantive: they give pay ranges and benefits description. So we should include Pay and Benefits sections? The instruction says: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state Pay & Benefits: includes summary pay range and description of benefits. So we should include a Pay section (maybe with the pay ranges) and a Benefits section (maybe with description). However they said prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But headings list includes Pay, Benefits, Schedule separate. We could make a Pay section with the pay ranges, and a Benefits section with the benefits description. That seems okay. Also there is info about Relocation, Conflict of Interest, Drug Free Workplace, Union represented, Export Control, Security Clearance, Visa Sponsorship, Shift, Contingent Upon Program Award, Equal Opportunity Employer. Many of these are boilerplate/legal. We should remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we should drop those sections: Conflict of Interest, Relocation (though it's mentioned but it's a policy; maybe we can drop as it's not substantive? It says "Relocation assistance is not a negotiable benefit for this position." That's a detail about relocation; could be considered part of Benefits? But it's a negative. Might be considered boilerplate. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. Relocation assistance statement might be considered policy but not EEO. It's not exactly legal but could be considered minor metadata. We could fold into a short

    or drop it. Since they said fold minor metadata into a short

    or drop it. So we could include a short paragraph about relocation under maybe Benefits? But better to drop. Similarly "This is a union represented position." Could be minor metadata. "Drug Free Workplace: ..." is legal/policy; drop. "Export Control Requirements: ..." is also legal; maybe drop unless it's substantive for the role (U.S. Person required). That could be considered a requirement (citizenship). Might be worth including as a requirement? But it's more legal. The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. Export control is legal; drop. "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. Secret Clearance Post-Start is required." That's also legal/security; maybe drop. "Visa Sponsorship Employer will not sponsor applicants for employment visa status." drop. "Shift This position is for 1st shift" could be schedule info; we could include Schedule section if they state shift. They state shift is 1st shift. That's specific schedule info. So we could include a Schedule section with "1st shift". "Contingent Upon Program Award The position is contingent upon program award" maybe minor metadata; could drop. "Equal Opportunity Employer: ..." drop. Thus we keep: About the role (intro), Responsibilities (list), Requirements (basic qualifications), Skills (preferred qualifications), Pay (pay ranges), Benefits (benefits description), Schedule (shift). Possibly also Qualifications? But we have Requirements and Skills; that covers. We need to ensure we don't create sections with filler text. All have real content. Now format: Use

    for each section heading. Then content: For prose use

    . For lists use

    • . For Pay section: we have pay ranges: Level 4: $142,800-$193,200; Level 5: $170,850-$231,150. Also mention that pay based on experience etc. Could include that as prose. The posting also says: "Pay is based upon candidate experience and qualifications, as well as market and business considerations." That's prose. So we can put that in a

      then maybe a

      for the ranges? Or just include in

      . Since they said use

      • for any list of duties/requirements/benefits. Pay ranges could be considered a list; we could do
        • Level 4: $142,800-$193,200
        • Level 5: $170,850-$231,150
        . Also include the prose about pay determination. Benefits section: The posting says: "At Boeing, we strive to deliver a Total Rewards package that will attract, engage and retain the top talent. Elements of the Total Rewards package include competitive base pay and variable compensation opportunities. The Boeing Company also provides eligible employees with an opportunity to enroll in a variety of benefit programs, generally including health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, and a number of programs that provide for both paid and unpaid time away from work. The specific programs and options available to any given employee may vary depending on eligibility factors such as geographic location, date of hire, and the applicability of collective bargaining agreements." That's prose; we could also list benefits as
        • but they said use
          • for any list of duties/requirements/benefits. So we could make a list of benefits: health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, paid and unpaid time away programs. Also mention competitive base pay and variable compensation opportunities maybe as part of benefits? But we already have Pay section. So Benefits section list: health insurance, flexible spending accounts, health savings accounts, retirement savings plans, life and disability insurance programs, paid and unpaid time away programs. Also note that specifics vary. Schedule section: "This position is for 1st shift". Could be just

            1st shift

            . Now we need to ensure we don't repeat the job title as heading. We aren't. We need to output only HTML fragment. Let's craft:

            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. Boeing is seeking enthusiastic and skilled Senior or Expert Engineers to help sustain the ICBM Minuteman III Weapon System, which is a land-based strategic nuclear deterrent for the United States. As part of the Propulsion Integrated Product Team (IPT), you’ll work with flight control systems to include flight control hardware, flight batteries, raceway cables, and automated test equipment. You’ll work alongside other engineers and technical teammates at Hill Air Force Base, UT in a collaborative work environment where your ideas and talents will make a positive impact.

            Responsibilities

            • Develop requirements for hardware or software using Model Based Systems Engineering (MBSE) and modern software tools such as DOORS and MSOSA
            • Develop and execute test procedures and conduct test data analysis to validate system requirements and objectives
            • Troubleshoot, diagnose, and resolve issues with flight control systems
            • Support maintenance of automated test equipment
            • Prepare technical reports and briefings to convey technical information to stakeholders
            • Collaborate with stakeholders to implement corrective actions and improve system reliability
            • Review, update, and maintain technical documentation including drawings and processes
            • Apply engineering principles to identify opportunities for design improvement, test efficiency, and long-term system sustainment