Mechanical Engineering Co-op (Winter/Spring 2027)

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We must not repeat job title. Must preserve all substantive info, remove boilerplate like EEO, navigation, cookie, legal, etc. Also remove duplicated lines, application instructions. Must not include Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range: "The salary range for this role is 37,000 USD - 82,000 USD." So we can include Pay section. Benefits: they list benefits: "Hired applicants may be eligible for benefits, including but not limited to, 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, and holidays." Also mention incentive compensation programs. So Benefits section can be included. Schedule: they mention "full-time, Monday-Friday co-op session, that will run January – July/August (including the spring semester; it is expected students will take a semester off from coursework to fully engage with this working mentorship opportunity)." So schedule info exists. So we can include Schedule section. We need sections: About the role (maybe intro paragraph), Responsibilities (What You Will Do), Requirements (U.S. Person etc), Qualifications (You Must Have, Qualifications We Prefer), Skills (maybe combine with qualifications? But we can have Skills section if there is specific skill content: CAD, ANSYS, Microsoft Office, cross-functional teams). Could put under Qualifications or Skills. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can create those sections if content exists. We must not include placeholder text like "commensurate with experience". Not relevant. We must not include duplicated lines. Ensure we preserve all substantive info. We need to output only HTML fragment, no or . Use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to decide what goes where. About the role: Could be the introductory paragraph: "Are you ready to explore the world of aerospace and defense? Do you want to learn from and collaborate with some of the greatest minds in the industry? At RTX, our internships, co-ops and full-time careers provide an exceptional foundation to work on complex problems, advance your skills and create a safer, more connected world. Discover opportunities to make a difference at RTX." Also maybe mention "Mechanical Engineering Co-op at Collins Aerospace". That is part of responsibilities? Could be about role. We'll put that in About the role. Responsibilities: The "What You Will Do" section: list of duties. We'll convert to

  • . Requirements: U.S. Person requirement details. Also maybe "Position Role Type: Onsite" and "Security Clearance Type: None/Not Required". Those are metadata but not boilerplate; we can include under Requirements or maybe a separate meta but we can fold into Requirements as short p. The 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 p for Onsite and clearance. Qualifications: Must have and Preferred. We'll list as

    • maybe separate subheadings? But we only have h3 for section headings; inside we can have paragraphs and lists. Could have two lists: "Must Have" and "Preferred". Could wrap each in

      with bold? But we can just list items with indication. Probably better to have two

      with preceding

      stating "Must Have:" and "Preferred:". Skills: Could be extracted from qualifications: CAD, ANSYS, Microsoft Office, cross-functional teams. But we already have them in qualifications; maybe we can omit Skills section to avoid duplication. However instruction: Prefer a few substantive sections over many thin ones. So we could combine qualifications and skills into one Qualifications section. But they gave example headings including Skills. We could still include Skills if we have specific skill content not covered elsewhere. But we already have CAD, ANSYS, Microsoft Office, cross-functional teams under qualifications. Might be redundant. Safer to not add Skills section if it would be thin. We'll omit Skills. Benefits: list of benefits. Pay: salary range. Schedule: description of schedule. We must not include boilerplate like EEO, privacy policy, etc. Remove duplicated lines. Let's extract content. Original text: Date Posted: 2026-09-15 Country: United States of America Location: US-IA-CEDAR RAPIDS-131 ~ 5450 C Ave NE ~ BLDG 131 Position Role Type: Onsite U.S. Citizen, U.S. Person, or Immigration Status Requirements: This job requires a U.S. Person. A U.S. Person is a lawful permanent resident as defined in 8 U.S.C. 1101(a)(20) or who is a protected individual as defined by 8 U.S.C. 1324b(a)(3). U.S. citizens, U.S. nationals, U.S. permanent residents, or individuals granted refugee or asylee status in the U.S. are considered U.S. persons. For a complete definition of “U.S. Person” go here: https://www.ecfr.gov/current/title-22/chapter-I/subchapter-M/part-120/subpart-C/section-120.62 Security Clearance Type: None/Not Required Security Clearance Status: Not Required Are you ready to explore the world of aerospace and defense? Do you want to learn from and collaborate with some of the greatest minds in the industry? At RTX, our internships, co-ops and full-time careers provide an exceptional foundation to work on complex problems, advance your skills and create a safer, more connected world. Discover opportunities to make a difference at RTX. What You Will Do Immerse yourself in a full-time, Monday-Friday co-op session, that will run January – July/August (including the spring semester; it is expected students will take a semester off from coursework to fully engage with this working mentorship opportunity). As a Mechanical Engineering Co-op at Collins Aerospace, you will be provided with the opportunity to broaden your background with a practical approach to engineering. The primary goal is to merge your theoretical knowledge gained in school with practical engineering applications. Our team is responsible for mechanical design support and mechanical development of dozens of unique display panels for Commercial and Military Avionics. Our team designs products that support the full avionics industry. Assist Mechanical Engineers in the design, development, support, and documentation associated with optical stacks and electronic packaging. This position offers the opportunity to expand the candidate's knowledge and skills of all phases of mechanical hardware design, including requirements capture, design, layout, test/verification, integration, and factory transition. Specific types of engineering-related activities include CAD design and test, component analysis and troubleshooting of thermal performance. This position not only supports design engineers, but also plays a key role in supporting factory, field, and customer related issues. Qualifications You Must Have Must be pursuing a Bachelor’s or Advanced degree in Mechanical Engineering and actively enrolled through the completion of the internship/co-op session. Experience using computer aided design (CAD) software such as SolidWorks, AutoCAD, Siemens NX, AutoDesk and/or Creo Experience may be obtained through on-the-job experience, research, coursework, or projects. Qualifications We Prefer Experience with Microsoft Office (Excel, Word, and/or PowerPoint)Experience with ANSYSExperience working on cross-functional teamsA minimum of 60 hours of credit by the start of the internship / co-op sessionPrior RTX internship, co-op, or work experience What We Offer Our values drive our actions, behaviors, and performance with a vision for a safer, more connected world. At RTX we value: Safety, Trust, Respect, Accountability, Collaboration, and Innovation. Relocation Eligibility Learn More & Apply Now! Please consider the following role type definition as you apply for this role. Onsite: Employees who are working in Onsite roles will work primarily onsite. This includes all production and maintenance employees, as they are essential to the development of our products. As part of our commitment to maintaining a secure hiring process, candidates may be asked to attend select steps of the interview process in-person at one of our office locations, regardless of whether the role is designated as on-site, hybrid or remote. The salary range for this role is 37,000 USD - 82,000 USD. The salary range provided is a good faith estimate representative of all experience levels. RTX considers several factors when extending an offer, including but not limited to, the role, function and associated responsibilities, a candidate’s work experience, location, education/training, and key skills. Hired applicants may be eligible for benefits, including but not limited to, 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, and holidays. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement. Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs depending on the level of the position and whether or not it is covered by a collective-bargaining agreement. Payments under these annual programs are not guaranteed and are dependent upon a variety of factors including, but not limited to, individual performance, business unit performance, and/or the company’s performance. This role is a U.S.-based role. If the successful candidate resides in a U.S. territory, the appropriate pay structure and benefits will apply. RTX anticipates the application window closing approximately 40 days from the date the notice was posted. However, factors such as candidate flow and business necessity may require RTX to shorten or extend the application window. RTX is an Equal Opportunity Employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, sex, sexual orientation, gender identity, national origin, age, disability or veteran status, or any other applicable state or federal protected class. RTX provides affirmative action in employment for qualified Individuals with a Disability and Protected Veterans in compliance with Section 503 of the Rehabilitation Act and the Vietnam Era Veterans’ Readjustment Assistance Act. Privacy Policy and Terms: Click on this link to read the Policy and Terms We need to remove boilerplate: EEO, Privacy Policy, etc. Also remove "Learn More & Apply Now!" and application instructions. Also remove "Relocation Eligibility". Also remove "Date Posted:", "Country:", "Location:", maybe we can keep location as minor metadata? The instruction: fold minor metadata into a short

      or drop it. So we could include a short p with location and role type. But we already have Onsite info. We could include a short p: "Location: Cedar Rapids, IA. Position type: Onsite." But we need to avoid duplication. We'll include a short p after About the role maybe. We must preserve all substantive information: that includes the description of role, responsibilities, qualifications, benefits, pay, schedule, US Person requirement, security clearance none, values, etc. We must not include duplicated lines: e.g., "Experience using computer aided design (CAD) software such as SolidWorks, AutoCAD, Siemens NX, AutoDesk and/or Creo Experience may be obtained through on-the-job experience, research, coursework, or projects." There's a missing space before "Experience". We'll keep as is but maybe fix spacing? We should preserve exactly? Probably okay to keep as is but ensure readability. We need to output HTML fragment. Let's craft: