Software Engineering Intern (Summer 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 with real content. No job title heading. No Job ID etc. Remove boilerplate. We need to parse the posting. Key info: - Date posted, location, etc: we can include as short paragraph maybe under a heading? 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 paragraph with date posted, location, role type, citizenship requirement, etc. - About the role: The paragraph starting "Are you ready to explore..." etc. That's description. - Responsibilities: "What You Will Do:" bullet list? It's prose describing tasks. Could be considered responsibilities. We'll make a

Responsibilities

with

containing that description. Could also include bullet list? Not explicit list. - What You Will Learn: Could be under Skills or maybe "What You Will Learn" as a section? Not in allowed headings list but we could treat as Skills? The allowed headings include Skills. So we can put that under Skills. - Qualifications: "Qualifications You Must Have:" and "Qualifications We Prefer". So we can have Requirements? Actually Qualifications heading allowed. We'll put Qualifications. - Benefits: "What We Offer" includes values and benefits list. Also mention relocation eligibility? Not specific. We'll include Benefits section with list of benefits. - Pay: Salary range given: "The salary range for this role is 37,000 USD - 82,000 USD." So we include Pay section. - Schedule: Not given explicitly. No schedule info. So we omit Schedule. - Also mention citizenship requirement: could be under Requirements? There's a heading Requirements allowed. We could include citizenship requirement there. Or we could include under Qualifications. But we have both Requirements and Qualifications allowed. We'll put citizenship under Requirements. - Also mention "U.S. Citizen, U.S. Person, or Immigration Status Requirements: U.S. citizenship is required..." So that is a requirement. - Also mention "Security Clearance Type: None/Not Required" etc. Could be minor metadata; we could drop or include in a short p. - Also mention "Relocation Eligibility Learn More & Apply Now!" That's boilerplate; we drop. - Also mention "Please consider the following role type definition..." etc. That's boilerplate; drop. - Also mention "As part of our commitment..." etc. Drop. - Also mention "The salary range provided is a good faith estimate..." etc. That's part of Pay; we can keep. - Also mention "Hired applicants may be eligible for benefits..." etc. That's Benefits. - Also mention "Hired applicants may be eligible for annual short-term and/or long-term incentive compensation programs..." That's also Benefits? Could be part of Benefits but it's incentive compensation. We'll include in Benefits. - Also mention "This role is a U.S.-based role..." etc. Could be minor metadata; maybe include in a short p. - Also mention "RTX anticipates the application window closing approximately 40 days..." etc. That's metadata; we can drop or include short p. - Also mention EEO etc. Drop. We need to preserve ALL substantive information; do not invent or summarize away detail. So we must keep the details like examples of projects, mentor, etc. We need to use

• for any list of duties/requirements/benefits. So we need to identify lists. What are lists? The 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, and holidays. That's a list. Also maybe the values list: Trust, Respect, Accountability, Collaboration, and Innovation. That's also a list but could be under Benefits? Actually it's under "What We Offer Our values drive our actions...". Could be a list under Benefits or maybe a separate section? Not in allowed headings; we could include under Benefits as a list. Also the qualifications we have: Must be pursuing Bachelor’s or Advanced degree... Must have a minimum of 60 hours of credit... Experience may be obtained through... That's not a list but could be
  if we break into items. But it's prose; we could keep as

  . The instruction: Use

  • for any list of duties/requirements/benefits. So if we have a list, we must use ul. For non-list prose, use p. Thus we need to decide what constitutes a list. - Benefits: definitely a list. - Values: could be a list. - Maybe "What You Will Do" includes multiple sentences but not a list. - "What You Will Learn": two items: Development of airborne embedded software; Development of operational concepts and use cases. That's a list of two items. Could be a list. - Responsibilities: maybe we can break into bullet points: focus on one or two projects, mentor, participate in team meetings, etc. But the text is prose; we could still make a list if we identify discrete items. Safer to keep as

    unless clearly list. - Qualifications You Must Have: multiple items: Must be pursuing degree..., Must have minimum 60 hours..., Experience may be obtained through... Could be list. - Qualifications We Prefer: Prior RTX internship... Could be list. Thus we can create ul for those. We must not repeat job title as heading. We must not include navigation etc. We'll output HTML fragment. Structure:

    Date Posted: 2026-09-10 | Location: US-MN-BURNSVILLE-WEST ~ 14300 Judicial Rd ~ WEST BLDG | Role Type: Onsite | Citizenship: U.S. citizenship required.

    Then sections:

    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

    Your position as software engineering intern will focus on one or two projects that you will be able to complete through the summer. We will provide a mentor to coach and oversee your progress. Our projects vary in focus but are always challenging projects that produce an output our engineers use regularly. Recent examples include software download tools, pressure voltage simulators for HIL testing, and automation tools for our test stations. During our internship, you sit directly with our software engineers and participate in team meetings, discussions, and project reviews; you participate as one of the team. Our goal is to expose you to the everyday life of our software engineers and evaluate how you would fit in the team full time after graduation. We are looking for an individual that is internally motivated to provide high quality work, can communicate effectively and drives their project to completion. Understanding embedded software (i.e., bare metal software development), full V-model development, and reading hardware schematics are skills regularly used in our team.

    What You Will Learn

    • Development of airborne embedded software
    • Development of operational concepts and use cases

    Qualifications

    Must Have

    • Must be pursuing Bachelor’s or Advanced degree in Science, Technology, Engineering or Mathematics (STEM) actively enrolled through the completion of the internship/co‑op session.
    • Must have a minimum of 60 hours of credit by the start of the internship / co‑op session.
    • Experience may be obtained through on‑the‑job experience, research, coursework, or projects.

    Preferred

    • Prior RTX internship, co‑op, or work experience.
    But we only allowed headings

    for section headings. Using

    might be considered extra heading not allowed? The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It didn't forbid other headings, but to be safe we could avoid

    and just have a single Qualifications section with paragraphs or lists. We could embed the "Must Have" and "Preferred" as

    with bold? But we cannot use markdown. We could use inside

    . That's okay. Thus:

    Qualifications

    Must have:

    • Must be pursuing Bachelor’s or Advanced degree in Science, Technology, Engineering or Mathematics (STEM) actively enrolled through the completion of the internship/co‑op session.
    • Must have a minimum of 60 hours of credit by the start of the internship / co‑op session.
    • Experience may be obtained through on‑the‑job experience, research, coursework, or projects.

    Preferred:

    • Prior RTX internship, co‑op, or work experience.
    That's fine. Now Benefits:

    Benefits

    At RTX we value: Trust, Respect, Accountability, Collaboration, and Innovation.

    • 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

    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.

    Pay:

    Pay

    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.

    We could also add a short paragraph about relocation eligibility? Not needed. We should also include the citizenship requirement maybe under Requirements section. Let's add a Requirements section.

    Requirements

    U.S. citizenship is required, as only U.S. citizens are authorized to access certain necessary systems. Security clearance is not required for this position.

    We could also mention that it's a U.S.-based role; but that's minor. We need to ensure we don't repeat info. We have citizenship in Requirements; we also have it in the initial metadata p. Could drop metadata p and put that info in Requirements. The instruction: fold minor metadata into a short

    or drop it. So we could have a short p at top with date posted, location, role type. That's okay. Thus final HTML:

    Date Posted: 2026-09-10