Systems Engineer - Summer/Fall Co-op 2027 - (Onsite)

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 need to parse the posting. Given content: - Date Posted, Country, Location, Position Role Type: Onsite, U.S. Citizen, etc. We need to fold minor metadata into a short

or drop it. Not headings. - "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." This is introductory prose. Could be "About the role" maybe. - "What You Will Do:" bullet list: Work with other systems, software, and hardware engineers to create avionics display solutions that are high quality, reliable and safe; Develop and execute system-level operational tests for Avionics Display Systems; Develop software tools to support display system integration, verification and validation. - "What You Will Learn:" bullet list: Implementation of multiple phases of the system development lifecycle including requirements capture, system design and modeling, integration, system verification and validation; Application of industry standards and processes, such as ARINC 661, ARINC 664, and ARP-4754. - "Qualifications You Must Have:" bullet list: Currently pursuing a bachelor’s or master’s degree in science, technology, engineering, or math (STEM) major and actively enrolled through the completion of the internship/co-op session. Cumulative GPA of 3.0 or above is required. - "Qualifications We Prefer:" bullet list: Experience with at least one programming or scripting language. - "What We Offer Our values drive our actions, behaviors, and performance with a vision for a safer, more connected world. At RTX we value: Trust, Respect, Accountability, Collaboration, and Innovation." This is values, maybe "Benefits"? But later there is a benefits paragraph: "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. - Salary range: "The salary range for this role is 37,000 USD - 82,000 USD." So we need a Pay section. - Schedule: Not explicitly given; maybe "Onsite" role type indicates schedule? Not explicit schedule like full-time, part-time. We can omit Schedule section if not present. - Benefits: we have details. - Skills: maybe "Experience with at least one programming or scripting language" is a skill; also maybe "Experience with ARINC standards"? But that's under What You Will Learn. Could put Skills section for preferred qualifications. We need to decide sections: About the role (intro), Responsibilities (What You Will Do), Requirements (Qualifications You Must Have), Qualifications (maybe Qualifications We Prefer?), Skills (maybe combine with Qualifications We Prefer?), Benefits, Pay. We must not repeat job title as heading. No Job ID. We must not include boilerplate like EEO, etc. We need to preserve all substantive information; do not invent or summarize away detail. We need to use

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

  for prose. We need to output only HTML fragment. Let's craft:

  About the role

  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.

  Responsibilities

  • Work with other systems, software, and hardware engineers to create avionics display solutions that are high quality, reliable and safe
  • Develop and execute system-level operational tests for Avionics Display Systems
  • Develop software tools to support display system integration, verification and validation

  Requirements

  • Currently pursuing a bachelor’s or master’s degree in science, technology, engineering, or math (STEM) major and actively enrolled through the completion of the internship/co-op session
  • Cumulative GPA of 3.0 or above is required

  Qualifications

  Experience with at least one programming or scripting language is preferred.

  Alternatively could be Skills section:

  Skills

  with that bullet. But we need to decide: The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have Qualifications and Skills separate. Qualifications could be the must-have; Skills could be preferred. But we already used Requirements for must-have. Could rename Requirements to Qualifications? But they gave both. Let's follow: Requirements for must-have, Qualifications for preferred? Or Qualifications for must-have and Skills for preferred. The example list includes both Qualifications and Skills. We'll assign: - Requirements: Must-have (degree, GPA) - Qualifications: Preferred (programming/scripting) - Skills: maybe none else; but we could put technical skills like ARINC standards? But those are under What You Will Learn, not a qualification. Could put under Skills? Might be stretching. Better: Use Qualifications for must-have, Skills for preferred programming language. But we already used Requirements for must-have. Let's see: The posting has "Qualifications You Must Have:" and "Qualifications We Prefer:" So we could map: - Qualifications (must-have) heading:

  Qualifications

  with list. - Skills (preferred) heading:

  Skills

  with list. But they also said "Requirements" as possible heading. We could use Requirements for must-have and Qualifications for preferred? But they'd be similar. Let's decide: Use Requirements for must-have (degree, GPA). Use Qualifications for preferred (programming/scripting). Use Skills maybe for nothing else; we could omit Skills if no specific content. But we need to avoid empty headings. So we can omit Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Now Benefits: need to list benefits as
  • . The paragraph includes many benefits. We'll extract list. Benefits list: 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 (annual short-term and/or long-term incentive compensation) but note not guaranteed. Could include as bullet. We'll include those as list items. Pay:

    The salary range for this role is 37,000 USD - 82,000 USD.

    We should also include location maybe as metadata in a short

    but not heading. Could include after About the role? But we already have About the role prose. Could add a

    with location and role type: "Location: Cedar Rapids, IA (Onsite)." But we need to preserve all substantive information; location is substantive. So we should include it somewhere. The instruction: "Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

    or drop it." Location is not minor? It's substantive. Could be included in a

    after About the role or as its own paragraph. We'll add a

    with location and role type. Thus after About the role, we can have a

    with location and role type: "Location: Cedar Rapids, IA (Onsite)." Also include that it's US-based. Now check for any other substantive info: "The company will offer immigration sponsorship for this position, if needed. The company will not seek an export authorization for this role." That's metadata about immigration sponsorship; could be folded into a short

    . Also "Security Clearance Type: None/Not Required" etc. Could be minor metadata; we could fold into a short

    as well. We need to preserve ALL substantive information; we should not drop it. So we need to include immigration sponsorship and security clearance info somewhere. Could be a

    under About the role or separate. Let's create a

    after About the role: "Location: Cedar Rapids, IA (Onsite). The company offers immigration sponsorship if needed and does not require an export authorization or security clearance for this role." Now ensure we didn't miss any other substantive info: "RTX anticipates the application window closing approximately 40 days from the date the notice was posted." That's metadata about application window; could be included in a short

    maybe under About the role or separate. We'll include in same paragraph or separate. We'll add: "Applications are expected to close approximately 40 days after posting, subject to change." Now also note "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." That's substantive; include. Now also note about benefits being dependent on business unit and collective bargaining; we already have benefits list but we could note that specifics may vary. We'll include a sentence after benefits list: "Specific benefits are dependent upon the specific business unit and whether the position is covered by a collective‑bargaining agreement." Also note about incentive compensation not guaranteed; we can include a sentence. Now ensure we don't include boilerplate like EEO, privacy policy, etc. We'll omit those. Now produce HTML. Let's craft:

    About the role

    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.

    Location: Cedar Rapids, IA (Onsite). The company offers immigration sponsorship if needed and does not require an export authorization or security clearance for this role. Applications are expected to close approximately 40 days after posting, subject to change. 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.

    Responsibilities

    • Work with other systems, software, and hardware engineers to create avionics display solutions that are high quality, reliable and safe
    • Develop and execute system-level operational tests for Avionics Display Systems
    • Develop software tools to support display system integration, verification and validation

    Requirements

    • Currently pursuing a bachelor’s or master’s degree in science, technology, engineering, or math (STEM) major and actively enrolled through the completion of the internship/co‑op session
    • Cumulative GPA of 3.0 or above is required

    Qualifications

    Experience with at least one programming or scripting language is preferred.

    Ben