Associate AWS DevOps Engineer

We need to output HTML fragment with sections: About the role? The posting includes "Position Overview" and "Key Responsibilities", "Required Qualifications", "Preferred Qualifications", "Role Scope and Development", "Why Join KBR", "Special Requirements", "KBR Benefits". Also "AWS Certification Requirement". Need to decide which sections to include based on content. We must use

for section headings (e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). 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 a short

  or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a 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 the posting actually states them. Prefer a few substantive sections over many thin ones. We need to decide which sections to output. Likely sections: About the role (Position Overview), Responsibilities (Key Responsibilities), Requirements (Required Qualifications), Qualifications (Preferred Qualifications maybe), Benefits (KBR Benefits). Also maybe "AWS Certification Requirement" could be part of Requirements. "Role Scope and Development" maybe part of About the role or separate? Could be a section like "Role Scope". But we should prefer few substantive sections. We need to include all substantive info. So we need to capture everything: Position Overview, Key Responsibilities, Required Qualifications, Preferred Qualifications, AWS Certification Requirement, Role Scope and Development, Why Join KBR, Special Requirements, KBR Benefits. We can combine some: maybe "About the role" includes Position Overview + Role Scope and Development + Why Join KBR? But we need to preserve all info; we can put them in paragraphs under that heading. But the instruction: "Prefer a few substantive sections over many thin ones." So we can have sections: About the role, Responsibilities, Requirements, Benefits. Possibly also "Qualifications" separate from Requirements? The list of allowed headings includes Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could have Requirements (covers required qualifications) and Qualifications (covers preferred qualifications + AWS cert). Or we could combine required and preferred into Requirements. But we need to preserve all info; we can split. Let's decide: -

  About the role

  : include Position Overview paragraph, Role Scope and Development paragraph, Why Join KBR paragraph, Special Requirements paragraph (US citizenship, background check). Also maybe mention belonging etc? The intro "BELONG. CONNECT. GROW." is tagline; we can include as part of About the role. -

  Responsibilities

  : list of Key Responsibilities as
  • items. -

    Requirements

    : Required Qualifications as
    • items (or paragraphs). Could also include AWS Certification Requirement as part of Requirements. -

      Qualifications

      : Preferred Qualifications as
      • items. -

        Benefits

        : KBR Benefits paragraph. We must not include Pay or Schedule sections because not stated. We must not include duplicate lines. Ensure we preserve all substantive info. We need to extract details. Let's rewrite content. Position Overview: "KBR is seeking an Associate AWS DevOps Engineer to support the development, automation, security, and operation of AWS environments for mission-critical customer workloads. This hands-on, early-career position will work with experienced cloud, DevOps, architecture, cybersecurity, application, and infrastructure teams. Under technical guidance, the engineer will support cloud modernization and develop expertise in AWS, Infrastructure as Code, continuous integration and delivery, containers, security, observability, FinOps, and AI-assisted engineering." Role Scope and Development: "Senior engineers will provide mentoring, design review, and production-change oversight. The Associate AWS DevOps Engineer will contribute to cloud migrations, production operations, compliance activities, incident response, and disaster-recovery planning while progressively assuming more complex responsibilities. This position is not expected to independently own enterprise cloud architecture, FedRAMP compliance, production incident command, disaster-recovery architecture, or large-scale cloud migrations." Why Join KBR: "KBR delivers science, technology, and engineering solutions supporting important national missions. This position provides hands-on experience with modern cloud technologies and opportunities to develop advanced AWS and DevOps skills while working with experienced engineers, architects, cybersecurity professionals, and application teams." Special Requirements: "U.S. Citizenship required. The candidate must be able to obtain and maintain a national agency check and background investigation after hiring to obtain a badge for government facility access and user account. Experience and/or Education in lieu of these qualifications will be reviewed for applicability to meet these requirements." 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. Click here to learn more: KBR Benefits | KBR 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. KBR is an equal opportunity employer. All qualified applicants will receive consideration for employment without regard to race, color, religion, disability, sex, sexual orientation, gender identity or expression, age, national origin, veteran status, genetic information, union status and/or beliefs, or any other characteristic protected by federal, state, or local law." We need to remove EEO boilerplate? The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate. So we should strip the EEO statement at the end of KBR Benefits. Also remove "Click here to learn more: KBR Benefits | KBR Belong, Connect and Grow at KBR". That's likely navigation/link. Also remove the repeated "At KBR, we are passionate about our people and our Zero Harm culture..." maybe that's not boilerplate? It's part of benefits description but could be considered fluff. However it's substantive? It's about culture; maybe keep but it's not required. The instruction says remove EEO/equal-opportunity boilerplate. The rest about Zero Harm culture might be considered boilerplate? Not sure. Safer to keep only the benefits list and maybe the sentence about career advancement. Remove the rest. Thus Benefits section: "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." Now Required Qualifications: list items: - Bachelor’s degree in Computer Science, Information Technology, Engineering, Mathematics, or a related technical field, or an equivalent combination of education and relevant experience. - At least two years of relevant experience in cloud engineering, DevOps, platform engineering, systems administration, software development, infrastructure automation, cybersecurity engineering, or a related field. Internships, cooperative education, military technical experience, and comparable applied engineering experience may count toward the experience requirement. - Hands-on experience with AWS cloud services. - Experience with at least one Infrastructure as Code technology, such as Terraform, AWS Cloud Development Kit, or AWS CloudFormation. - Experience with a scripting or programming language such as Python, Bash, PowerShell, Java, Go, or JavaScript. - Experience with Linux administration, command-line tools, scripting, or troubleshooting. - Familiarity with: Git and source-code management. Continuous integration and continuous delivery. Docker, Kubernetes, Amazon EKS, Amazon ECS, or another container platform. Cloud networking, identity and access management, encryption, logging, monitoring, and security practices. - Ability to troubleshoot technical problems, document findings, and appropriately escalate complex issues. - Strong collaboration, written communication, and verbal communication skills. - Ability and willingness to learn new AWS services, DevOps tools, security controls, and automation technologies. - U.S. citizenship is required due to customer and contract requirements. Employment is contingent upon verification of citizenship and satisfaction of applicable customer, facility-access, background-investigation, and contract eligibility requirements. - AWS Certification Requirement: The Candidate Must Hold One Of The Following Active Certifications At The Time Of Hire Or Obtain One Within Six Months: AWS Certified Solutions Architect – Associate, AWS Certified Developer – Associate, AWS Certified CloudOps Engineer – Associate, AWS Certified Data Engineer – Associate, AWS Certified Machine Learning Engineer – Associate. The AWS Certified Cloud Practitioner certification does not satisfy this requirement. We could split AWS cert into its own bullet. Preferred Qualifications: - Experience supporting AWS environments through professional employment, an internship, cooperative education, military service, an academic project, or another applied engineering setting. - Experience with tools such as GitLab, GitLab Runners, Ansible, Helm, ArgoCD, or Flux. - Familiarity with FedRAMP, FISMA, NIST Special Publication 800-53, or a comparable security framework. - Familiarity with cloud observability, vulnerability management, incident response, backup and recovery, or FinOps. - Experience using approved Generative AI tools for engineering, scripting, testing, documentation, or troubleshooting. Now Responsibilities list: need to capture each bullet from Key Responsibilities. Let's extract: - Deploy, configure, maintain, monitor, and troubleshoot AWS cloud environments. - Support application and infrastructure migration and modernization. - Develop and maintain Infrastructure as Code using Terraform, AWS Cloud Development Kit, AWS CloudFormation, or comparable tools. - Create automation using Python, Bash, PowerShell, Go, Rust, or similar languages. - Build and maintain continuous integration and delivery pipelines using GitLab, GitLab Runners, GitHub Actions, or comparable platforms. - Automate build, testing, security scanning, artifact management, deployment, validation, promotion, and rollback processes. - Support containerized workloads using Docker, Kubernetes, Amazon EKS, Amazon ECS, Helm, and applicable GitOps tools. - Apply security practices covering identity and access management, encryption, secrets, vulnerabilities, logging, auditing, and least-privilege access. - Support environments subject to applicable FedRAMP, FISMA, NIST, customer, and contract security requirements. - Assist with compliance documentation, evidence collection, remediation, and continuous monitoring. - Maintain monitoring, alerting, dashboards, runbooks, backups, recovery processes, and service-health checks. - Troubleshoot cloud infrastructure, Linux, networking, pipelines, containers, and application deployments, escalating complex issues when appropriate. - Apply FinOps practices such as tagging, cost monitoring, rightsizing, scheduling, storage optimization, and identifying unused resources. - Maintain technical documentation, diagrams, configuration records, and operating procedures. - Participate in technical reviews, code reviews, Agile planning, incident response, knowledge sharing, and continuous improvement. - Use approved Generative AI tools for documentation, scripting, testing, troubleshooting, and automation in accordance with security and responsible-use requirements. Now About the role section: combine Position Overview, Role Scope and Development, Why Join KBR, Special Requirements (maybe separate). But we already have Special Requirements as part of Requirements? Actually citizenship is also in Required Qualifications. So we could keep citizenship there and not duplicate. Special Requirements also includes background check etc. That is also in Required Qualifications (employment contingent upon verification...). So we can