RF Analyst – Senior
or drop it. The Job ID is "R2123022". We can drop it or put in a short p. We need to use
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. But we can choose which sections to include based on content. The posting includes: About the role (intro), Why Join Us? (maybe part of About the role?), Responsibilities (Primary Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications maybe?), Skills (maybe not explicit), Pay (Basic Compensation), Benefits, Schedule? There's mention: "This role is performed full-time on site at a government facility". That's schedule info (full-time on site). So we can include Schedule section with that content.
We need to avoid filler like "commensurate with experience". Not present.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the content verbatim or close but not lose details.
We need to use - for any list of duties/requirements/benefits. So for responsibilities list, we need
- . For qualifications list (Required Qualifications) maybe bullet list? It's a paragraph with multiple sentences; but we can treat each sentence as list? The instruction: use
- for any list of duties/requirements/benefits. The Required Qualifications is not a list but a set of statements; we could keep as
. However we could break into bullet points if they are separate items. But safer to keep as
for prose. For Preferred Qualifications also as
. For Benefits list: they gave a sentence with possible benefits; we can make a
- list of those benefits.
For Pay: we have Basic Compensation range and Additional Compensation description. We can put Pay section with that info.
For Schedule: we have "This role is performed full-time on site at a government facility and is contingent upon contract award." Also earlier: "This is a contingent position based upon contract award". So schedule: full-time on site.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement and "Ready to Make a Difference?" etc. The EEO statement is boilerplate; we should remove it. Also "Ready to Make a Difference?" is maybe a call to action; could be considered application instruction? It's encouraging to apply; maybe we should remove as it's application instruction. The instruction says remove application instructions. So we should remove that paragraph. Also "Belong, Connect and Grow at KBR" etc is maybe part of culture; could keep as About the role? It's not boilerplate; it's about company culture. Might keep.
We need to preserve all substantive information; so we keep the "Why Join Us?" bullet points (Innovative Projects, Collaborative Environment, Impactful Work). Those are substantive.
We need to output only HTML fragment, no /, no markdown.
Let's structure:
About the role
Belong. Connect. Grow KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security.
Why Join Us?
- Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
- Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
- Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense.
This is a contingent position based upon contract award.
Responsibilities
- Lead technical assessments of RF-DE vulnerabilities for mission-critical systems and platforms; prioritize work across multiple efforts.
- Develop and refine RF threat models and vulnerability analysis methodologies (e.g., coupling pathways, susceptibility thresholds, system-level impacts).
- Provide expert guidance on protective measures and mitigation strategies (shielding/grounding, filtering, architectural changes, operational constraints).
- Oversee planning and execution of complex RF exposure test campaigns; ensure measurement integrity, configuration control, and safety compliance.
- Collaborate with engineering, operations, and program management teams to integrate RF protection requirements into system design and sustainment.
- Prepare and deliver technical reports, risk assessments, and executive-level briefings, articulate trade-offs, confidence, and residual risk.
- Support verification of mitigations through follow-on testing and/or analysis; document lessons learned and update best practices.
- Mentor junior engineers and analysts in RF vulnerability analysis techniques; perform quality assurance reviews of products.
- Ensure compliance with organizational standards and applicable regulatory frameworks related to spectrum, RF safety, and mission assurance.
Requirements
Education & Experience: Master’s degree and 11 years of relevant experience with demonstrated expertise OR Bachelor’s degree and 12 years of relevant experience with demonstrated expertise OR No degree and 14 years of relevant experience with demonstrated expertise. Extensive experience in RF vulnerability analysis, electromagnetic effects, RF systems engineering, or directed energy threat assessment. Proven ability to develop and apply vulnerability models and risk mitigation strategies for complex systems. In-depth knowledge of EMI/EMC, RF coupling mechanisms, measurement approaches, and system-level integration considerations. Active Top Secret/Sensitive Compartmented Information (TS/SCI) clearance with adjudicated polygraph.
Qualifications
Preferred Qualifications: Prior experience supporting national security or aerospace programs involving RF threat environments, EW, or RF-DE effects assessments. Advanced knowledge of hardening approaches, protective design, and verification methods for electromagnetic effects resilience. Familiarity with relevant test and compliance standards and guidance (e.g., MIL-STD-461, MIL-STD-464, HIRF guidance, and RF safety practices as applicable).
Pay
Basic Compensation: $183,600.00 - $224,300.00 (this is for the Springfield, VA area only). The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity.
Additional Compensation: KBR may offer bonuses, commissions, or other forms of compensation to certain job titles or levels, per internal policy or contractual designation. Additional compensation may be in the form of sign on bonus, relocation benefits, short term incentives, long term incentives, or discretionary payments for exceptional performance.
Benefits
- 401K plan with company match
- Medical, dental, vision
- Life insurance, AD&D
- Flexible spending account
- Disability
- Paid time off
- Flexible work schedule
- Professional training and development for career advancement
Schedule
This role is performed full-time on site at a government facility and is contingent upon contract award.
We need to ensure we didn't repeat job title as heading. We didn't. We didn't include Job ID. We removed EEO and application instructions. We kept "Belong. Connect. Grow" etc. The "Why Join Us?" section is included as its own heading; but the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join Us?" is not in that list. The instruction: use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should prefer those headings. It says "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It didn't forbid other headings, but the examples suggest we should stick to those. However "Why Join Us?" is a substantive section; we could incorporate its content into About the role or maybe under a generic heading like "About the role". But the instruction says use those headings for section headings; it's not strict that we cannot use others, but better to follow examples. We could merge "Why Join Us?" bullet points into About the role section. Let's do that: About the role includes the intro and the Why Join Us bullets.
Thus we will have About the role with paragraphs and a ul for the three bullet points.
Then Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule.
We need to ensure we don't have a Skills section (no specific skills listed). So we omit.
Now check we haven't missed any substantive info: The "Why Join Us?" bullets are included. The "This is a contingent position based upon contract award." we placed in About the role? Actually we placed it as a separate p after the intro? We could include it in About the role as well. Let's put it in About the role after the intro.
Also we have "This role is performed full-time on site at a government facility and is contingent upon contract award." That's schedule.
We also have "The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity." Already in Pay.
We have "Additional Compensation" paragraph.
We have Benefits list.
We have "Ready to Make a Difference?" removed.
We have "Belong, Connect and Grow at KBR" and the Zero Harm culture paragraph. That's substantive; we can include in About the role as well.
Let's craft About the role:
Belong. Connect. Grow KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security.
This is a contingent position based upon contract award.
- Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
- Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
- Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense.
At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and
- . For qualifications list (Required Qualifications) maybe bullet list? It's a paragraph with multiple sentences; but we can treat each sentence as list? The instruction: use
- for any list of duties/requirements/benefits. The Required Qualifications is not a list but a set of statements; we could keep as
. However we could break into bullet points if they are separate items. But safer to keep as
for prose. For Preferred Qualifications also as
. For Benefits list: they gave a sentence with possible benefits; we can make a
- list of those benefits.
For Pay: we have Basic Compensation range and Additional Compensation description. We can put Pay section with that info.
For Schedule: we have "This role is performed full-time on site at a government facility and is contingent upon contract award." Also earlier: "This is a contingent position based upon contract award". So schedule: full-time on site.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement and "Ready to Make a Difference?" etc. The EEO statement is boilerplate; we should remove it. Also "Ready to Make a Difference?" is maybe a call to action; could be considered application instruction? It's encouraging to apply; maybe we should remove as it's application instruction. The instruction says remove application instructions. So we should remove that paragraph. Also "Belong, Connect and Grow at KBR" etc is maybe part of culture; could keep as About the role? It's not boilerplate; it's about company culture. Might keep.
We need to preserve all substantive information; so we keep the "Why Join Us?" bullet points (Innovative Projects, Collaborative Environment, Impactful Work). Those are substantive.
We need to output only HTML fragment, no /, no markdown.
Let's structure:
About the role
Belong. Connect. Grow KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security.
Why Join Us?
- Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
- Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
- Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense.
This is a contingent position based upon contract award.
Responsibilities
- Lead technical assessments of RF-DE vulnerabilities for mission-critical systems and platforms; prioritize work across multiple efforts.
- Develop and refine RF threat models and vulnerability analysis methodologies (e.g., coupling pathways, susceptibility thresholds, system-level impacts).
- Provide expert guidance on protective measures and mitigation strategies (shielding/grounding, filtering, architectural changes, operational constraints).
- Oversee planning and execution of complex RF exposure test campaigns; ensure measurement integrity, configuration control, and safety compliance.
- Collaborate with engineering, operations, and program management teams to integrate RF protection requirements into system design and sustainment.
- Prepare and deliver technical reports, risk assessments, and executive-level briefings, articulate trade-offs, confidence, and residual risk.
- Support verification of mitigations through follow-on testing and/or analysis; document lessons learned and update best practices.
- Mentor junior engineers and analysts in RF vulnerability analysis techniques; perform quality assurance reviews of products.
- Ensure compliance with organizational standards and applicable regulatory frameworks related to spectrum, RF safety, and mission assurance.
Requirements
Education & Experience: Master’s degree and 11 years of relevant experience with demonstrated expertise OR Bachelor’s degree and 12 years of relevant experience with demonstrated expertise OR No degree and 14 years of relevant experience with demonstrated expertise. Extensive experience in RF vulnerability analysis, electromagnetic effects, RF systems engineering, or directed energy threat assessment. Proven ability to develop and apply vulnerability models and risk mitigation strategies for complex systems. In-depth knowledge of EMI/EMC, RF coupling mechanisms, measurement approaches, and system-level integration considerations. Active Top Secret/Sensitive Compartmented Information (TS/SCI) clearance with adjudicated polygraph.
Qualifications
Preferred Qualifications: Prior experience supporting national security or aerospace programs involving RF threat environments, EW, or RF-DE effects assessments. Advanced knowledge of hardening approaches, protective design, and verification methods for electromagnetic effects resilience. Familiarity with relevant test and compliance standards and guidance (e.g., MIL-STD-461, MIL-STD-464, HIRF guidance, and RF safety practices as applicable).
Pay
Basic Compensation: $183,600.00 - $224,300.00 (this is for the Springfield, VA area only). The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity.
Additional Compensation: KBR may offer bonuses, commissions, or other forms of compensation to certain job titles or levels, per internal policy or contractual designation. Additional compensation may be in the form of sign on bonus, relocation benefits, short term incentives, long term incentives, or discretionary payments for exceptional performance.
Benefits
- 401K plan with company match
- Medical, dental, vision
- Life insurance, AD&D
- Flexible spending account
- Disability
- Paid time off
- Flexible work schedule
- Professional training and development for career advancement
Schedule
This role is performed full-time on site at a government facility and is contingent upon contract award.
We need to ensure we didn't repeat job title as heading. We didn't. We didn't include Job ID. We removed EEO and application instructions. We kept "Belong. Connect. Grow" etc. The "Why Join Us?" section is included as its own heading; but the allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. "Why Join Us?" is not in that list. The instruction: usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says e.g., meaning those are examples, but we should prefer those headings. It says "IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". It didn't forbid other headings, but the examples suggest we should stick to those. However "Why Join Us?" is a substantive section; we could incorporate its content into About the role or maybe under a generic heading like "About the role". But the instruction says use those headings for section headings; it's not strict that we cannot use others, but better to follow examples. We could merge "Why Join Us?" bullet points into About the role section. Let's do that: About the role includes the intro and the Why Join Us bullets. Thus we will have About the role with paragraphs and a ul for the three bullet points. Then Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. We need to ensure we don't have a Skills section (no specific skills listed). So we omit. Now check we haven't missed any substantive info: The "Why Join Us?" bullets are included. The "This is a contingent position based upon contract award." we placed in About the role? Actually we placed it as a separate p after the intro? We could include it in About the role as well. Let's put it in About the role after the intro. Also we have "This role is performed full-time on site at a government facility and is contingent upon contract award." That's schedule. We also have "The offered rate will be based on the selected candidate’s knowledge, skills, abilities and/or experience and in consideration of internal parity." Already in Pay. We have "Additional Compensation" paragraph. We have Benefits list. We have "Ready to Make a Difference?" removed. We have "Belong, Connect and Grow at KBR" and the Zero Harm culture paragraph. That's substantive; we can include in About the role as well. Let's craft About the role:
Belong. Connect. Grow KBR’s National Security Solutions team provides high-end engineering and advanced technology solutions to our customers in the intelligence and national security communities. In this position, your work will have a profound impact on the country’s most critical role – protecting our national security.
This is a contingent position based upon contract award.
- Innovative Projects: KBR’s work is at the forefront of engineering, logistics, operations, science, program management, mission IT and cybersecurity solutions.
- Collaborative Environment: Be part of a dynamic team that thrives on collaboration and innovation, fostering a supportive and intellectually stimulating workplace.
- Impactful Work: Your contributions will be pivotal in designing and optimizing defense systems that ensure national security and shape the future of space defense.
At KBR, we are passionate about our people and our Zero Harm culture. These inform all that we do and are at the heart of our commitment to, and
- list of those benefits.
For Pay: we have Basic Compensation range and Additional Compensation description. We can put Pay section with that info.
For Schedule: we have "This role is performed full-time on site at a government facility and is contingent upon contract award." Also earlier: "This is a contingent position based upon contract award". So schedule: full-time on site.
We need to remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. At end there is EEO statement and "Ready to Make a Difference?" etc. The EEO statement is boilerplate; we should remove it. Also "Ready to Make a Difference?" is maybe a call to action; could be considered application instruction? It's encouraging to apply; maybe we should remove as it's application instruction. The instruction says remove application instructions. So we should remove that paragraph. Also "Belong, Connect and Grow at KBR" etc is maybe part of culture; could keep as About the role? It's not boilerplate; it's about company culture. Might keep.
We need to preserve all substantive information; so we keep the "Why Join Us?" bullet points (Innovative Projects, Collaborative Environment, Impactful Work). Those are substantive.
We need to output only HTML fragment, no /, no markdown.
Let's structure:
- for any list of duties/requirements/benefits. The Required Qualifications is not a list but a set of statements; we could keep as