Senior Radar Systems Engineer

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, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, application instructions). Must not include filler like "commensurate with experience". Must not create Pay/Schedule/Benefits unless posting actually states them. The posting includes salary range: "The salary range for this role is 86,800 USD - 165,200 USD." So we can include Pay section. Benefits: The posting includes "What We Offer: ... 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 content. So we can include Benefits section. Schedule: Not explicitly mentioned. There's no schedule info (like full-time, part-time). So we should not include Schedule heading. Skills: Could be derived from qualifications? The posting includes Qualifications You Must Have and Qualifications We Prefer. Those could be under Requirements or Qualifications. The instruction: Use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to decide which sections to include based on content. We have: - About the role: The paragraph after "At Raytheon, the foundation..." describing mission, role description. Could be About the role. - Responsibilities: The bullet list starting with "What You will Do:" includes multiple responsibilities. So we can have Responsibilities section. - Requirements: The "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" includes security clearance, citizenship, etc. Also "Qualifications You Must Have:" includes Bachelor's, 5 years experience, prior experience with radar systems, MATLAB/Python/C++. Those are requirements. Could be Requirements section. - Qualifications: Could be "Qualifications We Prefer:" as Qualifications section (preferred). Or we could combine Requirements and Qualifications? The instruction says we can have both Requirements and Qualifications sections. We'll include Requirements (must have) and Qualifications (preferred). Or we could treat "Qualifications You Must Have" as Requirements and "Qualifications We Prefer" as Qualifications. - Skills: Could be extracted from preferred qualifications like experience with design, development, analysis of radar system and software architectures, etc. But we already have Qualifications section for preferred. Might not need separate Skills unless we want to list skills like MATLAB, Python, C++, radar processing, etc. However we already have those in Requirements. To avoid duplication, we could keep Skills empty or not include. Better to not include Skills if no distinct skill list beyond what's already covered. The instruction: Prefer a few substantive sections over many thin ones. So we may omit Skills. - Benefits: we have content. - Pay: we have salary range. - Schedule: none. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. We need to use

for each section heading. Use

• for any list of duties/requirements/benefits. Use

  for prose. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, privacy policy, etc. Must remove duplicated lines. Also remove "Learn More & Apply Now!" etc. Also remove "Please consider the following role type definition as you apply for this role." etc. Also remove "As part of our commitment..." etc. Also remove "Hired applicants may be eligible for benefits..." we already captured benefits but need to keep the list. Also remove "Specific benefits are dependent..." maybe we can keep as part of benefits prose? It's substantive but maybe considered boilerplate? It's still about benefits. We'll keep it as part of benefits description. We must not include "The salary range provided is a good faith estimate..." maybe we can keep as part of Pay description. We must not include "RTX anticipates the application window closing..." etc. That's application instructions/boilerplate; remove. We must not include "RTX is an Equal Opportunity Employer..." etc. Remove. We must not include "Privacy Policy and Terms:" etc. Now craft HTML. Structure:

  About the role

  At Raytheon, the foundation of everything we do is rooted in our values and a higher calling – to help our nation and allies defend freedoms and deter aggression. We bring 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. Our team solves tough, meaningful problems that create a safer, more secure world. Are you passionate about turning innovative concepts into reality? Do you thrive in dynamic environments? Raytheon is seeking a talented and motivated Senior Radar Systems Engineer to join our team within the Systems Engineering and Test Capabilities (SETC) Discipline, supporting the LTAMDS and GhostEye Radars. This role offers a unique opportunity to work across the full lifecycle of the product, from concept to deployment. Every day will bring new challenges, requiring you to collaborate across disciplines to troubleshoot issues, perform data analysis, and implement solutions. Your contributions will directly impact the success of mission-critical defense systems, and you'll have a hands-on role in ensuring the entire system functions seamlessly. This position will be based out of our Tewksbury, MA with occasional travel to either Marlborough MA or Pelham NH sites possible.

  Responsibilities

  • You will be responsible for the development of concepts of operations for radar systems
  • You will be responsible for radar processing algorithm development
  • You will be responsible for radar software requirements development
  • You will be responsible for statistical and numerical analysis of radar performance data
  • Analysis tool development in support of problem identification and resolution
  • You will collaborate with Systems and Software Engineers to develop and implement solutions
  • You will present findings and solutions to Leadership and/or Customers

  Requirements

  • U.S. citizenship is required (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 (Secret - Current, active and existing security clearance required on day 1)
  • Typically requires a Bachelor’s in Science, Technology, Engineering, or Mathematics (STEM) and 5 years of prior relevant experience
  • Prior Experience with radar systems
  • Experience with MATLAB/Python/C++

  Qualifications

  • Experience with design, development, and analysis of radar system and software architectures
  • Experience of radar search and track capabilities, including use of pulse doppler and single pulse waveforms
  • Experience with design of search beam patterns and waveforms, PRIs, etc
  • Experience with Blake sheet construction
  • Experience with firm track range determination in nominal and ducting atmospheric conditions
  • The ability to review and redline B5 requirements for existing search and track requirements to reflect the new design
  • Experience of EA and EP techniques
  • Experience with technical writing and oral presentations
  • Masters/PhD in a STEM field

  Benefits

  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 and Innovation. 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.

  Pay

  The salary range for this role is 86,800 USD - 165,200 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.

  We must ensure no extra sections like Schedule. Also ensure we didn't include any boilerplate like "Learn More & Apply Now!" etc. We removed that. Check for any duplicated lines: we have not repeated. Check for any placeholders like "commensurate with experience": none. Check for any mention of "EEO": removed. Check for any mention of "Privacy Policy": removed. Check for any mention of "application window": removed. Check for any mention of "Onsite" definition: we removed that as it's boilerplate. Check for any mention of "U.S. Citizen, U.S. Person, or Immigration Status Requirements:" we turned into bullet items. Check for any mention of "Security Clearance Type: Secret - Current Security Clearance Status: Active and existing security clearance required on day 1" we incorporated. Check for any mention of "Position Role Type: Onsite" we omitted. Check for any mention of "Date Posted: 2026-09-22 Country: United States of America Location: US-MA-TEWKSBURY-TB3 ~ 50 Apple Hill Dr ~ CONCORD BLDG, Tewksbury Tb3 300 Concord" we omitted as metadata. Check for any mention of "This role is a U.S.-based role..." we omitted as maybe not essential? It's somewhat relevant but could be considered boilerplate. The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. That line about US-based role maybe not boilerplate but could be considered part of job details. However it's not a section heading; we could include it in About the role or Requirements? It says "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." That's somewhat relevant to pay/benefits. Could be included in Pay or Benefits. But we already have Pay and Benefits sections; we could add a sentence. However the instruction says preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep that detail. Where to put? Could add a

  under Pay or Benefits. Probably under Pay as it's about pay structure. Let's add a sentence after salary range: "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." Similarly, the line about "RTX anticipates the application window closing approximately 40 days from the date the notice was posted..." is application instructions/boilerplate; remove. Now ensure we didn't miss any substantive info: The initial paragraph about location: "Location: US-MA-TEWKSBURY-TB3 ~ 50 Apple Hill Dr ~ CONCORD BLDG, Tewksbury Tb3 30