Sr. Radar Analysis Engineer

We need to output HTML fragment with sections for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes: Title, Program Summary, Job Summary, Basic Qualifications, Preferred Qualifications, Belong, Connect and Grow at KBR (culture), EEO statement, Job ID. No explicit Benefits, Pay, Schedule. So we should not create those sections. We need to use

for section headings. Use

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

  for prose. We need to preserve all substantive information, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). The EEO statement is boilerplate; we should remove it. Also "Belong, Connect and Grow at KBR" maybe considered culture but not a standard heading; we could include as a section maybe "About KBR" but not in list. The instruction says use headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings? It says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely we should stick to those headings only if content exists. So we can have About the role (job summary), Responsibilities (maybe from job summary?), Requirements (basic qualifications), Qualifications (preferred qualifications), Skills (maybe from preferred qualifications). We need to decide what goes where. We must not repeat the job title as a heading. The page already shows it, so we omit. We need to include all substantive info: Program Summary, Job Summary, Basic Qualifications, Preferred Qualifications, Belong, Connect and Grow at KBR (maybe as a short paragraph). Also maybe mention travel 20%, US Citizen, Secret clearance. We need to format lists where appropriate. Let's extract content: Title: Sr. Radar Analysis Engineer Program Summary: KBR’s Missile, Aviation, and Ground Systems (MAGS) division delivers mission engineering solutions for critical U.S. Army programs, specializing in aviation and ground systems, integrated air and missile defense, and threat and target systems. As a trusted partner of the U.S. Department of War, MAGS provides innovative, technology-driven solutions to enhance national security. With a global presence and a strong ethical framework, KBR ensures secure, effective, and mission-ready capabilities worldwide. Job Summary: Join a dynamic team of talented and inspired engineers developing a US Army radar system. This program integrates state-of-the-art sensor technology with existing Army Air and Missile Defense systems, and requires in-depth understanding of Radar systems and theory, and hardware background. Candidates require strong analytical and problem-solving skills to perform data analysis and reporting of radar data from modeling and simulation and live events. Candidates will be required to become competent in data reduction software, data reduction output, and analysis tools. You will interface directly with the Government customer and contractor subject matter experts regularly. Basic Qualifications: - Possess a Bachelor of Science degree in engineering (electrical, software, computer, etc.) or other STEM related fields (physics, Mathematics, Computer Science, etc.) with 8+ years of experience or a Master’s Degree in degree in engineering (electrical, software, computer, etc.) or other STEM related fields (physics, Mathematics, Computer Science, etc.) with 6+ years of experience. - Demonstrated expertise of AESA radar hardware, radar architecture and signal processing. - Need to be familiar with DoD systems engineering processes and provide SME expertise to customers on daily basis. - Working knowledge of programming languages such as C, C++, MATLAB, and Python. - Candidate must be a US Citizen. - Possess or be able to obtain (and be able to maintain) a Secret Clearance. - Able to travel 20% of the time. Preferred Qualifications: - Bachelor of Science or Master of Science degree in Electrical Engineering. - Experience directly supporting a Government customer. - Technical expertise with ability to logically formulate solutions for execution on prescribed schedules. - Excellent written and verbal communication skills, strong social skills, and ability to build consensus among peers while building solid relationships with team members, leadership, and customers. - Proficiency in Microsoft Office applications with strong presentation skills and capable of briefing audiences large or small of varying technical knowledge. - Enjoy working in a dynamic, responsive, and collaborative environment, and dedicated to the success of our Government customers. 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. We need to remove EEO statement and Job ID. Now decide sections: About the role: Could combine Program Summary and Job Summary? Usually About the role includes overview. We'll put Program Summary and Job Summary as prose under About the role. Responsibilities: Could be derived from Job Summary: developing US Army radar system, integrate sensor tech, understanding radar systems, perform data analysis/reporting, become competent in data reduction software/tools, interface with Gov customer and SMEs. We'll list as

  • . Requirements: Basic Qualifications (maybe as list). Could also include citizenship, clearance, travel. Qualifications: Preferred Qualifications (list). Skills: Could be extracted from Preferred Qualifications: communication, Microsoft Office, presentation, teamwork, etc. But we might combine with Qualifications. However instruction says prefer few substantive sections over many thin ones. So maybe we combine Qualifications and Skills into one section? But they ask to use headings like Skills if content exists. We have content for Skills (communication, Microsoft Office, presentation). Could create Skills section. But we must not create sections with filler. We have real content for Skills. Thus sections: About the role, Responsibilities, Requirements, Qualifications, Skills. Possibly also a section for "About KBR" (Belong, Connect and Grow) but not in list; maybe we could put under About the role or as a separate section "Company Overview". But instruction only gave examples; not strict. Safer to include a section "About KBR" as

    About KBR

    with that paragraph. It's substantive. We must not include Benefits, Pay, Schedule. Now format:

    About the role

    Program Summary: ...

    Job Summary: ...

    But we might combine into one

    with both paragraphs. Better:

    Program Summary: ...

    Job Summary: ...

    Responsibilities:
    • ...
    Requirements:
    • ...
    (basic qualifications) Qualifications:
    • ...
    (preferred qualifications) Skills:
    • ...
    (communication, Microsoft Office, presentation, teamwork, etc.) About KBR:

    About KBR

    ...

    Make sure no duplicate lines. Now extract exact text, preserving meaning but not copying boilerplate. Program Summary text: "KBR’s Missile, Aviation, and Ground Systems (MAGS) division delivers mission engineering solutions for critical U.S. Army programs, specializing in aviation and ground systems, integrated air and missile defense, and threat and target systems. As a trusted partner of the U.S. Department of War, MAGS provides innovative, technology-driven solutions to enhance national security. With a global presence and a strong ethical framework, KBR ensures secure, effective, and mission-ready capabilities worldwide." Job Summary: "Join a dynamic team of talented and inspired engineers developing a US Army radar system. This program integrates state-of-the-art sensor technology with existing Army Air and Missile Defense systems, and requires in-depth understanding of Radar systems and theory, and hardware background. Candidates require strong analytical and problem-solving skills to perform data analysis and reporting of radar data from modeling and simulation and live events. Candidates will be required to become competent in data reduction software, data reduction output, and analysis tools. You will interface directly with the Government customer and contractor subject matter experts regularly." Now Responsibilities list items: - Developing a US Army radar system. - Integrating state-of-the-art sensor technology with existing Army Air and Missile Defense systems. - Applying in-depth understanding of radar systems, theory, and hardware background. - Performing data analysis and reporting of radar data from modeling and simulation and live events. - Becoming competent in data reduction software, data reduction output, and analysis tools. - Interfacing directly with Government customer and contractor subject matter experts regularly. We could phrase as bullet points. Requirements list (Basic Qualifications): - Bachelor of Science degree in engineering (electrical, software, computer, etc.) or other STEM related fields (physics, Mathematics, Computer Science, etc.) with 8+ years of experience, or a Master’s Degree in engineering (electrical, software, computer, etc.) or other STEM related fields (physics, Mathematics, Computer Science, etc.) with 6+ years of experience. - Demonstrated expertise of AESA radar hardware, radar architecture, and signal processing. - Familiarity with DoD systems engineering processes and ability to provide SME expertise to customers on a daily basis. - Working knowledge of programming languages such as C, C++, MATLAB, and Python. - Must be a US Citizen. - Ability to obtain and maintain a Secret Clearance. - Able to travel 20% of the time. We need to keep the exact meaning; we can rephrase slightly but preserve info. Preferred Qualifications list: - Bachelor of Science or Master of Science degree in Electrical Engineering. - Experience directly supporting a Government customer. - Technical expertise with ability to logically formulate solutions for execution on prescribed schedules. - Excellent written and verbal communication skills, strong social skills, and ability to build consensus among peers while building solid relationships with team members, leadership, and customers. - Proficiency in Microsoft Office applications with strong presentation skills and capable of briefing audiences large or small of varying technical knowledge. - Enjoy working in a dynamic, responsive, and collaborative environment, and dedicated to the success of our Government customers. Skills list: Could be communication, Microsoft Office, presentation, teamwork, collaboration, etc. But we already have many of those in Preferred Qualifications. To avoid duplication, maybe we put communication, Microsoft Office, presentation, teamwork under Skills, and keep Preferred Qualifications focusing on education/experience. However the instruction says preserve ALL substantive information; we can split but must not lose any. So we could keep Preferred Qualifications as is, and Skills could be a subset but we would be duplicating content. Better to not duplicate; we could move communication, Microsoft Office, presentation, teamwork to Skills and remove from Preferred Qualifications, but then we lose that info from Preferred Qualifications unless we keep it there too. Duplication is allowed? The instruction says preserve ALL substantive information; duplication is not prohibited but might be redundant. Safer to keep Preferred Qualifications as is and not create a Skills section if it would duplicate. However we could create Skills section for items not covered elsewhere: maybe "strong analytical and problem-solving skills" already in Responsibilities. But we already have that. Given the instruction to prefer few substantive sections over many thin ones, maybe we skip Skills section altogether and put those skills under Preferred Qualifications or Responsibilities. Since we already have communication etc in Preferred Qualifications, we can keep them there. So we will not create a Skills section. Thus sections: About the role, Responsibilities, Requirements, Qualifications (Preferred). Possibly also About KBR. Now check if we need to include "Belong, Connect and Grow at KBR" as a section. It's substantive but not a standard heading; we could include as

    About KBR

    . That seems okay. Now produce HTML fragment. Make sure to not include any markdown fences. Let's craft:

    About the role