Leadership Development Program – Engineering, Software Discipline (Starts June 2027)

We need to output only HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading only if there is real specific content. Must not repeat job title. Must not include Job ID etc. Must preserve all substantive info. Remove boilerplate like EEO, legal, application instructions, etc. Also remove duplicated lines. Must not create sections with filler like "commensurate with experience". We need to extract content. Let's parse the posting: - Date posted, country, location, role type: Onsite, U.S. Citizen requirement. Security clearance none. Then description: RTX corporation description. - "What You Will Do": description of program. - "Key Responsibilities": bullet list. - "Qualifications You Must Have": bullet list. - "Qualifications We Prefer": bullet list. - "What We Offer": description of benefits. - Then details about salary range: "The salary range for this role is 59,000 USD - 139,000 USD." - Also mention 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 "annual short-term and/or long-term incentive compensation programs". - Also mention "flexible work schedules" etc. - Also mention "Learn More & Apply Now!" etc but that's application instruction; we should remove. - Also mention rotation locations etc: that's schedule? Might be schedule info: rotation assignments, relocation, etc. Could be considered Schedule? The instruction: include Schedule section only if posting actually states them. There's mention of rotation assignments (three 8-month rotational assignments), relocation, travel/live anywhere, onsite/hybrid/remote. That's more about work arrangement, maybe schedule? But we have a Schedule heading; we could put info about rotation length, relocation, location flexibility. However we need to decide if that qualifies as schedule. The posting does not give explicit schedule like "full-time", "part-time", "shift". It gives rotation assignments and location flexibility. Might be better to put under About the role or Responsibilities? The instruction: Use headings only when posting has real, specific content for it. So we need to see if there is specific content for Schedule. The posting mentions "Rotation locations will vary & may be onsite, hybrid, or remote." and "Candidates will learn more about role type and current site status throughout the recruiting process." Also "For onsite and hybrid roles, commuting to and from the assigned site is the employee’s personal responsibility." Also definitions of onsite/hybrid/remote. That's about work arrangement, not schedule per se. Could be considered Schedule? Might be borderline. Safer to not create Schedule section if not explicit schedule like hours. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." So we need explicit mention of schedule (e.g., full-time, part-time, shift). Not present. So omit Schedule. Pay: we have salary range explicit, so include Pay section. Benefits: we have benefits list, include Benefits section. Skills: maybe we can combine Qualifications and Skills? The instruction: Use headings for Skills if there is real specific content. The posting includes "Qualifications You Must Have" and "Qualifications We Prefer". Those are qualifications, not skills. Could treat them as Qualifications section. Skills could be separate if there is explicit skills list. There is mention of "Experience utilizing object-oriented programming languages, software development tools, or testing frameworks (such as Python, C++, Java, or C#)." That's skill. Also "Experience with static code analysis, secure coding practices, or safety-critical software engineering methodologies." etc. Those could be skills. But we already have qualifications covering similar. To avoid thin sections, we could merge qualifications and skills into Qualifications section. But the instruction says prefer a few substantive sections over many thin ones. So we can have About the role, Responsibilities, Qualifications, Benefits, Pay. Possibly also Requirements (citizenship, relocation). There's a "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" and "U.S. citizenship is required". Also "Willing and able to operationally relocate to various RTX geographic locations across the United States for three distinct 8-month program assignments." That's a requirement. Could be under Requirements heading. Thus sections: About the role (description of company and program), Responsibilities (key responsibilities), Requirements (citizenship, relocation, degree, etc?), Qualifications (education, experience, preferred qualifications), Benefits, Pay. We must not repeat job title. Must not include metadata like date posted, location? Could be folded into short p or dropped. The instruction: "do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it." So we can include location etc in a short p maybe under About the role? But we should preserve all substantive information. Location is substantive? It's location of job. Could be included in About the role as a short paragraph. However the instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." So we need to keep location info. We can include a short p after the heading maybe:

Location: Arlington, VA (Wilson Blvd, Rosslyn HQ).

But we need to avoid boilerplate like "Date Posted: 2026-09-14". That's metadata; we can drop or fold into short p. Probably drop date posted as not substantive? It's maybe not needed for job description. But location is substantive. We'll include location in a p. Also "Position Role Type: Onsite". That's substantive; we can include in About the role. Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" we can put under Requirements. Also "Security Clearance Type: None/Not Required" maybe not needed; it's not substantive? Could be included under Requirements as "No security clearance required." But it's minor; we could drop. We must not include EEO boilerplate etc. Now craft HTML. Structure:

About the role

Location: Arlington, VA (Wilson Blvd, Rosslyn HQ). Position is onsite. RTX Corporation is an Aerospace and Defense company that provides advanced systems and services for commercial, military and government customers worldwide. It comprises three industry-leading businesses – Collins Aerospace Systems, Pratt & Whitney, and Raytheon. Its 185,000 employees enable the company to operate at the edge of known science as they imagine and deliver solutions that push the boundaries in quantum physics, electric propulsion, directed energy, hypersonics, avionics and cybersecurity. The company, formed in 2020 through the combination of Raytheon Company and the United Technologies Corporation aerospace businesses, is headquartered in Arlington, VA. Discover an extraordinary opportunity to accelerate your software engineering career and develop into a future technical leader at RTX. Our two-year rotational Engineering Leadership Development Program (ELDP) – Software Discipline provides challenging, high-visibility assignments across the enterprise, allowing you to build a powerful global network. You will receive high-caliber training, professional mentoring, and frontline, hands-on software experience directly within our cutting-edge development environments. This fast-paced path expands your business acumen, sharpens your technical expertise, and prepares you to make a lasting impact on our global software organization. Actively recruiting for the next cohort and program that begins June 2027.

Responsibilities

• Complete three 8-month rotational assignments across various U.S. locations, adapting quickly to new technology centers, business units, and software engineering teams.
• Execute core engineering milestones within one or more specialized program tracks, including software applications/systems design and development, hands-on coding, testing and implementation, and technical documentation.
• Stretch your professional and technical capabilities by taking ownership of frontline, hands-on development deliverables and software codebases.
• Collaborate cross-functionally with hardware, systems, and program management teams to define software requirements and optimize system deployment.
• Present technical reviews, code demonstrations, and strategic engineering data clearly and effectively to stakeholders and leadership teams.

Requirements

• U.S. citizenship is required (only U.S. citizens authorized to access information under this program/contract).
• Willing and able to operationally relocate to various RTX geographic locations across the United States for three distinct 8‑month program assignments.
• Bachelor’s or Master’s degree in Computer Engineering, Software Engineering, Electrical Engineering, Computer Science, or a related STEM major; degree must be obtained by start date.
• Relevant internship, co‑op, or professional work experience with one or more of the following areas: software engineering, embedded development, source code development, testing and implementation protocols, or technical documentation.
• Experience utilizing object‑oriented programming languages, software development tools, or testing frameworks (such as Python, C++, Java, or C#).
• Completed coursework or experience with one or more of the following: core computing fundamentals, including embedded, operating, or real‑time systems, data structures and algorithms OR digital logic, computer architecture, or communication systems.

Qualifications

Preferred qualifications:

• Active U.S. government secret security clearance.
• Self‑motivated and team‑oriented work style with the agility to thrive in a fast‑paced, dynamic technology and software development environment.
• Familiarity with Agile or Scrum software development methods and project management workflows.
• Experience or academic exposure to Model‑Based Systems Engineering (MBSE) frameworks and tools, such as Cameo or SysML.
• Experience with static code analysis, secure coding practices, or safety‑critical software engineering methodologies.
• Functional exposure to Continuous Integration/Continuous Deployment (CI/CD) pipelines, test automation tools, or automated software verification frameworks.
• Prior experience as a software or engineering intern or co‑op within an RTX business unit (Collins Aerospace, Pratt & Whitney, or Raytheon).

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 (including paternal) leave.
• Paid time off and holidays.
• Educational assistance.
• Child/adult backup care.
• Achievement awards.
• Leadership, functional and business acumen training.
• Upon program completion, LDP graduates receive continued mentorship.
• Annual short‑term and/or long‑term incentive compensation programs (subject to performance and business unit/collective‑bargaining factors).

Pay

The salary range for this role is $59,000 USD – $139,000 USD.

We should ensure no markdown, just HTML. Also ensure we didn't include any boilerplate like EEO, legal, application instructions, etc. We removed those. Check for any repeated content: We included location and onsite in About the role. Good. Check for any filler like "commensurate with experience": none. Check for any heading with empty content: all have content. Check for any mention of schedule: we omitted Schedule section. Check for any mention of "Pay": we have Pay section with salary range