Mechanical Engineer (Mid-Level)

We need to output HTML fragment with sections: About the role? The description includes intro paragraphs. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. We have: - About the role: we have description of Boeing, team, location, program. That's content. - Responsibilities: there is a list of responsibilities under "Position Responsibilities:" with bullet-like sentences. We can treat as list. - Requirements: Basic Qualifications (Required Skills and Experience) includes degree, years experience. - Qualifications: Preferred Qualifications (Desired Skills and Experience) includes experience with USAF, electromechanical assemblies, analog/digital design, obsolescence sustainment. - Skills: maybe we can combine responsibilities and qualifications? But we need separate sections if content exists. There's also "Analytical Skills (Technical): ..." etc. Those are more like skill descriptions. Could go under Skills. - Benefits: there is description of Boeing 401(k), Student Loan Match, etc. Also mention health insurance etc. So Benefits section. - Pay: there is "Summary pay range: $103,700-$140,300". Also mention Pay based on experience. So Pay section. - Schedule: there is "Shift This position is for 1st shift". So Schedule section. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Also remove "Conflict of Interest", "Drug Free Workplace", "Export Control Requirements", "Visa Sponsorship", "Equal Opportunity Employer". Also remove "Relocation" maybe? It's a detail but could be included in Benefits? It says relocation assistance is not a negotiable benefit. Could be included in Benefits? But it's a negative. Might be considered metadata; we could drop it as minor metadata. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So relocation could be minor metadata; we can drop or include in a short p. Probably drop. We need to preserve all substantive information. So we need to keep details about responsibilities, qualifications, skills, benefits, pay, schedule. We must not invent or summarize away detail. Must not include placeholder text like "commensurate with experience". We have specific pay range, so include. We must not create sections with filler. So each heading must have content. We need to output only HTML fragment, no /, no markdown fences. Structure: maybe:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

• ...
...

Skills

• ...
...

Benefits

• ...
...

Pay

...

Schedule

...

We need to ensure we don't repeat content. Let's extract substantive content. About the role: paragraphs: "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, Space & Security (BDS) team is seeking a Mechanical Engineer (Mid-Level) located in Heath (Columbus), OH. Boeing Defense and Space Systems is growing in the area of aircraft, missile, weapons and autonomous system Guidance Navigation and Control (GN&C) system design, development, integration, and test. The InterContinental Ballistic Missile (ICBM) Minuteman III Guidance Subsystem Support Contract (GuSSC) Sustainment Engineering program is looking for motivated, talented engineers to join the Boeing team in this exciting business area. The selected Mechanical Engineer (Mid-Level) product responsibilities will include engineering execution of sustainment efforts supported by the local Heath (Columbus), OH team. Support will include execution of the Program Work Structure (PWS), including schematic design, electrical component obsolescence studies, and circuit modeling in support of the local Heath team." We can keep that as a paragraph. Responsibilities: The list after "Position Responsibilities:" includes many bullet-like sentences each starting with a skill area. We need to capture each as list item. List items: - Analytical Skills (Technical): Skill and ability to: collect, organize, synthesize, and analyze data; summarize findings; develop conclusions and recommendations from appropriate data sources. - Design Concepts and Techniques: Advanced knowledge of design concepts and techniques (e.g., concurrent engineering, Design for Manufacture/Assembly [DFM/A]). - Engineering Processes: Knowledge of responsibilities and tasks performed by various engineering departments/disciplines (e.g., design, test, software, technology, avionics). Knowledge of the interaction between departments/disciplines and how their products/processes affect one another and impact non-engineering processes (e.g., Operations, Logistics, Business). - Engineering Knowledge/Comprehension: Knowledge of various engineering disciplines such as electrical, mechanical, and systems. The ability to communicate with technical personnel from multiple skill areas and functions to evaluate technical information and issues impacting design, production, and support of products, services, or other deliverables. - Systems Thinking: Ability to understand the big picture and the inter-relationships of all positions and activities in the system, including the impact of changes in one area on another area. This includes the ability to see and understand the inter-relationships between components of systems and plans, anticipate future events, and apply the principles of systems thinking to accelerate performance. - Mechanical Component/System Engineering: Knowledge of mechanical component and system design, analysis, and integration. Familiarization with the tools required for design, analysis, evaluation, and integration (i.e. computer aided design systems, mathematical modeling software, tolerance analysis software). - Liaison Engineering Judgment: Exercise engineering judgment in developing appropriate decisions considering decision criteria, implications, and possible consequences, to ensure product design integrity. Demonstrate understanding of the applicable scientific and engineering knowledge and involve others in obtaining information for the liaison engineering decision-making process. We can keep each as

. Requirements: Basic Qualifications (Required Skills and Experience): - Bachelor of Science degree in Engineering (with a focus on Mechanical, Civil, Aerospace Aeronautical or Material Sciences) - 5+ years of related work experience and a bachelor’s degree or an equivalent combination of related work experience and technical education We can list those. Qualifications: Preferred Qualifications (Desired Skills and Experience): - Experience working with USAF or other DoD agencies - Experience with creation, change, and design of electromechanical assemblies - Experience with analog and digital design, manufacturing, and sustainment - Experience engineering for obsolescence and sustainment We list those. Skills: Could be the analytical skills etc but we already used those under Responsibilities. Actually the responsibilities list includes skill areas. Might be better to put those under Skills, and responsibilities under Responsibilities as more specific duties (like execution of sustainment efforts, schematic design, etc). However the posting lumps skill areas under Position Responsibilities. But we can still treat them as responsibilities. The instruction: Use

• for any list of duties/requirements/benefits. So we can put the skill bullets under Responsibilities as duties. That's fine. Thus we may not need a separate Skills section. But we could still have Skills if we have other skill content not captured. However we already used all skill bullets. If we create Skills section, we would duplicate. Better to not create Skills section if no distinct content. But the instruction: "Prefer a few substantive sections over many thin ones." So we can omit Skills if content already covered. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Check Benefits: content includes: - The Boeing 401(k) helps you save for your future, with contributions from Boeing that can help you grow your retirement savings. Our best-in-class retirement benefit features: Best in class 401(k) plan: we'll match your contributions dollar for dollar, up to 10% of eligible pay with immediate 100% vesting. - Student Loan Match: The Boeing 401(k) Student Loan Match allows eligible enrolled U.S. employees to have their qualified student loan debt payments counted, along with any match-eligible contributions they make, for purposes of determining the Company Match to employees' Boeing 401(k) accounts. - 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. We can list these as bullet items. Pay: content: - Pay is based upon candidate experience and qualifications, as well as market and business considerations. - Summary pay range: $103,700-$140,300 We can put as paragraph or list. Schedule: - Shift This position is for 1st shift We can put as paragraph. Now ensure we don't include boilerplate like "Export Control Requirements", "Conflict of Interest", "Drug Free Workplace", "Visa Sponsorship", "Equal Opportunity Employer", "Relocation assistance is not a negotiable benefit", "Security Clearance", etc. Those should be removed. Also remove duplicated lines like "Education Bachelor's Degree or Equivalent Required" etc. Now produce HTML. Make sure to use proper escaping? Not needed. 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. The Boeing Defense, Space & Security (BDS) team is seeking a Mechanical Engineer (Mid-Level) located in Heath (Columbus), OH. Boeing Defense and Space Systems is growing in the area of aircraft, missile, weapons and autonomous system Guidance Navigation and Control (GN&C) system design, development, integration, and test. The InterContinental Ballistic Missile (ICBM) Minuteman III Guidance Subsystem Support Contract (GuSSC) Sustainment Engineering program is looking for motivated, talented engineers to join the Boeing team in this exciting business area. The selected Mechanical Engineer (Mid-Level) product responsibilities will include engineering execution of sustainment efforts supported by the local Heath (Columbus), OH team. Support will include execution of the Program Work Structure (PWS), including schematic design, electrical component obsolescence studies, and circuit modeling in support of the local Heath team.

  Responsibilities

  • Analytical Skills (Technical): Skill and ability to: collect, organize, synthesize, and analyze data; summarize findings; develop conclusions and recommendations from appropriate data sources.
  • Design Concepts and Techniques: Advanced knowledge of design concepts and techniques (e.g., concurrent engineering, Design for Manufacture/Assembly [DFM/A]).
  • Engineering Processes: Knowledge of responsibilities and tasks performed by various engineering departments/disciplines (e.g., design, test, software, technology, avionics). Knowledge of the interaction between departments/disciplines and how their products/processes affect one another and impact non-engineering processes (e.g