Senior Software Engineer - RDPL - Onsite (San Diego)

We need to output HTML fragment with sections: About the role? The posting includes description: At RTX... etc. We'll need to parse. We must not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We include only sections with real specific content. We need to preserve all substantive info, no boilerplate. We need to remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. We must not include Pay/Schedule/Benefits unless posting actually states them. Pay: The posting includes "The salary range for this role is 95,500 USD - 181,700 USD." So we have Pay section. Schedule: It says "This role will be 100% on-site in San Diego, California." That's schedule? Could be schedule info (onsite). Could treat as Schedule section? The instruction: Use

for Schedule if posting actually states them. It does state onsite requirement. So we can include Schedule. Benefits: The posting includes "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." Also mentions incentive compensation programs. So we have Benefits. We also have "Relocation Offered Based On Eligibility." That could be part of Benefits or separate? Probably part of Benefits. We need sections: About the role (intro description), Responsibilities (What You Will Do), Requirements (maybe security clearance and citizenship?), Qualifications (Qualifications You Must Have and Qualifications We Prefer), Skills (maybe not separate; but we could combine qualifications and skills? The instruction says use headings for those categories if content exists. We have qualifications (must have and prefer). Could also have Skills section for things like proficiency in C++, etc. But we already have qualifications covering that. Might be redundant. Better to follow typical: Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. About the role maybe as introductory paragraph before sections? The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include About the role as a section with the introductory paragraphs about RTX and team. We must not repeat job title as heading. So we will not include a heading for the job title. We need to preserve all substantive information, not invent or summarize away detail. So we need to include details like: "Active and transferable U.S. government issued security clearance is required prior to start date." etc. We need to remove duplicated lines: there are repeated statements about citizenship and clearance. We should keep only one instance? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. Remove duplicated lines. So we need to deduplicate identical sentences. We'll need to identify duplicates. Let's extract content. First, header lines: Date Posted, Country, Location, Position Role Type: Onsite, U.S. Citizen... etc. Those are metadata; we may fold minor metadata into a short

or drop it. The instruction: do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short

or drop it. So we could include a short paragraph with metadata like location, posting date, role type, citizenship requirement? But citizenship requirement is substantive; we should keep it in Requirements. We need to keep substantive info: security clearance requirements, citizenship, etc. Now body: "At RTX, the world's largest aerospace and defense company, 185,000 great minds are united by purpose and inspired to make a difference solving the world’s most complex problems. With our three market leading businesses, world-class operations and investments in research and development, we offer capabilities and opportunity no one else can. Together, we push the boundaries of known science and find new ways to connect and protect our world. Raytheon brings the strength of more than 100 years of experience and renowned engineering expertise to meet the needs of today’s mission and stay ahead of tomorrow’s threat. We deliver solutions that help our nation and allies defend freedoms and deter aggression, creating a safer, more secure world. Join us and help shape the future of aerospace and defense. Raytheon’s Radar Digital Product Line (RDPL) team in San Diego, California, is growing! We are seeking motivated Senior Software Engineers to join our team. In this role, you will have the opportunity to work on cutting-edge technology solutions, grow your expertise in the radar domain, and engage in potential travel to support radar site operations. This position offers a dynamic and collaborative environment where you can make a meaningful impact. This role will be 100% on-site in San Diego, California." That's About the role. Next: "What You Will Do" bullet list: - Collaborate with Scrum teams to design, develop, and troubleshoot tactical radar software in a DevSecOps environment. - Design, code, and maintain robust C++ software for real-time applications, ensuring high reliability. - Execute software integration testing (SWIT) and root-cause analysis using Jenkins and Linux-based tools. - Develop scripts (Python, Bash, or Perl) to automate testing, log analysis, and system integration tasks. - Contribute to architectural decisions and technical reviews, actively growing your skills in system-level design. That's Responsibilities. Next: "Qualifications You Must Have": - Typically requires a degree in Science, Technology, Engineering or Mathematics (STEM) and a minimum 5 years of prior relevant experience. - Proficiency in C++ and Object-Oriented Design (OOD). - Experience with Linux development environments and DevSecOps tools (Jenkins, Jira, Git). - Strong problem-solving skills and a self-motivated approach to debugging and fixing complex software issues. - The ability to obtain and maintain a U.S. government issued Secret security clearance is required. - U.S. citizenship is required, as only U.S. citizens are eligible for a security clearance. Next: "Qualifications We Prefer": - Experience with MATLAB for data analysis and visualization of test runs. - Familiarity with Container technologies (Docker, Kubernetes, Podman) for build and test environments. - Hands-on experience with scripting languages (Python, Perl, Bash) for automation and testing. - Strong grasp of data structures, algorithms, and system software design. - Exposure to radar systems, Digital Signal Processing (DSP), or real-time embedded software. - Desire to stay updated with new technologies and grow into technical leadership or software architecture roles. Next: "What We Offer Our values drive our actions, behaviors, and performance with a vision for a safer, more connected world. At RTX we value: Safety, Trust, Respect, Accountability, Collaboration, and Innovation." Then: "Relocation Offered Based On Eligibility. Learn More & Apply Now!" (we drop application instructions). Then: "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." That's role type definition; could be considered Schedule? But we already have schedule info. Then: "Clearance Information: This position requires a security clearance. DCSA Consolidated Adjudication Services (DCSA CAS), an agency of the Department of Defense, handles and adjudicates the security clearance process. More information about Security Clearances can be found on the US Department of State government website here: https://www.state.gov/m/ds/clearances/c10978.htm" That's more clearance info; but we already have clearance requirement. Might be considered boilerplate? It's still substantive about clearance process. Might keep as part of Requirements? But we already have clearance requirement. Could include a short note about clearance process. However instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. This clearance info is not exactly boilerplate but could be considered supplemental. Might keep as part of Requirements. Then: "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." That's maybe not needed. Then: "The salary range for this role is 95,500 USD - 181,700 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." Then EEO boilerplate etc. We need to remove EEO/equal-opportunity boilerplate. Thus we need to extract Benefits: includes list of benefits and relocation offered, incentive compensation. We need to avoid duplication: The benefits list appears twice? Actually only once. We need to ensure we don't include duplicated lines like citizenship requirement appears twice (in Requirements You Must Have and also earlier in metadata). We'll keep only one. Now construct HTML. We'll have:

About the role

...

Responsibilities

• ...
...

Requirements

• ...
...

Qualifications

Maybe split into Must Have and Preferred? Could have two subsections? But we only have h3 headings; we could include two

sections: Qualifications (Must Have) and Preferred Qualifications? But instruction says use headings for those categories if content exists. Could have Qualifications (Must Have) and Preferred Qualifications as separate sections? Might be okay. However we could combine into one Qualifications section with two lists: Must Have and Preferred. But that would mix headings inside? Not allowed because only h3 for section headings; we could use

to label inside. Simpler: have one Qualifications section with two

lists, each preceded by a

describing. But we need to avoid filler. We'll include both. Then Benefits:

Benefits

list of benefits

Relocation offered based on eligibility.

Eligible for annual short-term and/or long-term incentive compensation programs...

Pay:

Pay

The salary range for this role is 95,500 USD - 181,700 USD.

Schedule:

Schedule

This role is 100% on-site in San Diego, California.