​​AWS Cloud Engineer

We need to output HTML fragment with sections: headings

for sections like 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. Must preserve all substantive info, remove boilerplate (cookie/navigation/legal/EEO/equal-opportunity/scam-warning, duplicated lines, application instructions). Also remove "If you're looking for comfort..." etc. Also remove "Original Posting September 22, 2026" etc. Also remove "For U.S. Positions: While subject to change..." etc. Also remove "About Leidos" maybe? That's not a required heading but could be considered "About the role"? Actually "About Leidos" is company description, not role. Could be omitted as boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. "About Leidos" is not explicitly prohibited but might be considered boilerplate? It's not required heading; we could include as a paragraph under maybe "About the role"? But they said use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can include "About the role" heading and put description of role there. The "About Leidos" is company overview; could be omitted as not required. But we must preserve ALL substantive information; does company overview count as substantive? Possibly yes, but they didn't list a heading for company overview. Could incorporate into "About the role" or maybe a separate section not listed? The instruction says use those headings for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)". Likely they expect only those headings. So we should map content to those sections. We need to extract: - About the role: description of role, location, hybrid remote, etc. - Responsibilities: list of primary responsibilities. - Requirements: maybe Minimum Qualifications. - Qualifications: maybe Preferred Qualifications. - Skills: maybe certifications, technical skills. - Benefits: Pay and benefits section includes description of benefits (competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement). Also Pay Range. - Pay: Pay Range. - Schedule: maybe location/hybrid remote? Not exactly schedule. Could include "Location: This position will be hybrid remote. Candidates will be required to work onsite as needed. Preferred candidates will be located near Hanscom AFB (Boston, MA) or work in Huntsville, AL." That's more about location/work arrangement, not schedule. Could treat as "Schedule" maybe? But schedule usually refers to work hours. Not present. Could omit Schedule section if no specific content. The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. So we need to check if schedule is stated. The posting does not mention work hours, shift, etc. So we should not include Schedule section. Pay: we have Pay Range $107,900.00 - $195,050.00 plus note. So include Pay section. Benefits: we have "Pay and benefits are fundamental..." and list: competitive compensation, Health and Wellness programs, Income Protection, Paid Leave and Retirement. Also reference to more details at website. So include Benefits section. Skills: we could list technical skills from responsibilities and qualifications: AWS, Azure, GCP, OCI, Infrastructure as Code, DevOps/DevSecOps, CI/CD pipelines, Linux/Unix, networking, cloud security, scripting languages (Python, Bash, Go), etc. Also certifications: CompTIA Security+ or equivalent (IAT-2). Also cloud certifications examples. Could put under Skills. Qualifications: maybe separate Minimum Qualifications and Preferred Qualifications. Could combine under Qualifications heading with sub-sections? But we have headings: Requirements, Qualifications, Skills. Could treat Minimum Qualifications as Requirements, Preferred Qualifications as Qualifications. Or Requirements as the mandatory items, Qualifications as preferred. We'll decide. Let's parse: Minimum Qualifications: - Bachelors and 8+ years or more of experience; Masters and 6+ years or more of experience. Additional experience may be accepted in lieu of degree. - Must have an active Secret clearance required to start - US citizenship required - Certifications: CompTIA Security+ or equivalent (IAT-2) - Expert-level experience designing and supporting cloud environments (AWS, Azure, GCP, or OCI). - Strong experience with Infrastructure as Code, automation, and DevOps/DevSecOps practices. - Hands-on experience with CI/CD pipelines and cloud-native application architectures. - Advanced knowledge of Linux/Unix systems, networking, and cloud security concepts. - Proficiency in one or more scripting or programming languages (e.g., Python, Bash, Go). - Excellent written and verbal communication skills. - Demonstrated experience in cloud operations and sustainment and performing tasks and actions described in the primary responsibilities section Preferred Qualifications: - Experience with USAF Cloud One or Platform 1 - Experience with Zero Trust Architecture - Excellent customer service skills, with experience working in a customer-facing position - Strong understanding Active Directory, AWS AD, SAML and the standards, procedures, and processes - Experience with Ansible, AWS console, Elastic, AWS, Jira, Confluence, Git, Bitbucket and various cloud SaaS offerings - Administration experience with cloud-based applications (MS O365, SharePoint, AWS AD, AWS) - Experience administering Windows Server, and related services - Cloud certifications in AWS, Azure, Google, or Oracle clouds (list examples) Thus we can map: Requirements (h3) -> Minimum Qualifications (as list) Qualifications (h3) -> Preferred Qualifications (as list) Skills (h3) -> Technical skills and certifications maybe overlapping; but we can still list skills like cloud platforms, IaC, CI/CD, Linux, networking, security, scripting, etc. Could also include certifications. But we must avoid duplication. Could combine skills within Responsibilities? Better to have separate Skills section listing technical competencies. Let's extract responsibilities list from "Primary Responsibilities" paragraph which is a long sentence with many items separated by line breaks? Actually the text after "Primary Responsibilities" is a continuous paragraph with many items separated by line breaks? It appears as a block with many sentences. We need to turn into

• items. We'll split by each distinct responsibility. Let's copy the responsibilities text: "Provide cloud operations and engineering tasks toenhance, sustain, andmaintainscalable, resilient, and secure cloud solutionsforAWScloudenvironmentPerformAWScloud operations, sustainment, and maintenance activities tomaintainoptimumcloud performance, security, and cloud user experienceDevelop cloud strategy and roadmaps aligned with organizationobjectivesand technical requirements Continuously evaluate emerging cloud technologiesto maximize automation and performassessments ofthe potential impact on organizationaland programgoals Drive adoption of DevOps practices, infrastructure as code, and automation frameworks Optimizeapplication performance and reliability in cloud environments Support Design,implementationand sustainment ofsecure cloud architectures implementing zero-trust principles and defense-in-depth strategies Ensure compliance with industry standards (SOC 2, HIPAA, PCI-DSS, etc.) and regulatory requirements Architect, implement andmaintaincloud networking security controls including STIG requirementsImplement identity and access management solutions and security monitoring frameworks Facilitate customer onboarding and implement a consistent pathway to cloud adoptionAssess legacy systems and design modernization strategies including containerization and microservices Support development ofmigration methodologies and ensure minimal organizational disruption during transitions Manage andoptimizecloudAWSenvironments, networking, VPNs, IaaS, PaaS, and SQL systems.Implement andmaintainCI/CD workflows and infrastructure-as-code development usingJenkins, Terraform, Ansible, Kubernetes, Jira, Confluence, Artifactory, and Guacamole to supportDevSecOpspractices.Containerize applications to enhance scalability and deployment efficiency.Support thedesign anddevelopment of Shared Services.Configure and troubleshoot cloud, virtual, and physical hardware and software systems.Establish andmaintainSQL and NoSQL databases, ensuring their performance and reliability.Prepare detailed technical documentation to support development and operational processes.Collaboratewith cross-functional teams including development, operations, security, and product management Create reference architectures, design patterns, and technical standards for cloud implementations" We need to split into sensible items. Let's manually parse: - Provide cloud operations and engineering tasks to enhance, sustain, and maintain scalable, resilient, and secure cloud solutions for AWS cloud environment - Perform AWS cloud operations, sustainment, and maintenance activities to maintain optimum cloud performance, security, and cloud user experience - Develop cloud strategy and roadmaps aligned with organization objectives and technical requirements - Continuously evaluate emerging cloud technologies to maximize automation and perform assessments of the potential impact on organizational and program goals - Drive adoption of DevOps practices, infrastructure as code, and automation frameworks - Optimize application performance and reliability in cloud environments - Support design, implementation and sustainment of secure cloud architectures implementing zero-trust principles and defense-in-depth strategies - Ensure compliance with industry standards (SOC 2, HIPAA, PCI-DSS, etc.) and regulatory requirements - Architect, implement and maintain cloud networking security controls including STIG requirements - Implement identity and access management solutions and security monitoring frameworks - Facilitate customer onboarding and implement a consistent pathway to cloud adoption - Assess legacy systems and design modernization strategies including containerization and microservices - Support development of migration methodologies and ensure minimal organizational disruption during transitions - Manage and optimize cloud AWS environments, networking, VPNs, IaaS, PaaS, and SQL systems - Implement and maintain CI/CD workflows and infrastructure-as-code development using Jenkins, Terraform, Ansible, Kubernetes, Jira, Confluence, Artifactory, and Guacamole to support DevSecOps practices - Containerize applications to enhance scalability and deployment efficiency - Support the design and development of Shared Services - Configure and troubleshoot cloud, virtual, and physical hardware and software systems - Establish and maintain SQL and NoSQL databases, ensuring their performance and reliability - Prepare detailed technical documentation to support development and operational processes - Collaborate with cross-functional teams including development, operations, security, and product management - Create reference architectures, design patterns, and technical standards for cloud implementations That seems comprehensive. Now About the role: we need to capture description: "Leidos has an opening for a AWS Cloud Engineer supporting the U.S. Air Force Cloud One Architecture and Common Shared Services (ACSS) contract. This is an exciting opportunity to apply your expertise in a large-scale, multi-cloud environment spanning AWS, Azure, Google Cloud, and Oracle Cloud while supporting a critical Air Force mission focused on improving system resiliency, security, and cost effectiveness. We are seeking someone with experience working across multiple cloud platforms. In this hands-on technical role, you will design, develop, deploy, and support scalable, cloud-native solutions while applying best practices across architecture, development, operations, and security. You will support solutions throughout the full lifecycle—from design, development, testing, and integration through production deployment, sustainment, and maintenance. This role requires a strong technical foundation and a willingness to be hands-on. You will work directly with cloud technologies to architect, build, troubleshoot, automate, and optimize solutions, while also providing technical guidance and mentorship to other engineers. Location: This position will be hybrid remote. Candidates will be required to work onsite as needed. Preferred candidates will be located near Hanscom AFB (Boston, MA) or work in Huntsville, AL." We can put that as prose under

  About the role

  with

  . Now Benefits: we have "Pay and benefits are fundamental to any career decision. That