ICBM Minuteman Flight Control Systems Engineer (Associate or Mid-Level)

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). We need to include sections only when posting has real specific content. We have: - Intro: "Job Description At Boeing, we innovate..." That's about the role/company. Could be "About the role". We'll put that as

. - Responsibilities: list bullet points after "Position Responsibilities:" with multiple lines. We'll make

• . - Basic Qualifications (Required Skills and Experience): list bullet points? It's a paragraph with bullet-like lines: Bachelor of Science degree..., Level 2..., Level 3... We'll treat as list. - Preferred Qualifications (Desired Skills and Experience): list bullet points. - Pay & Benefits: includes description of total rewards, specific pay ranges for Level 2 and Level 3. So we need Pay section (maybe also Benefits). The instruction: only create Pay/Schedule/Benefits sections if posting actually states them. It does state Pay ranges and benefits description. So we can have a

  Pay

  with the pay ranges and maybe benefits description. Could also have Benefits section but we can combine? The instruction says prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one section? But they gave examples of separate headings. However we can decide to have Pay section with pay ranges and benefits description. Since they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state both pay and benefits. Could make two sections: Pay and Benefits. But we might combine to avoid thin sections. However the benefits description is substantive. Could make Benefits section with the description of total rewards. Pay section with the specific ranges. That seems okay. - Schedule: mention "Shift This position is for 1st shift". That's schedule info. So we can have Schedule section. - Other metadata like Relocation, Conflict of Interest, Drug Free Workplace, Export Control, Security Clearance, Visa Sponsorship, Contingent Upon Program Award, Equal Opportunity Employer. Those are boilerplate? Some are specific: Relocation assistance is not a negotiable benefit; Conflict of Interest assessment; Drug Free Workplace; Export Control Requirements; Security Clearance; Visa Sponsorship; Shift; Contingent Upon Program Award; Equal Opportunity Employer. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. EEO/equal-opportunity is boilerplate; we should remove Equal Opportunity Employer line. Conflict of Interest, Drug Free Workplace, Export Control, Security Clearance, Visa Sponsorship, Relocation, Contingent Upon Program Award might be considered legal boilerplate? The instruction says remove legal/EEO/equal-opportunity/scam-warning boilerplate. Conflict of Interest maybe legal; Drug Free Workplace maybe policy; Export Control maybe legal; Security Clearance maybe requirement; Visa Sponsorship maybe legal; Contingent Upon Program Award maybe program-specific. Not sure. The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." So we should remove legal boilerplate. Conflict of Interest, Drug Free Workplace, Export Control, Security Clearance, Visa Sponsorship are legal/policy. Might be considered boilerplate. However they are specific to the job; but still legal. Safer to remove them? The instruction says remove legal boilerplate. So we should omit those sections. However we need to preserve ALL substantive information; do NOT invent or summarize away detail. If we remove legal info, we might be losing substantive info (like requirement for US Person, security clearance). Those are substantive. The instruction says remove legal boilerplate, but those are not boilerplate? They are specific requirements. However they are legal in nature. The instruction may intend to remove standard EEO statements, not job-specific legal requirements like security clearance. But ambiguous. Usually in such tasks, they want to keep requirements like security clearance, export control, relocation, etc. The boilerplate removal is for generic statements like "We are an equal opportunity employer", "EEO", "scam warning". So we keep Conflict of Interest? Might be considered boilerplate but it's specific to the company. I'd keep it as a short paragraph maybe under a section like "Additional Information". But we don't have a heading for that. Could incorporate into a paragraph under "About the role" or as a separate

  . The instruction says use

  for section headings (list). It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should only use those headings. Additional info could be placed in a

  under About the role or maybe not needed. But we need to preserve all substantive info. So we need to include Conflict of Interest, Relocation, Drug Free Workplace, Export Control, Security Clearance, Visa Sponsorship, Shift, Contingent Upon Program Award. Some of these are covered by Schedule (Shift). Relocation we could mention in a paragraph. Conflict of Interest maybe we can note in a paragraph. Drug Free Workplace maybe we can note. Export Control and Security Clearance maybe we can note. Visa Sponsorship maybe note. Contingent Upon Program Award maybe note. We could create a section "Requirements" to hold qualifications (basic and preferred). Actually we have Basic Qualifications and Preferred Qualifications. Could combine into Requirements section with sub-lists? But we need to follow headings: Requirements, Qualifications, Skills. The examples include Requirements, Qualifications, Skills. We could use Requirements for basic qualifications, Qualifications for preferred, Skills for tools? But we have both basic and preferred. Might be better to have Requirements (basic) and Qualifications (preferred). Skills maybe not needed. We also have "Skills" maybe for tools like DOORS, MSOSA. But we already have those in preferred. Simplify: Use sections: About the role (intro), Responsibilities, Requirements (basic qualifications), Qualifications (preferred qualifications), Pay, Benefits, Schedule. That seems reasonable. Now we need to extract content. About the role: The first paragraph: "Job Description 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 Associate and Mid-Level 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." We should remove "Job Description" maybe as it's redundant. Keep the rest. Responsibilities: list bullet points: - 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 Requirements (basic qualifications): bullet points: - 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 2: 2+ years of related work experience and a bachelor’s degree or an equivalent combination of related work experience and technical education - Level 3: 5+ years of related work experience and a bachelor’s degree or an equivalent combination of related work experience and technical education Qualifications (preferred): bullet points: - ICBM Minuteman knowledge and experience - Experience utilizing automated test equipment - Experience performing root cause failure analysis - Experience with requirements development - Experience using modern tools such as DOORS and MSOSA Pay: include summary pay range: - Level 2: $93,500-$126,500 - Level 3: $115,600-$156,400 Also maybe mention that pay is based on candidate experience and qualifications, market and business considerations. Could include that as prose. Benefits: description: "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." Schedule: "Shift This position is for 1st shift". Also maybe mention "Contingent Upon Program Award" but that's not schedule. Could be additional note but maybe we can include as a short paragraph under Schedule? Might be better to add a short paragraph under Schedule about shift and contingency. But the instruction says only create Schedule section if posting actually states them. It does state shift. Contingent Upon Program Award is not schedule; maybe we can include in a paragraph under About the role or as a separate

  without heading. But we are only allowed to use

  for section headings; we can still have

  without heading. So we can add a

  for that info. Similarly, we might include Conflict of Interest, Relocation, Drug Free Workplace, Export Control, Security Clearance, Visa Sponsorship as

  paragraphs maybe under About the role or after sections. But we need to preserve all substantive info. Let's decide to add a

  after Schedule for additional notes: Conflict of Interest, Relocation, Drug Free Workplace, Export Control, Security Clearance, Visa Sponsorship, Contingent Upon Program Award. But that may be many lines; we can combine into a paragraph. But we must not include boilerplate legal statements. However these are specific requirements; I'd keep them. Let's craft HTML:

  About the role

  Boeing innovates and collaborates to make the world a better place, fostering a welcoming, respectful, and inclusive environment with great opportunity for professional growth. Boeing is seeking enthusiastic and skilled Associate and Mid-Level Engineers to help sustain the ICBM Minuteman III Weapon System, 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—including flight control hardware, flight batteries, raceway cables, and automated test equipment—at Hill Air Force Base, UT, collaborating with engineers and technical teammates in a setting where your ideas and talents 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