Senior Electronic Warfare Systems Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use

for each heading. Use

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

  for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings; fold minor metadata into short

  or drop it. Preserve all substantive info; do not invent or summarize away detail. Remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Include a section ONLY when posting has real, specific content for it — never emit 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 posting actually states them. We have content: Job Summary (maybe "About the role"?). Role And Responsibilities (list). Basic Qualifications (education, experience, security clearance). Preferred Qualifications (list). Scheduled Weekly Hours: 40 hours/week. Compensation: $141,000-$212,000. Additional Compensation: KBR may offer bonuses... Additional compensation may be in the form of... KBR Benefits: KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development. Then some culture statements (Belong, Connect and Grow...). Then EEO statement (remove). Then Job ID R2130593 (drop or minor metadata). Also "The salary range posted is based on the national average..." etc. We need to decide sections: About the role (Job Summary). Responsibilities (list). Requirements (maybe Basic Qualifications). Qualifications (Preferred Qualifications). Skills (maybe not explicit; could combine with qualifications? The posting doesn't have a separate "Skills" section; we could omit Skills if no specific content. Benefits (we have benefits description). Pay (we have compensation range). Schedule (we have scheduled weekly hours). Ensure we don't create sections with filler. We must not repeat job title as heading. Use

  for each section heading. We need to preserve all substantive info; do not invent or summarize away detail. So we need to include all details from the posting, except boilerplate. Let's extract substantive content: Job Summary paragraph: "KBR is seeking a Senior Electronic Warfare Systems Engineer to support the Naval Air Systems Command (NAVAIR), Program Executive Office for Unmanned Aviation and Strike Weapons (PEO(U&W)), Program Management Air (PMA)-266. This position supports the MQ-9 Marine Air-Ground Task Force (MAGTF) Unmanned Aircraft System (UAS), Expeditionary (MUX) Family of Systems and associated airborne Electronic Warfare capabilities. The selected candidate will serve as a technical lead for the integration, certification, testing, fielding, and sustainment of advanced EW systems and payloads while supporting engineering, acquisition, and operational objectives. This role requires close collaboration with government, industry, test, and fleet stakeholders to ensure EW capabilities are effectively integrated into operational systems and meet mission requirements. The position offers the opportunity to directly influence future unmanned aviation survivability, electromagnetic spectrum operations, and advanced sensing capabilities supporting the Fleet." That's the About the role. Responsibilities: list of bullet points after "Role And Responsibilities". Let's extract each sentence as bullet. - Serve as the program's Electronic Warfare subject matter expert, providing technical recommendations and engineering assessments supporting acquisition, integration, fielding, and sustainment decisions. - Provide technical leadership for the integration, testing, certification, and sustainment of EW payloads and mission systems on the MQ-9 MUX MALE platform. - Develop, decompose, trace, and manage EW system requirements across aircraft, payload, ground control station, and mission system architectures. - Support development, integration, and assessment of Electronic Support (ES), Electronic Attack (EA), and Electronic Protection (EP) capabilities. - Conduct technical trade studies, analyses of alternatives, and engineering assessments to evaluate EW technologies, architectures, and mission solutions. - Support electromagnetic spectrum operations, RF compatibility assessments, and spectrum certification activities to ensure compliance with applicable standards and operational requirements. - Perform end-to-end technical integration of EW payloads with aircraft systems, mission processors, communications architectures, and Ground Control Stations. - Plan, coordinate, and support laboratory, ground, and flight test activities, including verification of requirements, certification objectives, and operational effectiveness. - Support System Requirements Reviews (SRR), Preliminary Design Reviews (PDR), Critical Design Reviews (CDR), Test Readiness Reviews (TRR), and other technical review events. - Evaluate EW system performance against operational requirements, threat environments, and mission objectives, identifying risks and recommending corrective actions. - Shape EW collection, Electronic Support Measures (ESM), and mission-data workflows while ensuring interoperability with Joint and Naval aviation architectures. - Support development of airworthiness, certification, technical manual, training, and sustainment documentation required for fielding and lifecycle support. - Collaborate with program managers, engineers, test teams, operators, and industry partners to ensure EW systems meet performance, safety, airworthiness, and certification requirements. - Other duties as assigned in support of mission and business requirements. Basic Qualifications: Education, Experience, Security Clearance. - Education: Bachelor's degree in Electrical Engineering, Systems Engineering, Aerospace Engineering, Physics, or a related technical discipline. Additional relevant experience may be considered in lieu of formal education. - Experience: Minimum twelve (12) years of experience supporting the design, integration, acquisition, testing, deployment, or sustainment of complex aerospace, aviation, EW, RF, or defense systems. Experience developing, integrating, operating, or sustaining Electronic Warfare systems. Experience supporting systems engineering activities including requirements development, architecture development, integration, verification, validation, or test. - Security Clearance: Active Secret security clearance with the ability to obtain and maintain Top Secret/Sensitive Compartmented Information (TS/SCI) eligibility. U.S. Citizenship required. Preferred Qualifications: list. - Master's degree in Electrical Engineering, Systems Engineering, Aerospace Engineering, Physics, or related technical discipline. - INCOSE ASEP, CSEP, or ESEP certification, or DAWIA certification. - Experience supporting NAVAIR Systems Engineering Technical Review (SETR) processes. - Experience with electromagnetic spectrum operations, spectrum certification, and RF systems engineering. - Experience with SIGINT, ELINT, Electronic Support Measures (ESM), ISR payloads, or airborne sensing systems. - Experience supporting EW developmental testing, operational testing, and flight test programs. - Experience integrating airborne EW systems with command-and-control, tactical data link, mission-management, or Joint All-Domain Command and Control (JADC2) architectures. - Demonstrated experience supporting NAVAIR programs. - Experience supporting military avionics systems. - Experience supporting unmanned aviation systems, particularly the MQ-9 MAGTF UAS/MUX Family of Systems or similar Group 4/5 UAS programs. - Experience preparing formal engineering reports, technical correspondence, requirements documentation, and executive briefing materials. Scheduled Weekly Hours: 40 hours/week. Compensation: $141,000-$212,000. The salary range posted is based on the national average. The offered rate will be based on the selected candidate’s location, knowledge, skills, abilities, and/or experience, contract affordability, 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 a sign-on bonus, relocation benefits, short-term incentives, long-term incentives, or discretionary payments for exceptional performance. KBR Benefits: KBR offers a selection of competitive lifestyle benefits which could include 401K plan with company match, medical, dental, vision, life insurance, AD&D, flexible spending account, disability, paid time off, or flexible work schedule. We support career advancement through professional training and development. Culture statements: "Belong, Connect and Grow at KBR 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 ongoing journey toward being a People First company. That commitment is central to our team of team’s philosophy and fosters an environment where everyone can Belong, Connect and Grow. We Deliver – Together." This is not a standard section; could be considered part of Benefits? But it's more about company culture. The instruction: include a section ONLY when posting has real, specific content for it — never emit a heading followed by filler/placeholder text. This is substantive content but not a standard heading. Could we include it under Benefits? Might be okay to add a separate section like "Company Culture" but not in the prescribed list. The list of allowed headings is given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We should stick to those. The culture statements could be placed under Benefits? Not exactly. Could be omitted? But we must preserve ALL substantive information; do NOT invent or summarize away detail. If we omit culture statements, we lose substantive info. However, we could incorporate them into Benefits section as additional detail (like "KBR offers ... We support career advancement ... Belong, Connect and Grow..."). That would preserve the info while staying within Benefits heading. That seems acceptable. Job ID R2130593: minor metadata; we can fold into a short

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

  or drop it. So we can either drop it or include a short paragraph at end maybe not needed. Safer to drop. Now we need to output HTML fragment only, no /, no markdown fences. We'll produce sections:

  About the role

  Job summary paragraph.

  Responsibilities

  • ...
  ...

  Requirements

  Education: ...

  Experience: ...

  Security Clearance: ...

  Alternatively could use
  for each but instruction: Use
  • for any list of duties/requirements/benefits, and

    for prose. For Requirements, we have three items; could be a list. But they are not a list of duties; they are qualifications. Could treat as list. Safer to use

    • for each requirement. Similarly for Qualifications (Preferred) use list. Skills: we have no explicit skills section; we could omit Skills heading. Benefits: we have benefits description plus culture statements; we can combine into
      • for each benefit item? The benefits list includes multiple items; we can list them. Also include "We support career advancement through professional training and development." and culture statements. Pay: we have compensation range and additional compensation details; we can put in

        maybe with

        for additional compensation? The instruction: Use
        • for any list of duties/requirements/benefits. Pay is not a list; we can use

          . But we have additional compensation which is a list; could use

          . Schedule: we have scheduled weekly hours; we can use

          . Now ensure we don't create sections with filler. All sections have real content. Let's craft. First, About the role paragraph: copy exactly. Second, Responsibilities list: each bullet as

          • . Third, Requirements list: Education, Experience, Security Clearance. Fourth, Qualifications list: Preferred Qualifications items. Fifth, Benefits list: include benefits items and culture statements. Sixth