Agile Release 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. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate. We need to parse the posting. Title: Agile Release Engineer Belong. Connect. Grow. with KBR! (but we ignore title heading). The posting includes sections: "Why Join Us?" (maybe About the role?), "Who You Are", "Primary Responsibilities", "Required Qualifications", "Ready to Make a Difference?" (maybe not needed), "Basic Compensation", "Additional Compensation", "KBR Benefits", "Belong, Connect and Grow at KBR", "We Deliver – Together.", EEO etc. We need to map to headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role: maybe the introductory paragraph about KBR, mission, etc. Could be "Why Join Us?" and "Who You Are". We'll combine into About the role. Responsibilities: "Primary Responsibilities" list. Requirements: maybe "Required Qualifications" includes qualifications. Could be Requirements and Qualifications separate? The spec says we can have both Requirements and Qualifications sections. We need to decide what goes where. Typically Requirements = mandatory qualifications; Qualifications = preferred? But we have only one list: Required Qualifications. Could split into Requirements (mandatory) and Qualifications (preferred) but we don't have separate. We could put all under Requirements and leave Qualifications empty (but we must not emit empty sections). So we should only include sections with real content. So we can have either Requirements or Qualifications, not both. Choose Requirements for the mandatory list. Or we could treat Required Qualifications as Qualifications. But we need to follow spec: Use headings exactly as given: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only those with real content. We have content for About the role, Responsibilities, Required Qualifications (which could go under Requirements or Qualifications). We also have Skills maybe implied in qualifications (expertise with CI/CD tools, etc). Could extract skills into Skills section. Benefits: KBR Benefits section. Pay: Basic Compensation (and Additional Compensation). Schedule: not mentioned; we should not include Schedule unless present. No schedule info. Thus we will output sections: About the role, Responsibilities, Requirements (or Qualifications), Skills, Benefits, Pay. We need to decide which heading to use for the qualifications list. The posting says "Required Qualifications". That seems like Requirements. We'll put that under Requirements. Skills we can extract from the qualifications list: expertise with CI/CD tools, experience with cloud platforms, DevOps and automation skills, etc. Could also list communication, facilitation, problem-solving. We'll create a Skills subsection. We must preserve all substantive information; do not invent or summarize away detail. So we need to keep the details but can rephrase? We should preserve meaning but can format as list items. Must not omit details. Must not add new info. Thus we need to capture all points from the posting. Let's extract: About the role / Why Join Us? / Who You Are: Paragraphs: - 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. - Who You Are KBR is looking for a motivated Agile Release Engineer to join our team and provide Systems Engineer Technical Advisor (SETA) support for the Intelligence Community Customer Ground Enterprise Directorate (GED). GED plays a critical role in enabling the Intelligence Community Customer to plan and execute intelligence-gathering missions, transforming collected data into useful information for the Intelligence Community (IC) and Department of Defense (DoD) users. In this role, you will have the chance to design, develop, test, and deliver products that support our customers’ advanced systems. In support of GED Front Office, Chief Architect, Integrated Intelligence Program Office, Advanced Ground Office, and Enterprise Data Applications and Platforms. You'll collaborate with multi-disciplinary teams focused on hardware, software, system integration, and data analysis to help achieve important missions and meet requirements. This is a contingent position based upon contract award. We need to preserve all that. We'll put into

paragraphs. Responsibilities list: - Own and evolve CI/CD frameworks to support Agile delivery, ensuring speed, reliability, and scalability of releases. - Design, implement, and maintain automation for large-scale, complex software systems, reducing manual effort and improving release predictability. - Facilitate Agile Release Trains (ARTs), aligning teams on vision, roadmap, and backlog priorities, and ensuring adherence to SAFe or other Agile scaling frameworks. - Coordinate program-level processes across multiple Scrum and product teams, resolving dependencies, risks, and integration issues. - Manage release planning and execution, including backlog grooming, PI planning, and change management for delivery plans. - Coach and mentor technical teams, Scrum Masters, and stakeholders on Lean-Agile practices, continuous improvement, and quality standards. - Leverage Agile lifecycle management tools (e.g., Jira, Confluence, Azure DevOps) for planning, tracking, and reporting. - Drive operational excellence by improving release processes, reducing defects, and increasing delivery velocity. We'll put as

• . Requirements (Required Qualifications): List: - Bachelor’s degree in Computer Science, Software Engineering, or a related field. - Must possess an active TS/SCI clearance and Polygraph. - 10+ years of relevant experience in Agile/SAFe roles, with prior RTE or Scrum Master experience. - 5+ years as a Release Engineer or similar role. - Strong SDLC and release management knowledge. - Expertise with CI/CD tools (Jenkins, GitLab CI, Artifactory, etc.). - Experience with cloud platforms (AWS, Kubernetes) and infrastructure automation. - DevOps and automation skills for large-scale systems. - Experience as a Release Train Engineer (RTE), Chief Scrum Master, or Agile program lead. - SAFe Agile methodology proficiency. - Lean and systems thinking. - Excellent communication and facilitation skills. - Problem-solving, prioritization, and adaptability. We'll put as
  • . Skills: We could extract from qualifications: Expertise with CI/CD tools, Experience with cloud platforms, DevOps and automation skills, SAFe Agile methodology proficiency, Lean and systems thinking, Excellent communication and facilitation skills, Problem-solving, prioritization, adaptability. But these are already in qualifications; we risk duplication. The spec says preserve ALL substantive information; we can split but must not lose info. If we move some to Skills, we still need to keep them somewhere. Could keep them in Requirements and also list in Skills? That would duplicate. Better to keep qualifications as Requirements and not have a separate Skills section unless there are distinct skills not captured. However the posting includes many skill-like items; we could treat the whole list as Skills and not have Requirements. But we need to decide. Given the headings, we could put the list under Qualifications (since it's titled Required Qualifications). Then we could have Requirements empty (skip). But we need at least one of Requirements or Qualifications. Let's put the list under Qualifications. Then we could have Requirements maybe empty -> skip. But we need to include some content for Requirements? Not required; we can omit if no real specific content. The posting does not have a separate "Requirements" section besides qualifications. So we can omit Requirements heading. Thus we will have: About the role, Responsibilities, Qualifications, Skills, Benefits, Pay. Now Skills: we could extract specific skill items that are not already covered? But we risk losing info if we only put some. Better to keep all qualifications under Qualifications and not have Skills. However the spec encourages a few substantive sections over many thin ones. Having both Qualifications and Skills may be thin. So we could combine them: treat Qualifications as the list, and not have Skills. That satisfies having a section for qualifications. Thus final sections: About the role, Responsibilities, Qualifications, Benefits, Pay. Check if we have Benefits: KBR Benefits paragraph: "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". Also earlier "Belong, Connect and Grow at KBR" paragraph about Zero Harm culture etc. That's also benefits/culture. Could include that as part of Benefits or About the role? It's more about culture. Could be part of About the role? But we already have About the role covering mission etc. Might be better to include under Benefits as additional culture benefits. However the spec says Benefits section for benefits. We'll include the KBR Benefits paragraph and also the Belong, Connect and Grow paragraph as part of Benefits (since it's about culture benefits). Ensure we don't omit any. Pay: Basic Compensation "$156,400 –215,100 annum (This range is for the VA area only)" plus Additional Compensation paragraph about bonuses etc. We'll combine into Pay section. Schedule: none. Now we need to output HTML fragment only, no /. Use

    for section headings. Use

    • for lists. Use

      for prose. We must not include job title heading. Must not include Job ID etc. Remove boilerplate like EEO, etc. We must preserve all substantive information: ensure we didn't drop any details. Let's craft. About the role: combine paragraphs. We'll have maybe two

      elements. First paragraph: 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. Second paragraph: 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. Third paragraph: Who You Are KBR is looking for a motivated Agile Release Engineer to join our team and provide Systems Engineer Technical Advisor (SETA) support for the Intelligence Community Customer Ground Enterprise Directorate (GED). GED plays a critical role in enabling the Intelligence Community Customer to plan and execute intelligence-gathering missions, transforming collected data into useful information for the Intelligence Community (IC) and Department of Defense (DoD) users. In this role, you will have the chance to design, develop, test, and deliver products that support our customers’ advanced systems. In support of GED Front Office, Chief Architect, Integrated Intelligence Program Office, Advanced Ground Office, and Enterprise Data Applications and Platforms. You'll collaborate with multi-disciplinary teams focused on hardware, software, system integration, and data analysis to help achieve important missions and meet requirements. This is a contingent position based upon contract award. We need to keep the exact wording? Not required to be verbatim but preserve all info. We'll keep as is. Responsibilities:

      with each responsibility as
      • . Qualifications:
        with each qualification as
        • . Benef