Sr. Manufacturing Engineer

We need to output HTML fragment with sections: About the role? The posting includes description: "At RTX, the world largest aerospace..." etc. That's about the company. Could be "About the role" or "About RTX". The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we need to decide which sections have content. We have: - About the role: maybe the introductory paragraph about RTX and the role? The posting includes "At RTX, the world largest aerospace..." and "Join us and help shape the future..." That's about the company and role. Could be "About the role". We'll include that as prose. - Responsibilities: bullet list under "What You Will Do:" includes list of responsibilities. We'll output

• each. - Requirements: includes "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." Also "Security Clearance Type: None/Not Required". Also "Position Role Type: Onsite". Also location etc. But we should not repeat job title. We can include a short

  for metadata: location, citizenship requirement, onsite, etc. However we need to decide if we put that under Requirements or maybe a separate "Requirements" section for citizenship and clearance. The instruction: Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have a Requirements section containing the citizenship requirement and maybe clearance. - Qualifications: "Qualifications You Must Have:" and "Qualifications We Prefer:" We'll combine into Qualifications section with two sublists? Could use

  for must-have and preferred? Might be okay to have two
  with headings? But we only allowed

  for section headings, not subheadings. Could embed plain text like "Must have:" then

  . That's fine. - Skills: Not explicitly listed separate; but preferences include skills like CAD, GD&T, etc. Could be under Qualifications or Skills. Since we have a Skills heading possible, we could extract skills from preferences: "Experience with a shop floor management system (i.e. SAP, PRISM, ERP, MRP, or similar manufacturing software)", "Proficiency with CAD solid modeling tools (preference for CREO/ProE) and hands-on mechanical aptitude", "Experience with automated tooling, machinery and programming and adjusting software parameters on production or process equipment", "Technical drawing interpretation, Geometric Dimensioning and Tolerancing (GD&T) and experience with technical writing", "Experience with project execution", "Organizational skills with attention to detail and the ability to manage multiple tasks and innovative mindset that drives continuous improvement, lean manufacturing and keeps pace with advances in technology". That's more skills. Could create a Skills section. - Benefits: The posting includes "What We Offer Our values drive our actions..." then list of benefits: medical, dental, vision, life insurance, short-term disability, long-term disability, 401(k) match, flexible spending accounts, flexible work schedules, employee assistance program, Employee Scholar Program, parental leave, paid time off, holidays. Also mention incentive compensation programs. So we can create Benefits section with that list. - Pay: The posting includes "The salary range for this role is 86,800 USD - 165,200 USD." So we can create Pay section with that. - Schedule: Not explicitly mentioned besides Onsite. Could infer schedule? Not given. So we should not create Schedule section unless stated. The posting does not give schedule details. So omit. We must not include boilerplate like EEO, privacy, etc. Also remove duplicated lines, navigation, cookie, legal, etc. Also remove "Please Note: This position is located at the Raytheon Diné Facility in Farmington, NM." That's location info; we can include in metadata paragraph. We must preserve all substantive information. So we need to include location, citizenship requirement, onsite, etc. Also include the note about Navajo Nation Preference in Employment Act. Also include that the job is posted as ONSITE and based at Raytheon’s Farmington, NM site. Also include that RTX anticipates application window closing approx 40 days from date posted. That's substantive? Might be considered metadata but we can include in a short paragraph maybe under About the role or a separate meta. But instruction: do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

  or drop it. So we can include a short

  for metadata like location, citizenship, onsite, application window, etc. We need to output only HTML fragment, no /, no markdown fences. Let's structure:

  About the role

  At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market-leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Raytheon brings the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. We deliver solutions that help our nation and allies defend freedoms and deter aggression, creating a safer, more secure world. Join us and help shape the future of aerospace and defense.

  Maybe also include note about Navajo Nation Preference? Could be part of About the role or a separate meta. I'll include in About the role paragraph after location? Might be better to have a separate short paragraph for location and preferences. But we must not create extra headings unless content. Could have a

  for metadata: location, citizenship requirement, onsite, Navajo Nation Preference, application window. Let's do:

  Location: Raytheon Diné Facility, Farmington, NM (US-NM-FARMINGTON-426S ~ 10059 Hwy 371 S ~ SOUTH BLDG). This position is onsite. U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract). RTX Diné Facility adheres to the Navajo Nation Preference in Employment Act in recruitment and hiring. The application window is expected to close approximately 40 days from the posting date.

  That covers metadata. Then Responsibilities:

  Responsibilities

  • Designing, controlling and improving the manufacturing process through collaboration with a multi-disciplined team
  • Improving cycle and lead times
  • Implementing manufacturing process control and performance monitoring
  • Creating and overseeing improvement projects
  • Translating engineering design requirements into manufacturing processes
  • Performing hardware defect analysis
  • Participating in corrective action investigations
  Then Requirements:

  Requirements

  U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract). No security clearance required.

  But we already mentioned citizenship in metadata; but we can still include in Requirements. Might be duplicate but okay. However we should avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is okay if it's in original. But we could keep it only once. Since we already included citizenship in metadata paragraph, we could omit from Requirements and just put "No security clearance required." But the requirement section should contain the citizenship requirement; maybe better to keep it there and remove from metadata to avoid duplication. Let's think: The metadata paragraph is for minor metadata like location, onsite, etc. Citizenship is a requirement, not minor metadata. So we should put citizenship in Requirements. So metadata paragraph will include location, onsite, Navajo Nation Preference, application window. Then Requirements will have citizenship and clearance. Thus: Metadata paragraph:

  Location: Raytheon Diné Facility, Farmington, NM (US-NM-FARMINGTON-426S ~ 10059 Hwy 371 S ~ SOUTH BLDG). This position is onsite. RTX Diné Facility adheres to the Navajo Nation Preference in Employment Act in recruitment and hiring. The application window is expected to close approximately 40 days from the posting date.

  Requirements:

  Requirements

  U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract. No security clearance is required for this role.

  Qualifications: We have must-have and preferred. We'll make a Qualifications section with two subheadings? Not allowed to use

  for subheadings? Could use or just plain text. We'll do:

  Qualifications

  Must have:

  • Bachelor’s Degree in Science, Technology, Engineering or Math (STEM) and minimum 5 years prior relevant experience
  • Experience with work instructions in a manufacturing environment

  Preferred:

  • Experience with a shop floor management system (i.e. SAP, PRISM, ERP, MRP, or similar manufacturing software)
  • Proficiency with CAD solid modeling tools (preference for CREO/ProE) and hands-on mechanical aptitude with the ability to work across disciplines
  • Experience with automated tooling, machinery and programming and adjusting software parameters on production or process equipment to fix problems or improve performance
  • Technical drawing interpretation, Geometric Dimensioning and Tolerancing (GD&T) and experience with technical writing
  • Experience with project execution
  • Organizational skills with attention to detail and the ability to manage multiple tasks and innovative mindset that drives continuous improvement, lean manufacturing and keeps pace with advances in technology

  Skills: Could be separate but we already covered skills in preferred. Could still create Skills section listing those skills. But to avoid duplication, we might combine qualifications and skills. The instruction says prefer a few substantive sections over many thin ones. So we could merge skills into Qualifications. So we won't create separate Skills section. Benefits:

  Benefits

  • Medical, dental, vision, life insurance
  • Short-term and long-term disability
  • 401(k) match
  • Flexible spending accounts
  • Flexible work schedules
  • Employee assistance program
  • Employee Scholar Program
  • Parental leave
  • Paid time off and holidays
  • Annual short-term and/or long-term incentive compensation programs (eligibility dependent on position level and collective-bargaining coverage)

  Pay:

  Pay

  The salary range for this role is $86,800 USD – $165,200 USD.

  We should not include Schedule. Now ensure we didn't include any boilerplate like EEO, privacy, etc. We removed those. Check for any repeated lines: We have location paragraph includes location details; we didn't repeat the location elsewhere. Good. Check for any "Please Note:" we incorporated location and onsite. Check for "We Are RTX" etc removed. Check for "Learn More & Apply Now!" removed. Check for "Please consider the following role type definition as you apply for this role." removed. Check for "As part of our commitment to maintaining a secure hiring process..." removed. Check for "Hired applicants may be eligible for benefits,