Senior Evolved Strategic Systems (ESS) Ground Systems Integration Engineer

We need to output HTML fragment with sections: About the role? Actually we need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. Must preserve all substantive info. We need to parse the posting. Key parts: - Intro: "Senior Evolved Strategic Systems (ESS) Ground Systems Integration Engineer Belong. Connect. Grow. with KBR! 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. KBR is seeking a Senior Evolved Strategic Systems (ESS) Ground Systems Integration Engineer to join our team in El Segundo, CA. Due to security requirements, work is required to be on-site in a secure facility. You will join a Systems Engineering team defining the next generation of space communication systems supporting Air Force Military Satellite Communications. You will support Systems Engineering & Integration activities in a multidisciplinary and collaborative environment. The Systems Integration Engineer will interface and collaborate with SE&I team members, contractors, government civilians and members of the US Space Force. The Systems Integration Engineer will lead and support several working groups responsible for leading technical discussion, resolve and identify risk, requirement gaps, developing briefings, writing and tracking action items, and authoring meeting minutes. The MILSATCOM Systems Engineering, Integration, and Test (MSEIT) effort provides leading edge Systems Engineering & Integration (SE&I) for the Air Force’s Space and Missiles System Center. We support the Air Force’s acquisition of state-of-the-art Military Satellite Communications systems, providing global secure, survivable, and protected communications for our nation’s warfighters. We seek technical individuals who will thrive in a highly collaborative work environment of small teams, using the most modern tools and methodologies to tackle the challenges of integrating complex space and ground communications systems." That's about the role. Could be "About the role". We'll include that as a

maybe multiple paragraphs. Then "Why Join Us?" with bullet points: Innovative Projects..., Collaborative Environment..., Impactful Work... That could be a Benefits? Actually it's more like "Why Join Us". Could be considered Benefits? But we have Benefits section for benefits like 401K etc. The "Why Join Us" is more like selling points; could be placed under "About the role" or maybe a separate section like "Why Join Us" but not in allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we need to map content accordingly. Responsibilities: The bullet list after "Key Responsibilities". That is a list of duties. We'll put under

Responsibilities

with

• each. Requirements: Might be the required qualifications? Usually "Qualifications" includes required and desired. But we have separate headings: Requirements, Qualifications, Skills. We need to decide distribution. The posting has "Qualifications Required:" then list: Active Secret clearance required with ability to obtain Top Secret; Bachelor's degree in ...; 15+ years experience; Experience with MILSATCOM; Experience working with military and DoD civilians; Demonstrated experience integrating Space and Ground segments; Strong interpersonal skills, communication (oral and written), and presentation skills; Proficient in Microsoft Office products; Due to security requirements, work is required to be on-site in a secure facility. Then "Desired TS/SCI (or eligible) clearance; MS degree in technical field; Experience with mission planning, COMSEC/TRANSEC, or key management; Demonstrated strong Systems Engineering and Technical Leadership experience; Knowledge and experience in Agile Development and collaboration tools (Jira/Confluence); INCOSE CSEP/ESEP certification or equivalent systems engineering credentials" Thus we can treat "Qualifications" as both required and desired? Or separate "Requirements" for required, "Qualifications" for desired? But we have also "Skills" maybe for technical skills like MBSE, Digital Twins, etc. However the responsibilities include many skills. The posting also mentions "Apply Digital Engineering methods and modeling strategies (e.g., MBSE, Digital Twins, digital threads, and analytical models)" etc. That could be skills. We need to avoid filler sections. We'll include sections that have substantive content. Let's plan: - About the role: intro paragraph(s) covering company description, role purpose, location, on-site, etc. - Responsibilities: list of key responsibilities (the bullet list after "Key Responsibilities"). - Qualifications: maybe combine required and desired? But we have also "Skills" maybe for technical skills like MBSE, Digital Twins, etc. However the responsibilities already mention those. Could put technical skills under Skills. Better: Use "Requirements" for required qualifications (clearance, degree, years experience, MILSATCOM experience, etc). Use "Qualifications" for desired qualifications (TS/SCI, MS degree, mission planning, Agile, INCOSE). Use "Skills" for specific technical skills like MBSE, Digital Twins, digital threads, analytical models, Microsoft Office, etc. But we already have Microsoft Office in required. Might be redundant. We need to ensure we don't create sections with filler like "commensurate with experience". We have actual content. Pay: The posting includes "Basic Compensation: $183,000-$228,000 in El Segundo, CA". So we can include Pay section with that. Schedule: The posting includes "Working Hours: Standard" under Work Environment. That's schedule info. So we can include Schedule section with "Standard working hours". Also location: On-site, Travel Requirements: Minimal. Could be part of About the role or Schedule? But schedule heading only for schedule; we can include location and travel under About the role. Benefits: The posting includes "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." So we can include Benefits section. Now we need to ensure we don't repeat job title as heading. We'll not. We'll output only HTML fragment. Structure:

  About the role

  ... (maybe multiple paragraphs)

  Responsibilities

  • ...
  ...

  Requirements

  • Active Secret clearance required with the ability to obtain a Top Secret clearance
  • Bachelor's degree in systems engineering, aerospace engineering, electrical engineering, computer engineering, physics, mathematics, or a related technical discipline
  • 15+ years experience in systems engineering, integration, or architecture development for complex aerospace, defense, or space systems
  • Experience with MILSATCOM, such as AEHF, PTS, EPS, WGS, and FAB-T terminal programs
  • Experience working with military and DoD civilians
  • Demonstrated experience integrating Space and Ground segments within national security space, military satellite communications, or related space programs
  • Strong interpersonal skills, communication (oral and written), and presentation skills
  • Proficient in Microsoft Office products (Word, Excel, PowerPoint)
  • Due to security requirements, work is required to be on-site in a secure facility

  Qualifications

  • Desired TS/SCI (or eligible) clearance
  • MS degree in technical field (such as engineering, mathematics, physics, or computer science) or Space Systems
  • Experience with mission planning, COMSEC/TRANSEC, or key management
  • Demonstrated strong Systems Engineering and Technical Leadership experience
  • Knowledge and experience in Agile Development and collaboration tools (Jira/Confluence)
  • INCOSE CSEP/ESEP certification or equivalent systems engineering credentials

  Skills

  • Apply Digital Engineering methods and modeling strategies (e.g., MBSE, Digital Twins, digital threads, and analytical models) to develop ground architectures, evaluate technical performance, support integration planning, and verify system behavior throughout the lifecycle
  But note that the skill about Digital Engineering appears in responsibilities bullet. Might be duplicate. Could still be under Skills. Alternatively we could put that bullet under Skills and not duplicate in Responsibilities. But responsibilities list includes many items; we should keep them as is. The skill bullet is part of responsibilities; we could keep it there and not duplicate. But we need a Skills section only if there is specific skill content not already covered. The posting mentions "Proficient in Microsoft Office products" which is a skill; also "Strong interpersonal skills, communication (oral and written), and presentation skills" which is skill. But those are already in Requirements/Qualifications. Might be okay to have Skills section with those items. But we must avoid duplication? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Duplication is not prohibited but might be redundant. Better to avoid duplication by placing skill-related items under Skills and not repeat elsewhere. However the responsibilities list includes many items that are not skill-specific; we can keep them. Let's examine responsibilities list: - Lead ground systems engineering and integration activities to develop, define, and implement ESS ground architectures, technical approaches, and engineering processes required to integrate satellite communication systems, segments (Ground, Space, Crypto, and Terminals), subsystems, elements, and components; establish, maintain, and control the technical baseline across multiple stakeholders and programs. - Perform analysis of the systems requirements that define the technical baseline and verification of the technical baseline - Apply Digital Engineering methods and modeling strategies (e.g., MBSE, Digital Twins, digital threads, and analytical models) to develop ground architectures, evaluate technical performance, support integration planning, and verify system behavior throughout the lifecycle. - Work with Government and contractor engineering teams to analyze, resolve, and document technical gaps, requirements discrepancies, interface issues, and architecture trades; support major requirements reviews, architecture reviews, design reviews, and other technical forums. - Lead and support Government/Contractor Working Group meetings—by developing briefings, leading discussion, and writing minutes—to address/resolve risks, issues, and action items - Review proposed changes to the technical baseline for impacts to enterprise capabilities and to cross-stakeholder integration concerns - Conduct trade studies, engineering analyses, and technical assessments to develop and evaluate alternative solutions for complex integration and architecture challenges; assess technical, cost, schedule, and performance impacts of recommended solutions. - Facilitate technical reviews of program documentation, including requirements specifications, interface control documents (ICDs), verification artifacts, engineering analyses, and design products; provide technical comments and adjudicate resolutions with stakeholders. - Serve as a subject matter expert to assess technical issues and to prepare briefings to U.S. Space Force program office personnel and other stakeholders; provide courses of actions to support Government decisions - Support management of risks, issues, interdependencies, identifying schedule disconnects and conflicts, developing action plans for resolution, and assisting the Government in executing selected solutions These are responsibilities. Now skills: maybe "Digital Engineering methods and modeling strategies (e.g., MBSE, Digital Twins, digital threads, and analytical models)" is a skill but it's already in responsibilities. Could still be under Skills but would duplicate. However duplication is not prohibited but might be considered unnecessary. The instruction: "Prefer a few substantive sections over many thin ones." Duplication could be considered thin? Not sure. Safer to not duplicate; we can keep that bullet under Responsibilities and not have a separate Skills section unless there are other skills not covered. What other skills? "Proficient in Microsoft Office products" is a skill but appears in Requirements. Could move to Skills and remove from Requirements? But then we lose that requirement info.