AWS Infrastructure 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 if posting has real specific content. We need to parse the job description. Key info: - Title: Infrastructure Engineer (AWS / Terraform / EKS) (also Senior Infrastructure Engineer). But we should not repeat job title as heading. - Location: hybrid capacity in Fairfax, VA office. - About the role: description paragraphs. - Responsibilities: list of duties. - Requirements: qualifications (citizenship, clearance, degree, hybrid work, certifications, experience years, etc.) - Skills: maybe separate Required Skills and Desired Skills. - Benefits: "General Description Of Benefits" but no details given; only phrase "General Description Of Benefits" appears but no actual benefits listed. So we should not create Benefits section because no specific content. - Pay: Salary Range: $140,000-180,000 and note "Salary is commensurate with skillset..." We should include Pay section only if posting actually states them. It does state Salary Range. So include Pay. - Schedule: hybrid capacity, up to 3 business days per week onsite. That's schedule info. So include Schedule. We must not include boilerplate like EEO, etc. We need to preserve all substantive information. We need to use

• for any list of duties/requirements/benefits, and

  for prose. We need to avoid repeating job title as heading. We need to not put Job ID/requisition numbers as headings. We need to output only HTML fragment. Let's extract sections: About the role: The first paragraph(s) describing role: "Everforth ECS is seeking an Infrastructure Engineer (AWS / Terraform / EKS) to work in a hybrid capacity in our Fairfax, VA office. Everforth ECS is seeking a Senior Infrastructure Engineer (AWS / Terraform / EKS) to join a team responsible for managing and maintaining multiple network enclaves to support the DoD community. This role focuses on designing, building, and operating secure, repeatable AWS environments within a FedRAMP and ATO-governed context. The engineer will work in an environment where all deployments are infrastructure-as-code, peer-reviewed, and fully auditable. The successful candidate will combine hands-on AWS engineering depth with a strong sense of operational discipline, automation, and compliance awareness. This is not just EKS/Terraform build work; it is operational ownership across commercial and GovCloud AWS accounts for connectivity, routing, DNS, F5/load balancing, EKS, Terraform, security remediation, migrations, and stakeholder coordination." We can combine into a

  under

  About the role

  . Responsibilities: The "Duties" section includes a list after "The ideal candidate will be able to align to the following duties:" then bullet list (though not bullet but sentences). We'll convert each duty into
• . The list includes many items separated by periods. We'll split them. Let's extract duties: - Troubleshoot and support enterprise load-balancing and ingress patterns, including F5 or equivalent technologies, DNS, TLS/certificate paths, routing, and endpoint reachability. - Coordinate directly with application teams, Security, stakeholders, network owners, and program leadership to resolve connectivity, access, migration, and production readiness - Design, build, and maintain Infrastructure-as-Code using Terraform (modules, S3/DynamoDB remote state, OPA/tfsec policy integration). - Provision, upgrade, and manage EKS clusters, including namespaces, Helm-based add-ons (cert-manager, ESO, Confluent Operator), and IAM roles for service accounts. - Design, configure, and troubleshoot AWS VPC networking, including routing, TGWs, DNS, DHCP, endpoints, NACLs, and security groups. - Implement and secure microservices on EKS with proper connectivity to AWS services (S3, ECR, Secrets Manager, IAM). - Automate infrastructure deployments using GitHub Actions (or self-hosted runners), cross-account IAM role assumptions, and CI/CD policy gates. - Collaborate with security and applications teams to enforce least-privilege IAM, automate compliance evidence collection, and support RMF/ATO documentation. - Diagnose and resolve complex issues spanning containers, Kubernetes networking, and AWS layers (VPC - Zscaler - C-TIPS - SaaS endpoints). - Support observability, logging, and monitoring through integration with Elastic, ScienceLogic, or AppDynamics to meet SLA and audit requirements. - Mentor and guide junior engineers through knowledge sharing, paired engineering, and process standardization. - Evaluate and improve infrastructure design for policy compliance, resiliency, and performance tuning. - Develop and maintain SOPs and playbooks that align with program governance. - Support legacy-to-CAWS migration activities, including RabbitMQ/app-server connectivity, environment cutover support, dependency discovery, and validation of network paths across lower and production environments. - Quickly build working knowledge of inherited environments, document tribal knowledge, create diagrams/runbooks, and transfer operational context to primary and backup owners. - Operate within a formal change-control, evidence, and audit expectations, including CR support, implementation evidence, rollback planning, and post-change validation. - Other duties, as assigned. We'll include these as
• . Requirements: This could be qualifications: U.S. Citizen, Active DoD Secret clearance, Bachelor's degree or 6 years of relevant experience or high school diploma with 9+ years of relevant experience, Candidate is required to work in a hybrid capacity, with up to 3 business days per week onsite at Everforth ECS Corporate Offices, Required certifications: Active DoD 8140 IAT Level II Security+ (or higher), CLF-C02 AWS Certified Cloud Practitioner, SAA-C03 AWS Certified Solutions Architect - Associate, Experience required: 6+ years designing, implementing, securing, and maintaining AWS Cloud infrastructure (CAWS, GovCloud, or equivalent). 5 + years troubleshooting hybrid/cloud network connectivity, including VPC routing, TGW, DNS, DHCP, TLS/certificates, security groups, NACLs, endpoints, and load balancers. 5+ years of of Terraform (advanced modules, state management, policy enforcement). 5+ years' of Kubernetes networking, ingress, CoreDNS, service exposure, node/security group behavior, and connectivity between EKS workloads and AWS/external services. 5+ years of infrastructure experience related to network security. Strong networking foundation: TCP/IP, DNS, DHCP, TLS, routing, subnetting, NACLs, and endpoint connectivity. Proficient scripting/automation using Python or Bash, YAML/JSON templating, and Git-based workflows. Experience in security compliance environments (FedRAMP, FISMA, NIST 800-53) and supporting ATO documentation. Demonstrated ability to collaborate cross-functionally with Security, DevSecOps, and CI/CD teams to maintain compliant, auditable infrastructure. Strong problem-solving and decision-making capabilities, with a proven ability to weigh the relative costs and benefits of potential actions and identify the most appropriate solution. Highly developed interpersonal and oral/written communication skills, with the ability to effectively and professionally interact with a diverse set of stakeholders (from peers to end-users to executive management). We could split into Requirements (citizenship, clearance, education, hybrid work, certifications) and Skills (technical skills). But the instruction says use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can have both Requirements and Qualifications maybe overlapping. But we need to avoid thin sections. Perhaps combine Requirements and Qualifications into one section? But they are distinct headings. We could put citizenship, clearance, education, hybrid work under Requirements, and certifications under Qualifications? Or we could treat certifications as part of Qualifications. Let's decide: - Requirements: citizenship, clearance, education/experience, hybrid work expectation. - Qualifications: certifications (Security+, AWS CP, AWS SA-Assoc) plus maybe the years of experience? But years of experience are also requirements. Might be better to have Requirements include all mandatory criteria (citizenship, clearance, education/experience, hybrid, certifications, years of experience). Skills could be technical skills list (networking, scripting, etc.) and Desired Skills separate. But we have a lot of detail; we could create sections: Requirements (citizenship, clearance, education/experience, hybrid work, certifications) and Skills (technical skills: networking, scripting, compliance, etc.) and maybe Desired Skills as a subsection under Skills? However instruction says use headings for sections like Skills. We could have Skills section containing both required and desired skills as lists. But we must not create thin sections. Let's think: we have a lot of content for Responsibilities (many duties). For Requirements we have several items. For Skills we have many technical skills. For Pay we have salary range. For Schedule we have hybrid schedule. We'll produce:

  About the role

  ...

  Responsibilities

  ...

  Requirements

  ...

  Skills

  ...

  Pay

  Salary Range: $140,000-180,000 (commensurate with skillset, qualifications, experience, and educational background)

  Schedule

  Hybrid capacity: up to 3 business days per week onsite at Everforth ECS Corporate Offices in Fairfax, VA.

  We should not include Benefits because no specifics. Now we need to ensure we preserve all substantive information. Let's extract Requirements items: - U.S. Citizen. - Active DoD Secret clearance. - Bachelor's degree or 6 years of relevant experience or high school diploma with 9+ years of relevant experience. - Candidate is required to work in a hybrid capacity, with up to 3 business days per week onsite at Everforth ECS Corporate Offices. - Required certifications: - Active DoD 8140 IAT Level II Security+ (or higher). - CLF-C02 AWS Certified Cloud Practitioner. - SAA-C03 AWS Certified Solutions Architect - Associate. - Experience required: - 6+ years designing, implementing, securing, and maintaining AWS Cloud infrastructure (CAWS, GovCloud, or equivalent). - 5+ years troubleshooting hybrid/cloud network connectivity, including VPC routing, TGW, DNS, DHCP, TLS/certificates, security groups, NACLs, endpoints, and load balancers. - 5+ years of Terraform (advanced modules, state management, policy enforcement). - 5+ years of Kubernetes networking, ingress, CoreDNS, service exposure, node/security group behavior, and connectivity between EKS workloads and AWS/external services. - 5+ years of infrastructure experience related to network security. - Strong networking foundation: TCP/IP, DNS, DHCP, TLS, routing, subnetting, NACLs, and endpoint connectivity. - Proficient scripting/automation using Python or Bash, YAML/JSON templating, and Git-based workflows. - Experience in security compliance environments (FedRAMP, FISMA, NIST 800-53) and supporting ATO documentation. - Demonstrated ability to collaborate cross-functionally with Security, DevSecOps, and CI/CD teams to maintain compliant, auditable infrastructure. - Strong problem-solving and decision-making capabilities, with a proven ability to weigh the relative costs and benefits of potential actions and identify the most appropriate solution. - Highly developed interpersonal and oral/written communication skills, with the ability to effectively and professionally interact with a diverse set of stakeholders (from peers to end-users to executive management). Some of these are more skills than requirements. But we can keep them under Requirements. Skills section could