Principal RF Module Design/Development Engineer
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones.
We need to decide which sections to include based on content.
Content includes:
- Date posted, location, etc. Might be minor metadata; we can put in a short
maybe.
- Position Role Type: Onsite
- 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 after day 1
- Raytheon values paragraph (foundation...)
- Job Summary: description of role.
- What You Will Do: bullet list of duties.
- Qualifications You Must Have: list.
- Qualifications We Prefer: list.
- What We Offer: values list, plus salary range, benefits description.
We need sections: maybe "About the role" (Raytheon values and mission), "Job Summary", "Responsibilities" (What You Will Do), "Requirements" (security clearance, citizenship), "Qualifications" (must have), "Preferred Qualifications" (maybe combine with Qualifications? but we can have separate sections: "Qualifications" and "Preferred Qualifications" or "Skills"? The instruction list includes Skills as possible heading. But we can just use "Qualifications" for must-have and "Preferred Qualifications" for preferred. However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map:
- About the role: Raytheon values paragraph.
- Responsibilities: What You Will Do (list).
- Requirements: security clearance and citizenship (maybe also location Onsite? but location is minor metadata; we can include in a short p).
- Qualifications: Must Have list.
- Skills: maybe Preferred Qualifications list (skills). Or we could put Preferred Qualifications under Skills.
- Benefits: What We Offer includes values and benefits list; also salary range (Pay). So we need Pay section for salary range, Benefits section for benefits list, maybe also include values under About the role? But values already in About the role; we could also include values in Benefits? The instruction says include a section only when posting has real specific content. The posting includes "What We Offer: Our values drive our actions..." then list of values, then salary range, then benefits list. So we can have:
- About the role: maybe the Raytheon mission paragraph (foundation...).
- Benefits: list of benefits (medical, dental, etc.) plus maybe values? But values are also in What We Offer. Could put values under About the role, and benefits under Benefits.
- Pay: salary range.
- Schedule: maybe not specified; they didn't give schedule details besides Onsite. Could we put Schedule? The posting says Position Role Type: Onsite. That's schedule type. Could be considered schedule. But they said never create Schedule section unless posting actually states them. It does state Onsite. So we could include Schedule with content "Onsite". However they said prefer a few substantive sections over many thin ones. A section with just "Onsite" might be thin. Could we fold Onsite into a short p under About the role or Requirements? Probably better to include a short p with metadata: Date posted, location, role type. But they said do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can have a short p at top: "Posted 2026-09-15 • Andover, MA • Onsite". That covers date, location, role type.
Thus we may not need a separate Schedule section.
Now we need to remove boilerplate: EEO, privacy policy, etc. Also remove duplicated lines.
We need to preserve all substantive information: include all duties, qualifications, preferred qualifications, benefits list, salary range.
We must not invent or summarize away detail.
We need to output only HTML fragment, no /, no markdown fences.
We'll produce something like:
Posted 2026-09-15 • Andover, MA • Onsite
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.
Job Summary
An exciting opportunity exists for an experienced Principal RF Module Design/Development Engineer to join our Module Development Section within the RF Microelectronics/Module Development & Foundry Services (RFMicro) Department. The RFMicro department designs, fabricates, and tests state-of-the-art Monolithic Microwave Integrated Circuits (MMICs) in our on-site foundry. These chips are designed into custom modules to support multiple programs and enhance the capabilities of next generation radar systems. The successful candidate will be responsible for designing power combining structures, capabilities and transitions for RF/microwave modules containing GaAs- and GaN-based MMIC products. This would be in active support of existing technologies in production as well as next-generation products in development. This position requires a strong academic background and experience in RF/Microwave Design, Development, Integration & Test.
Responsibilities
- Designing RF structures and transitions on multi-layer, multi-channel RF Modules and analog circuitry enabling both receive and transmit behavior.
- 3D electromagnetic simulations of power combining and other RF structures.
- Troubleshooting RF Modules that are prototyped and under development.
- Collaborating across RF module design, MMIC design and assembly teams
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.
- DoD Clearance: Secret (active and existing security clearance required after day 1).
Qualifications
- BS degree in a Science, Technology, Engineering & Math (STEM) Field.
- Eight (8) or more years of relevant experience (An advanced STEM degree could count for 3 years of experience) in Microwave/RF module, subsystem and component analysis, design, and test.
- Hands-on experience with electromagnetic simulation tools such as HFSS, ADS, CST.
- The ability to obtain and maintain a US security clearance.
Skills
- Master’s degree or PhD. in a STEM Field (preferred).
- Experience in module/sub-system assembly & packaging process.
- Experience in thermal modeling and analysis.
- Experience of different topology trade-offs, process and active/passive component selection, system/sub-system level, gain-loss analysis and flowing down requirements from the system to the component level.
- Layout experience in Mentor Graphics’ Xpedition, Cadence Virtuoso or AutoCAD.
- Experience with analytical tools such as Matlab, Python, or JMP.
- Understanding of allocating and flowing down requirements from the system to the component level.
- Experience in a production environment.
- Experience with microwave testing techniques, including using spectrum analyzers, Real-time Spectrum Analyzers (RSAs), Vector Network Analyzers (VNAs) and Performance Network Analyzer (PNAs).
- Experience with GaAs and/or GaN MMIC devices.
- Experience leading teams and/or projects.
- Current DoD Secret level security clearance (preferred).
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 and holidays.
- Annual short-term and/or long-term incentive compensation programs (depending on level and collective-bargaining agreement).
Pay
The salary range for this role is 107,500 USD - 204,500 USD.
We need to ensure we didn't include any boilerplate like EEO, privacy policy, etc. We removed those.
Check for duplicated lines: we have not repeated.
Check for any placeholder text: none.
Check that we didn't create Schedule section (we didn't). Good.
Check that we didn't repeat job title as heading (we didn't). Good.
Check that we didn't put Job ID/requisition numbers as headings (none present). Good.
Check that we preserved all substantive information: Let's verify.
From posting:
- Date posted, location, role type: we included in short p.
- Raytheon values paragraph: included under About the role.
- Job Summary: included.
- What You Will Do: included as Responsibilities.
- Qualifications You Must Have: included as Qualifications.
- Qualifications We Prefer: included as Skills (we added "preferred" note). Might be better to have a separate "Preferred Qualifications" heading but Skills is allowed. However we might want to rename to "Preferred Qualifications" but instruction list includes Skills as an example heading; we can use Skills. It's okay.
- What We Offer: includes values (we already used values in About the role; but we might be duplicating values. The values appear both in About the role paragraph and in What We Offer list. The posting's "What We Offer" starts with "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." That's a list of values. We already have a paragraph about Raytheon's foundation etc. That's different. The values list is separate. We should include that list somewhere. We could include it under Benefits or maybe under About the role as a list. But we already used About the role for the foundation paragraph. We could add a second paragraph under About the role for the values list, or we could create a separate section "Values" but not in allowed head
for prose. Do NOT repeat the job title as a heading. Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to include based on content. Content includes: - Date posted, location, etc. Might be minor metadata; we can put in a short
maybe. - Position Role Type: Onsite - 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 after day 1 - Raytheon values paragraph (foundation...) - Job Summary: description of role. - What You Will Do: bullet list of duties. - Qualifications You Must Have: list. - Qualifications We Prefer: list. - What We Offer: values list, plus salary range, benefits description. We need sections: maybe "About the role" (Raytheon values and mission), "Job Summary", "Responsibilities" (What You Will Do), "Requirements" (security clearance, citizenship), "Qualifications" (must have), "Preferred Qualifications" (maybe combine with Qualifications? but we can have separate sections: "Qualifications" and "Preferred Qualifications" or "Skills"? The instruction list includes Skills as possible heading. But we can just use "Qualifications" for must-have and "Preferred Qualifications" for preferred. However they said use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can map: - About the role: Raytheon values paragraph. - Responsibilities: What You Will Do (list). - Requirements: security clearance and citizenship (maybe also location Onsite? but location is minor metadata; we can include in a short p). - Qualifications: Must Have list. - Skills: maybe Preferred Qualifications list (skills). Or we could put Preferred Qualifications under Skills. - Benefits: What We Offer includes values and benefits list; also salary range (Pay). So we need Pay section for salary range, Benefits section for benefits list, maybe also include values under About the role? But values already in About the role; we could also include values in Benefits? The instruction says include a section only when posting has real specific content. The posting includes "What We Offer: Our values drive our actions..." then list of values, then salary range, then benefits list. So we can have: - About the role: maybe the Raytheon mission paragraph (foundation...). - Benefits: list of benefits (medical, dental, etc.) plus maybe values? But values are also in What We Offer. Could put values under About the role, and benefits under Benefits. - Pay: salary range. - Schedule: maybe not specified; they didn't give schedule details besides Onsite. Could we put Schedule? The posting says Position Role Type: Onsite. That's schedule type. Could be considered schedule. But they said never create Schedule section unless posting actually states them. It does state Onsite. So we could include Schedule with content "Onsite". However they said prefer a few substantive sections over many thin ones. A section with just "Onsite" might be thin. Could we fold Onsite into a short p under About the role or Requirements? Probably better to include a short p with metadata: Date posted, location, role type. But they said do not put Job ID/requisition numbers as headings — fold minor metadata into a short
or drop it. So we can have a short p at top: "Posted 2026-09-15 • Andover, MA • Onsite". That covers date, location, role type. Thus we may not need a separate Schedule section. Now we need to remove boilerplate: EEO, privacy policy, etc. Also remove duplicated lines. We need to preserve all substantive information: include all duties, qualifications, preferred qualifications, benefits list, salary range. We must not invent or summarize away detail. We need to output only HTML fragment, no /, no markdown fences. We'll produce something like:
Posted 2026-09-15 • Andover, MA • Onsite
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.
Job Summary
An exciting opportunity exists for an experienced Principal RF Module Design/Development Engineer to join our Module Development Section within the RF Microelectronics/Module Development & Foundry Services (RFMicro) Department. The RFMicro department designs, fabricates, and tests state-of-the-art Monolithic Microwave Integrated Circuits (MMICs) in our on-site foundry. These chips are designed into custom modules to support multiple programs and enhance the capabilities of next generation radar systems. The successful candidate will be responsible for designing power combining structures, capabilities and transitions for RF/microwave modules containing GaAs- and GaN-based MMIC products. This would be in active support of existing technologies in production as well as next-generation products in development. This position requires a strong academic background and experience in RF/Microwave Design, Development, Integration & Test.
Responsibilities
- Designing RF structures and transitions on multi-layer, multi-channel RF Modules and analog circuitry enabling both receive and transmit behavior.
- 3D electromagnetic simulations of power combining and other RF structures.
- Troubleshooting RF Modules that are prototyped and under development.
- Collaborating across RF module design, MMIC design and assembly teams
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.
- DoD Clearance: Secret (active and existing security clearance required after day 1).
Qualifications
- BS degree in a Science, Technology, Engineering & Math (STEM) Field.
- Eight (8) or more years of relevant experience (An advanced STEM degree could count for 3 years of experience) in Microwave/RF module, subsystem and component analysis, design, and test.
- Hands-on experience with electromagnetic simulation tools such as HFSS, ADS, CST.
- The ability to obtain and maintain a US security clearance.
Skills
- Master’s degree or PhD. in a STEM Field (preferred).
- Experience in module/sub-system assembly & packaging process.
- Experience in thermal modeling and analysis.
- Experience of different topology trade-offs, process and active/passive component selection, system/sub-system level, gain-loss analysis and flowing down requirements from the system to the component level.
- Layout experience in Mentor Graphics’ Xpedition, Cadence Virtuoso or AutoCAD.
- Experience with analytical tools such as Matlab, Python, or JMP.
- Understanding of allocating and flowing down requirements from the system to the component level.
- Experience in a production environment.
- Experience with microwave testing techniques, including using spectrum analyzers, Real-time Spectrum Analyzers (RSAs), Vector Network Analyzers (VNAs) and Performance Network Analyzer (PNAs).
- Experience with GaAs and/or GaN MMIC devices.
- Experience leading teams and/or projects.
- Current DoD Secret level security clearance (preferred).
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 and holidays.
- Annual short-term and/or long-term incentive compensation programs (depending on level and collective-bargaining agreement).
Pay
The salary range for this role is 107,500 USD - 204,500 USD.
We need to ensure we didn't include any boilerplate like EEO, privacy policy, etc. We removed those. Check for duplicated lines: we have not repeated. Check for any placeholder text: none. Check that we didn't create Schedule section (we didn't). Good. Check that we didn't repeat job title as heading (we didn't). Good. Check that we didn't put Job ID/requisition numbers as headings (none present). Good. Check that we preserved all substantive information: Let's verify. From posting: - Date posted, location, role type: we included in short p. - Raytheon values paragraph: included under About the role. - Job Summary: included. - What You Will Do: included as Responsibilities. - Qualifications You Must Have: included as Qualifications. - Qualifications We Prefer: included as Skills (we added "preferred" note). Might be better to have a separate "Preferred Qualifications" heading but Skills is allowed. However we might want to rename to "Preferred Qualifications" but instruction list includes Skills as an example heading; we can use Skills. It's okay. - What We Offer: includes values (we already used values in About the role; but we might be duplicating values. The values appear both in About the role paragraph and in What We Offer list. The posting's "What We Offer" starts with "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." That's a list of values. We already have a paragraph about Raytheon's foundation etc. That's different. The values list is separate. We should include that list somewhere. We could include it under Benefits or maybe under About the role as a list. But we already used About the role for the foundation paragraph. We could add a second paragraph under About the role for the values list, or we could create a separate section "Values" but not in allowed head