Systems Security Engineer II - P2 (Onsite - McKinney, TX)

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 must not repeat job title. Must not include Job ID etc. Must preserve all substantive info, not invent or summarize away detail. Remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions. Also remove lines like "Please ensure the role type defined below is appropriate for your needs before applying to this role." etc. Also remove "This position is classified as: Onsite..." maybe that's schedule? Actually schedule is Onsite. The posting says "Position Role Type: Onsite". So we can include a Schedule section with "Onsite". Also Pay: salary range given. Benefits: they list benefits. So include Benefits section. About the role: there is description about Raytheon and role. Responsibilities: bullet list of "What You Will Do". Qualifications: "Qualifications You Must Have" and "Qualifications We Prefer". Skills: maybe not explicit separate; but we could combine under Qualifications? The instruction: use headings for sections like Skills if present. There's no explicit Skills list, but we could infer from qualifications? Better not to create Skills unless there is explicit list. The posting includes "Experience in System Security Engineering, computer technology reverse engineering, cybersecurity or embedded security" etc. That's qualifications. So we can have Qualifications section covering both must have and preferred. Could also split into Requirements (maybe security clearance, citizenship) and Qualifications (education/experience). But we need to follow instruction: use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Ensure we don't create sections with filler. We must preserve all substantive information. Let's extract: About the role: description of Raytheon, SSE team, role purpose. Paragraphs: "At RTX, the world's largest aerospace and defense company..." etc. Also "Raytheon is seeking a Systems Security Engineer II - P2 to join our elite Systems Security Engineering (SSE) team..." etc. Also "This is an onsite position at Raytheon in McKinney, TX." Responsibilities: bullet list under "What You Will Do": - Support implementation of SSE solutions into RTX products - Help define SSE requirements, solutions, trades, costs, implementation, system impacts and effectiveness - Plan and guide SSE implementations in customer systems - Attack threat modeling / Critical Program Information Assessments - Developing top-level system requirements, and flowing down requirements and implementation concepts to subsystem - Understanding and compliance with DoD technology release and export licensing policies Also "What You Will Learn": Embedded Cybersecurity Engineering, Embedded Anti-Tamper Engineering. Could be considered responsibilities or maybe a separate section like "Learning Opportunities". Not in headings list; we could incorporate into Responsibilities or maybe a separate section like "What You Will Learn" but not allowed headings. Probably include under Responsibilities as additional bullet? But it's not a duty; it's learning. Could treat as part of Responsibilities? Might be okay to add a bullet list under Responsibilities for what you will learn. However instruction: preserve ALL substantive information; do not invent or summarize away detail. So we need to include that info somewhere. Could add a separate section like "Learning Opportunities" but not in allowed headings; but we could still use

for any section heading? The instruction says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but 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 fit learning into Responsibilities or maybe Qualifications? Could add a bullet under Responsibilities: "Learn Embedded Cybersecurity Engineering and Embedded Anti-Tamper Engineering". That preserves info. Requirements: security clearance, US citizenship, active transferable clearance, etc. Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements: Active and transferable U.S. government issued security clearance is required prior to start date. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance Security Clearance Type: DoD Clearance: Secret Security Clearance Status: Active and existing security clearance required on day 1". Also maybe "Position Role Type: Onsite" is schedule not requirement. Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" is a heading but we should not repeat as heading; we fold into Requirements paragraph. Qualifications: "Typically requires a Bachelor’s Degree in Science, Technology, Engineering or Mathematics (STEM) and 2 years of prior relevant experienceThe ability to obtain and maintain a U.S. government issued security clearance is required. U.S. citizenship is required, as only U.S. citizens are eligible for a security clearanceExperience in System Security Engineering, computer technology reverse engineering, cybersecurity or embedded security". Also "Qualifications We Prefer" list. We need to avoid duplication: security clearance and citizenship appear both in Requirements and Qualifications; we should keep them but not duplicate? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. Duplication is okay if it's in original; but we could combine to avoid redundancy but might lose some nuance. Safer to keep both sections as they appear, but ensure we don't duplicate headings incorrectly. Could have Requirements covering clearance/citizenship, and Qualifications covering education/experience and preferred knowledge. Benefits: list: "Relocation Eligible – Relocation assistance is available", then 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 depending on level and collective bargaining. Also note that specific benefits depend on business unit and collective bargaining. Also mention that hired applicants may be eligible for benefits etc. We'll include that. Pay: salary range: 68,900 USD - 131,100 USD. Also note that it's a good faith estimate etc. We'll include that. Schedule: Onsite. Now produce HTML fragment. Structure:

About the role

... paragraphs ...

Responsibilities

• ...
...

Requirements

... (clearance, citizenship, active transferable secret clearance required day 1) ...

Qualifications

... (Bachelor's degree STEM + 2 years experience, ability to obtain/maintain clearance, US citizenship, experience in SSE, reverse engineering, cybersecurity, embedded security) ...

Preferred qualifications:

• Knowledge in generating systems requirements, design and architecture artifacts, plans and/or policies
• Knowledge in Software, Firmware, & Microelectronics Engineering, Cryptography and FPGA design
• A Degree in Electrical Engineering, Systems Engineering, Mechanical Engineering, Engineering Mechanics, Computer Science or Engineering Science
• Broad understanding of technology and working knowledge of DODI-S-5230.28
• Candidate must exhibit ingenuity, creativity and resourcefulness
• Experience contributing in a team environment for the purpose of developing creative solutions to technical problems

Benefits

Relocation Eligible – Relocation assistance is available.

• 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

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 programs are not guaranteed and depend on individual, business unit, and/or company performance. Specific benefits are dependent upon the specific business unit as well as whether or not the position is covered by a collective-bargaining agreement.

Pay

The salary range for this role is 68,900 USD - 131,100 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.

Schedule

Onsite

We must ensure no boilerplate like EEO, privacy policy, etc. Also remove duplicated lines like "U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance" appears multiple times; we have it in Requirements and Qualifications (maybe duplicate). Could we keep only once? The instruction says preserve ALL substantive information; does that mean we must keep each occurrence? It says "Preserve ALL substantive information; do NOT invent or summarize away detail." If we remove a duplicate sentence, we are summarizing away detail (removing duplicate). Might be considered okay? Safer to keep both occurrences, but we could note that it's repeated. However we could keep it in both sections; it's not harmful. It's still substantive info (the fact that citizenship is required). Duplication doesn't lose info. So we can keep it in both sections. Check for any other substantive info: "Position Role Type: Onsite" we used in Schedule. "Date Posted: 2026-09-24" maybe not needed; it's metadata but could be considered minor metadata; instruction says do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. Date posted is minor metadata; we could drop it. Location: US-TX-MCKINNEY-513WC ~ 2501 W University Dr ~ WING C BLDG. That's location info; could be considered minor metadata but maybe we should include as part of About the role? Could add a sentence about location. The posting includes location; we should preserve. So add location in About the role paragraph. Also "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" we folded into Requirements. Also "Security Clearance Type: DoD Clearance: Secret" etc. Also "Security Clearance Status: Active and existing security clearance required on day 1". We'll include. Also "At RTX, the world's largest aerospace and defense company..." we included. Also "Raytheon brings the strength of more than 100 years of experience..." we included. Also "Join us and help shape the future of aerospace and defense." included. Also "This is an onsite position at Raytheon in McKinney, TX." included. Also "What You Will Learn" we turned into bullet under Responsibilities maybe as separate bullet: "Learn Embedded Cybersecurity Engineering and Embedded Anti-Tamper Engineering". We'll add that. Also "Please ensure the role type defined below is appropriate for your needs before applying to this role." is application instruction; remove. Also "This position is classified as: Onsite: Employees who are working in Onsite roles will work primarily onsite. This includes all production and maintenance employees,