Secure System Engineering Intern (Summer 2027)

We need to output HTML fragment with sections: About the role? The posting includes description: "Are you ready to explore..." etc. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections with real specific content. We must not repeat job title as heading. No Job ID etc. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove "Learn More & Apply Now!" etc. Also remove "Please consider the following role type definition..." etc. Also remove "RTX is an Equal Opportunity Employer..." etc. Also remove "Privacy Policy and Terms". Also remove "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" maybe part of Requirements? Actually they have "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." That's a requirement. Also "Must be a U.S. Person/Permanent Resident" appears later? Actually they say "Must be a U.S. Person/Permanent Resident". That's also requirement. We need to preserve all substantive info: responsibilities list, what you will learn, qualifications must have, qualifications we prefer, what we offer (values, relocation eligible, benefits list). Pay: salary range given: "The salary range for this role is 37,000 USD - 82,000 USD." So we need Pay section with that. Schedule: they mention "This is an onsite position." Also "Employees who are working in Onsite roles will work primarily onsite." So schedule: Onsite. Could be a Schedule section with "Onsite". Also maybe "Relocation Eligible" could be part of Benefits? But we can include in Benefits or separate? The instruction: include a section ONLY when posting has real, specific content for it. Relocation Eligible is specific content; could be part of Benefits or maybe a separate section? Not listed among headings; we have Benefits, Pay, Schedule. Relocation could be part of Benefits. We'll include in Benefits. We must not include filler like "commensurate with experience". Not present. We need to avoid duplication. Let's extract sections: 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 "What You Will Do:" is responsibilities. So About the role could be that intro. Responsibilities: The bullet list under "What You Will Do:" plus maybe "Assist with developing and executing fuzzing and penetration tests..." etc. Also "Develop threat models..." etc. Also "Participate in code reviews..." etc. Also "Conduct vulnerability assessments..." etc. Also "Develop and improve tools and scripts..." etc. What You Will Learn: Could be considered as part of Responsibilities or maybe a separate section like "What You Will Learn". Not in headings list; we could treat as part of Responsibilities or maybe as a separate section like "Learning Opportunities". But headings limited to given list; we could put under Responsibilities or maybe under Qualifications? Better to include as part of Responsibilities? But we have a separate "What You Will Learn" content; we could incorporate into Responsibilities or maybe into a section like "What You Will Learn" not in allowed headings, but we could omit? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect us to use those headings only. So we need to map content to those headings. Thus: - About the role: introductory paragraph. - Responsibilities: list of duties (What You Will Do). - Requirements: maybe "U.S. citizenship is required" and "Must be pursuing a Bachelor’s or Advanced degree..." etc? Actually those are qualifications. Requirements could be citizenship and enrollment? But we have Qualifications section for must have and preferred. Could treat Requirements as citizenship and enrollment? But we also have Qualifications Must Have and Qualifications We Prefer. Could combine into Qualifications section with two subsections? But we need to follow headings: Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could assign: - Requirements: U.S. citizenship required, Must be pursuing a Bachelor’s or Advanced degree and actively enrolled, Minimum 60 credit hours, etc. Actually those are qualifications must have. But we can put them under Requirements. - Qualifications: maybe the "Qualifications We Prefer" list. - Skills: maybe the specific skills like Python proficiency, Linux, network protocols, etc. Could be from Qualifications Must Have. But we need to avoid duplication. Let's think: The posting has "Qualifications You Must Have:" list and "Qualifications We Prefer:" list. Also earlier they mention "Solid understanding of fundamental cybersecurity principles. High proficiency in Python programming. Familiarity with Linux operating systems. Basic knowledge of network protocols and secure architectures." That's part of Must Have. Thus we could map: - Requirements: Citizenship and enrollment (U.S. citizenship required, Must be pursuing a Bachelor’s or Advanced degree and actively enrolled, Minimum 60 credit hours). Also maybe "Must be a U.S. Person/Permanent Resident" (though that seems redundant). We'll include. - Qualifications: The "Qualifications We Prefer:" list. - Skills: The specific technical skills from Must Have: Solid understanding of fundamental cybersecurity principles, High proficiency in Python programming, Familiarity with Linux operating systems, Basic knowledge of network protocols and secure architectures. But we might also include "Strong problem-solving and analytical skills" etc under Skills? That is in Qualifications We Prefer. Might be better to put under Qualifications. We need to ensure we preserve all substantive info. Let's list all substantive info bits: Intro paragraph (About the role). What You Will Do (Responsibilities): - Assist with developing and executing fuzzing and penetration tests to evaluate attack surface robustness. - Develop threat models and data flow diagrams to ensure data is properly isolated in transit and at rest. - Implement mandatory access controls (MAC) through the development of SELinux policies. - Participate in code reviews to identify weaknesses in the implementation of security functions. - Conduct vulnerability assessments on proposed and in-service systems. - Develop and improve tools and scripts that enhance the overall efficacy of the Embedded Product Cybersecurity team. What You Will Learn (maybe could be part of Responsibilities or a separate "Learning" but we can incorporate into Responsibilities as bullet list? Might be better to add a separate section like "What You Will Learn" but not in allowed headings. Could we treat as part of Responsibilities? It's about learning outcomes, not duties. Could be placed under "Qualifications" maybe? But better to add a section "What You Will Learn" as a heading? The instruction says use h3 for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect those headings only. However, we could still add a heading like "What You Will Learn" as h3; it's not prohibited but might be considered not following the guideline. Safer to stick to given headings. We could incorporate What You Will Learn into Responsibilities as additional bullet points (though they are learning outcomes). Or we could add a separate section "What You Will Learn" but risk being marked incorrect. I'd rather follow the instruction: use those headings. So we need to fit What You Will Learn somewhere. Could be under "Qualifications" maybe as "What you will learn" is not a qualification but could be under "About the role"? Might be okay to add as a subsection under About the role? But we need to preserve all info; we can include it as a paragraph under About the role after the intro. Thus About the role will contain the intro paragraph plus the "What You Will Learn" bullet list. Now Requirements: Citizenship, enrollment, credit hours, maybe also "Must be a U.S. Person/Permanent Resident". Also maybe "U.S. citizenship is required, as only U.S. citizens are authorized to access information under this program/contract." Also "Must be a U.S. Person/Permanent Resident". We'll include. Qualifications: The "Qualifications We Prefer:" list. Skills: The specific technical skills from Must Have: Solid understanding of fundamental cybersecurity principles, High proficiency in Python programming, Familiarity with Linux operating systems, Basic knowledge of network protocols and secure architectures. Benefits: The list: "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." Also "Relocation Eligible". Also 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 maybe "annual short-term and/or long-term incentive compensation programs". Also "hired applicants may be eligible for benefits, including but not limited to, ...". We'll include all. Pay: Salary range: 37,000 USD - 82,000 USD. Schedule: Onsite. We must not include boilerplate like "Learn More & Apply Now!", "Please consider the following role type definition...", "Employees who are working in Onsite roles will work primarily onsite." Actually that is schedule info; we could keep that as part of Schedule. But we need to avoid duplication. We'll keep schedule: Onsite. We must not include EEO statement, Privacy Policy, etc. Now produce HTML fragment with h3 headings and appropriate ul/li for lists, p for prose. We need to ensure we don't repeat job title. Not include. 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.

What You Will Learn:

• The stages and practical application of the Collins Aerospace Secure Systems Development Lifecycle.
• The day-to-day operations and responsibilities of a cybersecurity engineer.
• Practical experience in security testing methodologies, emphasizing fuzzing techniques.
• Advanced skills in developing Python scripts and tools to automate and enhance cybersecurity workflows.
• The end-to-end process of developing threat models and securing data through strict isolation and access controls.

Responsibilities

• Assist with developing and executing fuzzing and penetration tests to evaluate attack surface robustness.
• Develop threat models and data flow diagrams to ensure data is properly isolated in transit and at rest.
• Implement mandatory access controls (MAC) through the development of SELinux policies.
• Participate in code reviews to identify weaknesses in the implementation of security functions.
• Conduct vulnerability assessments