Cloud Infrastructure Engineer

We need to output HTML fragment with sections: headings

for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule etc. We must only include sections that have real specific content. We need to parse the job posting. We have: - Position Overview: description about role. Could be "About the role" section. - On-Site Requirement: location requirement. Could be part of "About the role" or separate? Not a heading we need unless we have content. Could be part of "About the role". - Key Responsibilities: list of duties. That's a "Responsibilities" section. - Basic Qualifications: list of qualifications. That's "Requirements" or "Qualifications". The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have "Requirements" for basic qualifications, maybe also "Qualifications" for preferred? But we need to avoid duplication. Could combine basic and preferred under "Qualifications". However they said prefer few substantive sections over many thin ones. So we could have "Requirements" (basic qualifications) and maybe "Preferred Qualifications" as part of same? But we could just have "Requirements" covering both basic and preferred? But they'd be separate content. Might be okay to have "Requirements" for basic, and "Preferred Qualifications" as a subsection? But headings only allowed those listed; we cannot create custom headings like "Preferred Qualifications". So we could put preferred qualifications under "Qualifications" heading. Then we have both basic and preferred under that? Might be confusing. Better: Use "Requirements" for basic qualifications, and "Qualifications" for preferred qualifications. That's two sections, both substantive. - Skills: maybe we can extract skills from responsibilities? But we have explicit skill mentions: Experience with IaC, containerization, DevSecOps, etc. Could be under "Skills". But we already have qualifications covering experience. Might be thin. The instruction: prefer few substantive sections over many thin ones. So maybe we combine skills into Responsibilities or Qualifications. But we need to follow headings list; we can omit Skills if not substantive. - Benefits: The posting mentions "Pay and benefits are fundamental..." then lists benefits: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. Also mentions more details at website. So we have benefits content. So we should include a Benefits section. - Pay: The posting includes Pay Range $107,900.00 - $195,050.00. So we need a Pay section. - Schedule: Not mentioned besides on-site requirement. No schedule details like full-time, shift. So we should not create Schedule section. - About Leidos: company description. Could be part of About the role? But we have "About Leidos" separate. Could be a section "About the role"? Actually About the role is about the position, not company. The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have About the role (position overview). The company description "About Leidos" is not required; could be omitted as boilerplate? It's not navigation/legal but it's about company. Might be considered substantive? But we might omit to keep sections few. However we need to preserve ALL substantive information; do not invent or summarize away detail. The company description is substantive? It's generic but still info. However we could incorporate into About the role? Might be okay to add a short paragraph about Leidos under About the role? But the instruction says About the role heading for section headings (e.g. About the role, Responsibilities...). So we can put position overview and maybe company description under About the role? Might be okay. But we must not repeat the job title as a heading. The page already shows it. So we don't add a heading for "Cloud Infrastructure Engineer". Good. We must not put Job ID/requisition numbers as headings. There's none visible. We must remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. So we need to strip out the scam warning, commitment to non-discribution, etc. Also remove "Original Posting September 15, 2026", "For U.S. Positions: While subject to change..." etc. Also remove "Pay And Benefits" heading? We'll create our own Benefits and Pay sections. We must preserve all substantive information: position overview, on-site requirement, responsibilities, basic qualifications, preferred qualifications, pay range, benefits description. We need to output only HTML fragment, no /, no markdown fences. Thus produce something like:

About the role

Leidos has an exciting career opportunity for a Cloud Infrastructure Engineer to support the Integrated Defensive Cyber System (IDCS) Cloud Team at Joint Base San Antonio, TX. This position offers the opportunity to work on a high-visibility, enterprise program at the intersection of data, analytics, and emerging AI technologies. Ideal candidates are motivated by mission impact, comfortable operating in complex stakeholder environments, and interested in building deep domain expertise while delivering capabilities with real-world national security outcomes. On-site presence is required at Joint Base San Antonio, TX.

Responsibilities

• Implement, operate, maintain, and optimize cloud infrastructure environments (e.g., AWS, Azure, or GCP) supporting services.
• Provide operational system administration and deployment support across AWS and Microsoft Azure GovCloud platforms.
• Configure, test, and implement native, COTS, FOSS, and custom capabilities within AWS and Azure GovCloud and on-premises cloud environments.
• Manage compute, storage, networking, and platform services across multi-enclave cloud environments.
• Implement and maintain Infrastructure-as-Code (IaC) and automation for cloud provisioning and configuration management.
• Support DevSecOps pipelines by enabling automated deployment, integration, and monitoring of cloud-based applications.
• Monitor system performance, availability, and reliability; implement improvements to optimize operations.
• Perform system administration tasks including patching, upgrades, configuration management, and troubleshooting.
• Ensure compliance with NIST SP 800-53, RMF, STIGs, and DoD cybersecurity policies.
• Support asset management, backup, disaster recovery, and continuity of operations (COOP) processes.
• Identify and resolve operational issues impacting system performance, scalability, and availability.
• Collaborate with DevSecOps, cybersecurity, data engineering, and system development teams to support integrated delivery.
• Support incident response and operational troubleshooting activities.
• Develop and maintain operational documentation, runbooks, and standard operating procedures.
• Participate in SAFe ceremonies including PI Planning, backlog refinement, sprint reviews, and retrospectives.

Requirements

• BS and 8+ years of prior relevant experience or Masters with 6+ years of prior relevant experience; additional years of experience accepted in lieu of a degree.
• Active DoD Secret clearance with DoD Top Secret SCI eligibility.
• Experience operating, maintaining, and securing GovCloud environments (AWS, Azure, or GCP).
• Minimum of 5 years of experience in DevOps engineering or related field.
• 3 years of GovCloud operations experience.
• At least one of the following foundational qualification pathways consistent with DoD 8140 requirements: current DoD 8570/8140 baseline certification appropriate for Intermediate System Administrator roles (e.g., Security+ CE, GSEC, SSCP, or equivalent), offerings listed in the DoD 8140 Training Repository, or demonstrated equivalent training and experience qualifying under DoD 8140 foundational qualification alternatives.
• Cloud certification (AWS Certified Solutions Architect - Associate, Azure Administrator - Associate, or Google Cloud Engineer, for example).
• Experience performing system administration in secure DoD or Federal environments.
• Experience implementing Infrastructure-as-Code (IaC) tools (e.g., Terraform, CloudFormation, or similar).
• Experience working with containerized environments (Docker, Kubernetes).
• Experience supporting DevSecOps pipelines and automated deployment workflows.
• Experience applying RMF, STIGs, and DoD cybersecurity requirements.
• Strong problem-solving skills and ability to conduct root cause analysis.
• Strong communication and collaboration skills.
• Experience developing and deploying systems via Infrastructure as Code.
• Experience deploying automated solutions to manage large scale systems.
• Experience horizontally and vertically scaling infrastructure with respect to application layer.

Qualifications

• Relevant DoD and/or Industry work experience.
• Active DoD Top Secret clearance preferred.
• Advanced cloud certification (AWS Certified Solutions Architect, AWS Certified DevOps Engineer, Azure Solutions Architect Expert, Azure DevOps Engineer Expert, or Google Cloud Professional DevOps Engineer, for example).

Benefits

• Competitive compensation
• Health and Wellness programs
• Income Protection
• Paid Leave
• Retirement benefits

Pay

Pay Range: $107,900.00 - $195,050.00 (Leidos pay range for this job level is a general guideline only and not a guarantee of compensation or salary).

We must ensure we didn't include any boilerplate like "Original Posting..." etc. Also we omitted the "About Leidos" company description. That's okay; we might be losing some substantive info but it's generic. The instruction says preserve ALL substantive information; but is company description substantive? It's not specific to the job; it's generic boilerplate about the company. Might be considered boilerplate. The instruction says remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Company description is not listed but could be considered boilerplate. However it's not navigation/legal etc. It's about the company. Might be considered substantive? The instruction says "Preserve ALL substantive information; do NOT invent or summarize away detail." The company description is detail but not specific to the role. It's still info about employer. Might be considered substantive. However we have limited sections; we could add an "About Leidos" paragraph under About the role or as a separate section? There's no heading for About the company in the list. Could we incorporate it into About the role? The About the role section is supposed to be about the role, but we could add a sentence about Leidos after the role description. That would preserve the info without a new heading. Let's add a sentence: "Leidos is an industry and technology leader serving government and commercial customers with smarter, more efficient digital and mission innovations. Headquartered in Reston, Virginia, with 47,000 global employees, Leidos reported annual revenues of approximately $16.7 billion for the fiscal year ended January 3, 2025." That would be substantive. Thus modify About the role paragraph to include that. Now check for any other substantive info: "Step 10 is ancient history..." etc is marketing fluff; could be considered boilerplate? It's not navigation/legal but it's fluff. Might be considered not substantive. We can omit. Also "If you're looking for comfort, keep scrolling..." etc is marketing fluff; omit. Also "For U.S. Positions: While subject to change..." is about posting duration; could be considered substantive? It's about