Principal Systems Engineer - Electronic Protection, AN/TPY-2

We need to output only HTML fragment, no /, no markdown fences. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. We need to parse the posting. We need to 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 "Date Posted", "Country", "Location", "Position Role Type", etc? Those are minor metadata; we can fold into a short

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

or drop it." So we can include a short paragraph with location, date posted maybe. But we must not repeat job title as heading (the page already shows it). The job title is "Principal Radar Systems Engineer". We should not output that as heading. We need sections: About the role (maybe the introductory paragraph about RTX and the team). Responsibilities (the "What You Will Do" bullet list). Requirements (maybe "Qualifications You Must Have" and security clearance requirements). Qualifications (maybe "Qualifications We Prefer"). Skills (maybe list of skills from preferred qualifications). Benefits (the "What We Offer" includes values and relocation eligible, benefits list). Pay (salary range). Schedule (maybe not present; there is no explicit schedule info besides onsite; but schedule could be inferred as onsite? The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. Schedule: not explicitly stated; only mention "Onsite" role type. That might be considered schedule? It says "Onsite: Employees who are working in Onsite roles will work primarily onsite." That's more about role type, not schedule like full-time/part-time. Probably we should not create Schedule section because no explicit schedule like "Full-time", "Part-time", "Shift". So omit Schedule. We need to include Pay section because salary range is given. Benefits section: we have "What We Offer" includes values, relocation eligible, benefits list. So we can include Benefits. Now we need to decide what goes into each section. We must not repeat job title as heading. So we can start with maybe a

for metadata: location, date posted, role type (Onsite). Then sections. We must preserve all substantive info: do not invent or summarize away detail. So we need to keep details like bullet points exactly? We can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should not omit details, but we can reformat. Probably we can keep the same sentences but maybe adjust for HTML. We need to use

• for any list of duties/requirements/benefits, and

  for prose. Thus: - About the role: prose describing RTX, the team, the role context. Could be multiple paragraphs. - Responsibilities: list from "Key responsibilities include:" bullet points. - Requirements: includes security clearance requirements, citizenship, degree, 8 years experience, experience with EP, AWF, advanced signal processing. Also "Qualifications You Must Have" includes degree and 8 years experience, experience with EP, AWF and/or advanced signal processing concepts. Also "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". Also "Ability to obtain INTERIM U.S. government issued security clearance is required prior to start date". So combine. - Qualifications: maybe "Qualifications We Prefer" list. - Skills: Could extract from preferred qualifications: proficiency in MATLAB, C/C++, ADA, DOORS; AI/ML; BMC4I familiarity; signal processing techniques; system-level requirements development; communication skills; analytical abilities; advanced degree; active DoD security clearance (though that is also requirement). But we might treat skills as separate section listing technical skills. However we must not create thin sections; maybe combine Qualifications and Skills? But we have both sections possible. The instruction: "Prefer a few substantive sections over many thin ones." So we might combine Qualifications and Skills into one section? But we have headings list: we can choose to include Qualifications and maybe not Skills if it's thin. However the posting has a lot of preferred qualifications that could be considered skills. We could make a Skills section listing technical skills (MATLAB, C/C++, etc.) and maybe soft skills. But we need to see if that would be thin. It has many items; could be substantive. Better to have sections: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay. Possibly also Skills if we think it's substantive. But we need to avoid duplication: Requirements already includes degree, experience, clearance. Qualifications We Prefer includes many items; we could treat that as Qualifications section. Skills could be omitted. Let's decide: Sections: About the role, Responsibilities, Requirements (must-have), Qualifications (preferred), Benefits, Pay. Now we need to ensure we don't include filler like "commensurate with experience", "not specified", etc. Not present. Now we need to strip boilerplate: EEO statements, Privacy Policy, etc. Also remove "Learn More & Apply Now!" and application instructions. Also remove "Relocation Eligible – Relocation assistance available" maybe keep as part of Benefits. Also remove "The salary range provided is a good faith estimate..." maybe keep as part of Pay but it's prose. Now produce HTML. We'll start with a

  for metadata: maybe "Posted: 2026-09-16 | Location: Woburn, MA (Onsite) | Role Type: Onsite". But we should not repeat job title. That's fine. Then

  About the role

  with paragraphs. We need to preserve the descriptive text about RTX, the team, the role. Let's extract: "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. The Systems Engineering and Test Capabilities (SE&TC) Surface Radars & Sensors Center is seeking a Principal Radar Systems Engineer to join our Electronic Protection and Arbitrary Waveform Development team within the Long Range Radars Department. This position is located onsite in Woburn, MA. The Long Range Radars Department provides subject matter expertise in concept development, architectural design, requirements generation and flow-down, modeling and simulation, systems analysis, integration, as well as the test and evaluation of world-class Missile Defense & Sensor Systems. These achievements are driven by our people, processes, technology, and performance. In this role, you will play a crucial part in supporting the AN/TPY-2 missile defense radar program, one of the world’s most advanced and reliable X-band missile defense sensors. The AN/TPY-2 radar system delivers high-resolution detection, tracking, and discrimination of ballistic missile threats, boasting an impeccable performance record across all classes of ballistic missiles." That's a lot; we can keep as prose, maybe split into paragraphs. Now Responsibilities: bullet list from "Key responsibilities include:": - Defining and prototyping new algorithms to enhance system performance. - Analyzing radar system performance data to ensure compliance with requirements. - Identifying performance gaps and proposing innovative solutions. - Presenting technical plans, designs, and performance analyses to peers, internal leadership, and external customers. - Providing subject matter expertise to agile software development teams to enable proper implementation of requirements. Now Requirements: combine security clearance, citizenship, degree, 8 years experience, experience with EP, AWF, advanced signal processing. From "Qualifications You Must Have": Typically requires a degree in STEM and a minimum of 8 years of prior relevant experience. Experience with Electronic Protection (EP), Arbitrary Waveform (AWF) and/or advanced signal processing concepts. Also security clearance: "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". Also "Ability to obtain INTERIM U.S. government issued security clearance is required prior to start date". Also "Security Clearance Type: DoD Clearance: Secret". Also "Security Clearance Status: Ability to obtain INTERIM U.S. government issued security clearance is required prior to start date". So we can include that. Now Qualifications (preferred): list from "Qualifications We Prefer". We'll bullet each. - Minimum of 8+ years of experience in radar engineering or related technical disciplines. - Expertise in Electronic Protection and Arbitrary Waveform concepts and employment techniques. - Proficiency in developing and coding system models, algorithms, test vectors, and analysis tools to analyze radar requirements and performance. - Experience utilizing Artificial Intelligence (AI), Machine Learning (ML), and signal processing techniques in database and algorithm development. - Familiarity with Battle Management Command, Control, Communications, Computers, and Intelligence (BMC4I) systems. - Practical knowledge of signal processing techniques and radar system concepts, including detection, discrimination, tracking, and signal processing algorithms. - Proficiency with tools and programming languages such as MATLAB, C/C++, ADA, or DOORS. - Proven experience in system-level requirements development, documentation, and maintenance, or design and development of system-level software architecture. - Strong communication, technical writing, presentation, and interpersonal skills. - Demonstrated ability to interface with customers and lead technical solutions to complex challenges. - Strong analytical, technical, and problem-solving abilities. - Advanced degree (Master’s or PhD) in Engineering, Mathematics, Physics, Business, or related disciplines. - Active DoD Security Clearance. Now Benefits: from "What We Offer". Include values, relocation eligible, benefits list. Paragraph: "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 Eligible – Relocation assistance 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, and holidays. Also mention: "Hired applicants may be eligible for benefits, including but not limited to, ..." plus annual short-term and/or long-term incentive compensation programs depending on level, not guaranteed. We can include that as prose. Now Pay: salary range: "The salary range for this role is 107,500 USD - 204,500 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, ..." Actually benefits already covered. For Pay we can just include salary range and note that it's a good faith estimate. Now we must not include duplicated lines. Ensure we don't repeat the same sentences. Now produce HTML. We'll start with a

  for metadata: maybe "Posted: 2026-09-16 | Location: Woburn, MA (Onsite)".