Senior Cloud Infrastructure Engineer

We need to output HTML fragment with sections: About the role? The posting includes description about Accenture Federal Services mission, etc. We need to include sections only when there is real specific content. We should not repeat job title as heading. Use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections have content. Content: There's a mission statement paragraph about Accenture Federal Services. Could be "About the role" or maybe "About the company". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can use About the role for the introductory paragraph about the company and mission. Responsibilities: list of key responsibilities and what you'll deliver. Should be in

• . Requirements: maybe "Here's What You Need" includes years experience, degree, DoD 8140 compliance. That's requirements. Qualifications: maybe "Bonus Points If You Have" could be Qualifications or Skills. Could treat as Qualifications (preferred qualifications). Or Skills: certifications etc. Skills: maybe list of specific technical skills: Terraform, CloudFormation, Ansible, Docker, Kubernetes, Linux/Unix, etc. Could be separate. Benefits: The posting mentions "Accenture Federal Services offers a wide variety of benefits. You can find more information on benefits here." No specific benefits listed, so we should NOT create Benefits section because no specific content. So omit. Pay: There is pay range: $120,400—$234,700 USD for certain locations. Also statement about compensation varies. So we have specific pay range, so include Pay section. Schedule: No mention of schedule (full-time, etc). Not present, so omit. We also have Security Requirements: Active TS clearance required; SCI preferred. That could be part of Requirements or Qualifications. Probably Requirements. We also have "As required by local law..." about compensation ranges. That's part of Pay. We need to preserve all substantive information, not invent or summarize away detail. So we need to include all details from the posting, but we can format them. We must remove boilerplate: cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the EEO statement, accommodation request, other employment statements, etc. Also remove "We accept applications on an on-going basis..." etc. Also remove "Job Description" heading? Not needed as heading but we can keep content. We need to output only HTML fragment, no /, no markdown fences. Let's extract substantive content: - Intro paragraph: "At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. Join us to drive positive, lasting change that moves missions and the government forward!" That's about the company/role. - Job Description heading: "Accenture Federal Services is looking for a Senior Cloud Infrastructure Engineer to own infrastructure design decisions for mission-critical cloud environments. You'll set engineering direction for infrastructure-as-code, architect solutions for compute, storage, and networking at enterprise scale, and mentor the engineers building against your designs." That could be part of About the role or Responsibilities. We'll incorporate into About the role maybe. - Key Responsibilities bullet list (looks like a paragraph but actually a list separated by commas? It says: "Infrastructure design and architecture for mission-critical workloads, including compute, storage, and networking at enterprise scale Infrastructure-as-code standards and technical direction for the team's IaC practices Disaster recovery, backup, and business continuity design for supported environments Security control implementation, STIG compliance, and vulnerability remediation across owned infrastructure Root-cause resolution for complex (Tier 3) infrastructure incidents Mentorship of mid-level and junior engineers, including infrastructure-as-code review and technical standards" We'll treat each line as
• . - What You'll Deliver list: "New infrastructure delivered as reusable, version-controlled infrastructure-as-code modules rather than one-off manual configuration Enterprise-scale cloud architecture that satisfies both mission performance and security requirements Disaster recovery and business continuity solutions, validated and ready for use Faster incident resolution as root-cause investigation becomes the team norm Junior and mid-level engineers who route architecture and design questions to you because your technical judgment is trusted" Again each line as
• maybe under Responsibilities or a separate section? Could be part of Responsibilities or maybe "What You'll Deliver" is like outcomes. We could include under Responsibilities as well, but maybe better to have a separate section? The instruction only allows certain headings; we could put under Responsibilities (makes sense). Or we could add a section "Responsibilities" and include both Key Responsibilities and What You'll Deliver as list items. - Here's What You Need: "5-6+ years of cloud engineering or infrastructure experience, including hands-on production work with infrastructure-as-code (Terraform, CloudFormation, or Ansible), containerization and orchestration (Docker, Kubernetes), and Linux/Unix systems administration At least 2 years of experience mentoring or providing technical leadership to other engineers Bachelor's degree in Computer Science, Information Systems, Engineering, or a related field, or 4+ years of relevant job or military experience in lieu of degree DoD 8140 compliance (e.g., Security+, CISSP, CASP, or equivalent)" These are requirements. - Bonus Points If You Have: "Experience designing solutions for multi-classification or cross-domain environments AWS or Azure certifications (Solutions Architect level or above) Kubernetes certifications (CKA, CKAD) Experience with configuration management tools (Chef, Puppet) beyond Ansible Familiarity with National Security systems and air-gapped environments" These could be Qualifications or Skills. We'll treat as Qualifications (preferred qualifications). Or Skills: maybe list of certifications etc. We'll decide: Qualifications for required, Skills for preferred? But we have both required and preferred. The instruction says use headings like Qualifications, Skills. We can put required under Requirements, preferred under Qualifications, and maybe technical skills under Skills? However we already listed many technical skills in Requirements (Terraform etc). Could move those to Skills. But we need to preserve all info; we can duplicate? Better to categorize: Requirements: years experience, mentorship, degree, DoD 8140. Skills: specific technical skills (Terraform, CloudFormation, Ansible, Docker, Kubernetes, Linux/Unix). Qualifications: bonus points (multi-classification, certifications, etc). That seems logical. But we must not invent sections that have no content. We'll have Requirements, Skills, Qualifications. Pay: we have pay range: "$120,400—$234,700 USD". Also statement: "Compensation for roles at Accenture Federal Services varies depending on a wide array of factors, including but not limited to office location, role, skill set, and level of experience." Also "As required by local law, Accenture Federal Services provides reasonable ranges of compensation for hired roles based on labor costs in the states of California, Colorado, Hawaii, Illinois, Maine, Maryland, Massachusetts, Minnesota, New Jersey, New York, Vermont, Virginia, Washington, and the District of Columbia, and the city of Cleveland. The base pay range for this position in these locations is shown below." Then later repeats pay range. We'll include that. Security Requirements: "Active TS clearance required; SCI preferred". Could be part of Requirements or maybe a separate section? Could be under Requirements as a bullet. We'll include that in Requirements. Now we need to strip out boilerplate: EEO statement, accommodation request, other employment statements, etc. Also remove lines like "We accept applications on an on-going basis and there is no fixed deadline to apply." Also remove "Job Description" heading? Not needed. We'll produce HTML:

  About the role

  At Accenture Federal Services, nothing matters more than helping the US federal government make the nation stronger and safer and life better for people. Our 13,000+ people are united in a shared purpose to pursue the limitless potential of technology and ingenuity for clients across defense, national security, public safety, civilian, and military health organizations. Join Accenture Federal Services, a technology company within global Accenture. Recognized as a Glassdoor Top 100 Best Place to Work, we offer a collaborative and caring community where you feel like you belong and are empowered to grow, learn and thrive through hands-on experience, certifications, industry training and more. Join us to drive positive, lasting change that moves missions and the government forward! Accenture Federal Services is looking for a Senior Cloud Infrastructure Engineer to own infrastructure design decisions for mission-critical cloud environments. You'll set engineering direction for infrastructure-as-code, architect solutions for compute, storage, and networking at enterprise scale, and mentor the engineers building against your designs.

  Then Responsibilities:

  Responsibilities

  • Infrastructure design and architecture for mission-critical workloads, including compute, storage, and networking at enterprise scale
  • Infrastructure-as-code standards and technical direction for the team's IaC practices
  • Disaster recovery, backup, and business continuity design for supported environments
  • Security control implementation, STIG compliance, and vulnerability remediation across owned infrastructure
  • Root-cause resolution for complex (Tier 3) infrastructure incidents
  • Mentorship of mid-level and junior engineers, including infrastructure-as-code review and technical standards
  • New infrastructure delivered as reusable, version-controlled infrastructure-as-code modules rather than one-off manual configuration
  • Enterprise-scale cloud architecture that satisfies both mission performance and security requirements
  • Disaster recovery and business continuity solutions, validated and ready for use
  • Faster incident resolution as root-cause investigation becomes the team norm
  • Junior and mid-level engineers who route architecture and design questions to you because your technical judgment is trusted
  Requirements:

  Requirements

  • 5-6+ years of cloud engineering or infrastructure experience, including hands-on production work with infrastructure-as-code (Terraform, CloudFormation, or Ansible), containerization and orchestration (Docker, Kubernetes), and Linux/Unix systems administration
  • At least 2 years of experience mentoring or providing technical leadership to other engineers
  • Bachelor's degree in Computer Science, Information Systems, Engineering, or a related field, or 4+ years of relevant job or military experience in lieu of degree
  • DoD 8140 compliance (e.g., Security+, CISSP, CASP, or equivalent)
  • Active TS clearance required; SCI preferred
  Skills:

  Skills

  • Infrastructure-as-code: Terraform, CloudFormation, Ansible
  • Containerization and orchestration: Docker, Kubernetes
  • Linux/Unix systems administration
  Qualifications (preferred):

  Qualifications

  • Experience designing solutions for multi-classification or cross-domain environments
  • AWS or Azure certifications (Solutions Architect level or above)
  • Kubernetes certifications (CKA, CKAD)
  • Experience with configuration management tools (Chef, Puppet) beyond An