Internship – Raytheon Systems Security Engineer- 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. Key info: - Date posted, location, etc: we can drop metadata or put in short p. - Position Role Type: Onsite. - U.S. Citizen, U.S. Person, or Immigration Status Requirements: Active and transferable U.S. government issued security clearance required prior to start date. U.S. citizenship required, as only U.S. citizens eligible for a security clearance. Security Clearance Type: DoD Clearance: Secret. Security Clearance Status: Ability to obtain INTERIM U.S. government issued security clearance required prior to start date. - Intro: "Are you ready to explore the world of aerospace and defense? ..." That's about the role maybe. - What You Will Do: description. - What You Will Learn: description. - Qualifications You Must Have: bullet list? It says: Must be pursuing Bachelor’s or Advanced degree in STEM and actively enrolled through completion of internship/co-op session. Must have a minimum of 60 hours of credit by start of internship session. Experience may be obtained through on-the-job experience, research, coursework, or projects. - Qualifications We Prefer: Specific majors: Systems Engineering, Cybersecurity, or related STEM discipline; Quick learner and motivated; Experience with tools, such as MATLAB or Python, for data analysis and automation; Prior RTX internship, co-op, or work experience; Current/Active DoD security clearance or SSBI. - What We Offer: values list; Relocation Eligibility Learn More & Apply Now! (skip). Then description of benefits: 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 depending on level, not guaranteed. - Pay: The salary range for this role is 37,000 USD - 82,000 USD. - Schedule: Not explicitly mentioned besides Onsite. No schedule details like full-time, part-time, hours. So we should not create Schedule section unless posting actually states them. It does not. So omit Schedule. - Benefits: we have content. - Skills: maybe we can include under Qualifications or Skills? The instruction says use headings for Skills if there is content. We have "Experience with tools, such as MATLAB or Python, for data analysis and automation" which is a skill. Also "Quick learner and motivated" is a skill. Could create Skills section. But we also have Qualifications sections. We could combine qualifications and skills? The instruction: "Prefer a few substantive sections over many thin ones." So we might combine Qualifications and Skills into one Qualifications section, or separate if we have enough content. We have qualifications (must have) and preferred qualifications. Could put both under Qualifications heading. Skills could be part of Qualifications. But we also have a separate Skills heading possible if we want to list specific tools etc. However we have limited skill specifics. Might be better to have Qualifications (must have) and Preferred Qualifications (or Skills) as sub-sections? But we only allowed headings h3 for sections; we could have subheadings? Not specified. Probably just use h3 for main sections. Could have Qualifications and Skills separate if we have enough content. Let's see: Skills: Experience with tools such as MATLAB or Python for data analysis and automation. Also maybe "Quick learner and motivated". That's not a technical skill but a trait. Could still be skill. So we could have Skills section with those items. But we also have "Current/Active DoD security clearance or SSBI" under Qualifications We Prefer. That's a qualification/clearance. Thus we could have: - About the role (intro paragraph) - Responsibilities (What You Will Do) - What You Will Learn (maybe under Responsibilities or separate? Could be "Learning Opportunities" but not in list. The instruction only lists specific headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content to those headings. "What You Will Learn" could be part of Responsibilities or maybe under Qualifications? Not exactly. Could treat as part of Responsibilities (what you will do/learn). Or we could create a separate section like "Learning Opportunities" but not allowed. So we should incorporate into Responsibilities or maybe under Qualifications? Probably best to add to Responsibilities: description of tasks and learning. - Requirements: security clearance and citizenship etc. - Qualifications: Must have and Preferred. - Skills: maybe list MATLAB/Python, quick learner, etc. - Benefits: list. - Pay: salary range. We should not include Schedule. We need to preserve all substantive information; do not invent or summarize away detail. So we need to keep specifics like "Must be pursuing Bachelor’s or Advanced degree in STEM and actively enrolled through the completion of the internship/co-op session." etc. We need to remove boilerplate: EEO, legal, privacy policy, application instructions, duplicated lines, cookie/navigation etc. Also remove "Relocation Eligibility Learn More & Apply Now!" etc. Also remove "Please consider the following role type definition as you apply for this role." etc. Also remove "RTX anticipates the application window closing approximately 40 days..." etc. Also remove "This role is a U.S.-based role..." etc. Also remove "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." That's benefits; we keep that. Also "Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement." That's also benefits detail; keep. Also "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." That's also benefits/compensation; maybe keep under Benefits or Pay? It's about incentive compensation; could be part of Benefits. We'll keep. Now we need to output only HTML fragment, no /, no markdown fences. We'll produce something like:

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

Systems Security Engineering creates holistic security solutions leveraging Cyber Security, Software Assurance and Supply Chain Risk Management to support Program Protection Implementation on Sensors, Ground Radars, and Platform systems. Join our highly visible team and perform technically challenging assignments, which will directly contribute to protecting our nation and our Warfighters. This is an onsite position at Raytheon. You will support, contribute, and collaborate in a team environment, receiving inputs from the program or team experts, and work on projects, determining and developing approaches and solutions. Collaborate across many engineering disciplines to execute program milestones. You will gain technical experience, mentorship opportunities, and exposure to established cybersecurity engineers within Mission Systems that will help advance your career. You will become knowledgeable in a variety of cybersecurity tools and policies in the ever-evolving cybersecurity engineering and program protection field.

Requirements

U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. Active and transferable U.S. government issued security clearance is required prior to start date. Ability to obtain INTERIM U.S. government issued security clearance is required prior to start date. Security Clearance Type: DoD Clearance: Secret.

Qualifications

• Must be pursuing Bachelor’s or Advanced degree in STEM (Science, Technology, Engineering, or Mathematics) and 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 session.
• Experience may be obtained through on-the-job experience, research, coursework, or projects.

Preferred Qualifications

• Specific majors: Systems Engineering, Cybersecurity, or related STEM discipline
• Quick learner and motivated
• Experience with tools, such as MATLAB or Python, for data analysis and automation
• Prior RTX internship, co-op, or work experience
• Current/Active DoD security clearance or SSBI

But we only allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We used "Preferred Qualifications" which is not in list. Could combine under Qualifications heading with sub-sections? But we can't add extra headings not in list. However we could include both must-have and preferred under Qualifications heading, maybe separate with

or

but not separate heading. 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, not exclusive? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." Likely they expect only those headings. So we should not create "Preferred Qualifications" heading. Instead we can include both must-have and preferred under Qualifications heading, maybe separate with

headings like Must Have and Preferred but that's not a heading. That's okay. Similarly for Skills: we could have Skills heading with list of skills: MATLAB/Python, quick learner, etc. Thus final sections: - About the role - Responsibilities - Requirements - Qualifications (must have) - Skills (preferred qualifications/skills) - Benefits - Pay We need to ensure we don't create empty sections. Now craft content. About the role: as earlier. Responsibilities: combine What You Will Do and What You Will Learn. Requirements: security clearance and citizenship. Qualifications: must have bullets. Skills: preferred qualifications/skills: list specific majors, quick learner, experience with MATLAB/Python, prior RTX internship, current/active DoD clearance or SSBI. Benefits: list values and benefits. Pay: salary range. We should also include location maybe in a short p under About the role? The instruction says do NOT repeat the job title as a heading and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include location and date posted in a short p after About the role? But we already have About the role paragraph; we could add a small p with metadata before or after. However we must preserve ALL substantive information; location is substantive. So we need to include location somewhere. Could add a p after About the role: "Location: US-MA-WOBURN-WB2 ~ 225 Presidential Way ~ GODDARD BLDG, Woburn, MA, USA." Also include date posted