Software Engineer 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. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions. Include a section only when posting has real, specific content for it. Avoid filler like "commensurate with experience". Pay/Schedule/Benefits only if posting actually states them. We need to parse the posting. Key info: - Date posted, country, location, role type: Onsite. U.S. Citizen, U.S. Person, or Immigration Status Requirements: The company will offer immigration sponsorship for this position, if needed. The company will not seek an export authorization for this role. Security Clearance Type: None/Not Required. Security Clearance Status: Not Required. - Then a paragraph: "Are you ready to explore the world of aerospace and defense? ..." - Then "What You Will Do" with description: ARINCDirect ... The Flight Planning team builds web and iOS software ... As a Software Engineering Intern, you will work with experienced engineers to develop and enhance full-stack applications and backend services supporting the ARINCDirect's Flight Planning experience. This is a hands-on opportunity to apply your academic knowledge to real-world software engineering challenges. - Then "What You Will Learn" bullet list: Develop full-stack application features using Python and JavaScript/TypeScript. Design, implement, and integrate APIs and backend services. Write unit and integration tests to ensure software quality and reliability. Create and enhance Grafana observability metrics to monitor application health and performance. Contribute to CI/CD pipelines and automated software delivery. Collaborate with engineers and cross-functional partners in an Agile development environment. - Then "Qualifications You Must Have": Must be pursuing Bachelor’s or Advanced degree in STEM actively enrolled through completion of internship/co-op session. Must have a minimum of 60 hours of credit by the start of the internship/co-op session. Experience with Python and JavaScript/TypeScript through coursework, projects, or prior experience. Experience with version control software such as Github or GitLab. Familiarity with SQL and relational databases. Experience may be obtained through on-the-job experience, research, coursework, or projects. - Then "Qualifications We Prefer": Strong problem-solving and communication skills. Ability to work effectively in a collaborative team environment. Experience developing full-stack or web applications. Experience building or consuming REST APIs. Experience with continuous integration tools such as Jenkins or GitLab CI/CD. Prior RTX internship, co-op, or work experience. - Then "What We Offer": Our values drive our actions... At RTX we value: 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 42,000 USD - 88,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... (EEO boilerplate). Privacy Policy and Terms: Click on this link to read the Policy and Terms. We need to remove EEO boilerplate, privacy policy, application instructions, duplicated lines, navigation, cookie, legal, etc. We need to keep substantive info: location, role type, immigration sponsorship, security clearance not required, maybe "U.S. Citizen, U.S. Person, or Immigration Status Requirements" is a requirement. Also "The company will offer immigration sponsorship for this position, if needed." and "The company will not seek an export authorization for this role." Also security clearance none. We also have "What You Will Do" paragraph. We have "What You Will Learn" list. We have "Qualifications You Must Have" list. We have "Qualifications We Prefer" list. We have "What We Offer" includes values, relocation eligibility, role type definition (Onsite), salary range, benefits list, incentive compensation, etc. We need to decide sections: About the role (maybe the introductory paragraph about RTX and opportunity). Responsibilities (What You Will Do). Requirements (Qualifications You Must Have). Qualifications (maybe Qualifications We Prefer could be under Skills? Or separate "Preferred Qualifications"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can map: - About the role: introductory paragraph about RTX and opportunity (the "Are you ready..." paragraph plus maybe the description of ARINCDirect? Actually "What You Will Do" includes description of role. But we could put the ARINCDirect description under About the role. Or we could treat "What You Will Do" as Responsibilities. The "What You Will Learn" could be under Skills or maybe under Qualifications? But we have separate Skills heading. We need to avoid filler. We need to include sections only if there is real content. Let's extract content: **About the role** (maybe combine the introductory motivational paragraph and description of ARINCDirect and Flight Planning team). The posting says: "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." Then after that: "What You Will Do ARINCDirect, part of the Connected Aviation Solutions unit of Collins Aerospace, provides planning, scheduling, and connectivity solutions that empower thousands of aircraft operations every day. The Flight Planning team builds web and iOS software that enables pilots to efficiently plan and manage flight operations. As a Software Engineering Intern, you will work with experienced engineers to develop and enhance full-stack applications and backend services supporting the ARINCDirect's Flight Planning experience. This is a hands-on opportunity to apply your academic knowledge to real-world software engineering challenges." We could treat the first paragraph as About the role, and the second as Responsibilities (What You Will Do). Or we could combine both into About the role. But we need Responsibilities section for duties. The "What You Will Do" is clearly responsibilities. Thus: - About the role: the motivational paragraph about RTX and opportunity. - Responsibilities: the paragraph describing ARINCDirect, Flight Planning team, and what the intern will do (develop full-stack apps, etc). Could be a paragraph. - Requirements: "Qualifications You Must Have" list. - Skills: maybe "Qualifications We Prefer" list (skills/preferred qualifications). Or we could treat "What You Will Learn" as Skills? But "What You Will Learn" is more about learning outcomes, not required skills. However we could put that under Skills as well. But we need to avoid duplication. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we have both Qualifications and Skills. Likely Qualifications = mandatory qualifications, Skills = preferred or desired skills. So we can put "Qualifications You Must Have" under Requirements (or Qualifications?). Actually they said Requirements heading for list of duties/requirements/benefits. Wait: "Use

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

    for prose." So Requirements heading could contain list of requirements (qualifications). But they also have Qualifications heading separate. Might be overlapping. But we need to follow instruction: Use headings as given. We can decide: - About the role: prose. - Responsibilities: prose (maybe list? but it's a paragraph). - Requirements: list of mandatory qualifications (Qualifications You Must Have). Use

    • . - Qualifications: maybe list of preferred qualifications (Qualifications We Prefer). Use
      • . - Skills: maybe list of what you will learn (skills you will gain). Use
        • . - Benefits: list of benefits from What We Offer (medical, dental, etc). Use
          • . - Pay: salary range. - Schedule: maybe mention Onsite role type? Or relocation eligibility? Not exactly schedule. The posting mentions Onsite role type, but schedule not given. Could we create Schedule section? Only if posting actually states schedule. It does not mention specific schedule (e.g., full-time, part-time, hours). It mentions Onsite role type, but not schedule. So we should not create Schedule section if no specific schedule info. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we can create Pay (salary range) and Benefits (list). Schedule: not stated, so omit. Also we need to include location and role type maybe in About the role or a separate meta paragraph? The instruction says do NOT put Job ID/requisition numbers as headings — fold minor metadata into a short

            or drop it. So we can include location, role type, date posted maybe in a short paragraph at top? But they said remove boilerplate, duplicated lines, application instructions. The location and role type are not boilerplate; they are substantive. We could include them in a short

            before sections. However the instruction says use

            for section headings (About the role, Responsibilities, etc). It doesn't forbid having a leading paragraph without heading. So we can output a

            with location, role type, date posted, immigration sponsorship, security clearance. Then sections. We must not repeat job title as heading (the page already shows it). So we don't add a heading for the job title. We must not invent or summarize away detail. Preserve ALL substantive information. So we need to keep all details: location, role type, immigration sponsorship, export authorization not sought, security clearance none, the motivational paragraph, ARINCDirect description, responsibilities, what you will learn, mandatory qualifications, preferred qualifications, values, relocation eligibility, Onsite definition, salary range, benefits list, incentive compensation note, US-based role, territory note, application window approx 40 days, EEO boilerplate removed, privacy policy removed. We need to be careful not to include