Kubernetes Engineer (Cloud Native Infrastructure & Automation)

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule as appropriate. Must not repeat job title. Must not include Job ID etc. Must include only sections with real specific content. Must not include filler like "commensurate with experience". Must preserve all substantive info. We need to parse the posting. Key content: - Company: Atlas Tech, veteran-owned IT company serving multiple DoD customers. - Role: Subject Matter Expert (SME) specializing in Kubernetes and cloud native infrastructure. - Telework up to 2 days per week; Atlas reserves right to adjust schedule. - Travel Up To - 10% - "You Will:" list of duties. - "You Have:" list of requirements. - "We’d be Impressed if You Had:" list of nice-to-have. - Education/Experience: BS Degree or combination; ability to obtain certs within 3 months: CompTIA Security+ CE, Professional Scrum Developer or Certified Scrum Developer; 3+ years dedicated hands-on experience designing, provisioning, administering production Kubernetes environments; 5+ years experience working with a wide range of IT products. - Culture: Core Values; recognized top 25 Best Places to Work; US DOL Hire Vets Gold Award. - Quotes from team members. - Equal opportunity employer etc (boilerplate to remove). - Accessibility & Accommodations (boilerplate? Might be considered boilerplate but it's specific contact info; but likely considered boilerplate? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The accessibility section might be considered legal/EEO? It's about accommodations; could be considered boilerplate but it's specific contact. Might be safer to remove as it's likely boilerplate. The instruction says remove EEO/equal-opportunity/scam-warning boilerplate. Accessibility & Accommodations is related to ADA, could be considered legal boilerplate. Safer to remove. - Salary/benefits: "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." This is vague but mentions competitive salary and generous benefits package. It's not specific numbers, but it's still substantive? The instruction: 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. Here they state competitive salary, generous benefits package. That's somewhat vague but still states they exist. Should we include Benefits and Pay sections? The posting says "competitive salary, generous benefits package". That's not specific numbers but it's stating they exist. The instruction says never create Pay/Schedule/Benefits sections unless the posting actually states them. It does state them (competitive salary, generous benefits). So we can include Benefits and Pay sections, but we must not include filler like "commensurate with experience". However "competitive salary" is somewhat vague but not placeholder like "varies". It's okay. Schedule: Telework up to 2 days per week; Atlas reserves right to adjust schedule. That's specific enough for Schedule section. Travel: Travel Up To - 10%: could be part of Schedule or maybe a separate bullet? Not a heading; we can include under Schedule or maybe a separate "Travel" but not required headings. We'll include under Schedule. Now we need sections: About the role (maybe a brief paragraph summarizing role). Responsibilities (You Will). Requirements (You Have). Qualifications (maybe Education/Experience and certifications). Skills (maybe technical skills list). Benefits (competitive salary, generous benefits package, opportunity to make impact, culture awards). Pay (competitive salary). Schedule (telework up to 2 days per week, travel up to 10%). Could combine Pay and Benefits? But we need separate headings only if content exists. We must not repeat job title as heading. So no heading for "Subject Matter Expert (SME)". We need to use

for section headings. We need

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

  for prose. We must preserve ALL substantive information; do not invent or summarize away detail. We must not include duplicated lines. We need to include the quotes from team members? They are substantive; we should preserve them. They are prose; we can put them in

  maybe as blockquote? Not required but we can just put them in

  . We must not include boilerplate like equal opportunity, accessibility, etc. We must not include application instructions (like "Want to hear more? Read on to see what our Team Members say...") Actually that line is part of the posting but not an instruction to apply; it's encouraging to read on. It's not application instruction. We can keep it as prose. We must not include duplicated lines. Let's extract sections. About the role: Could be first paragraph: "Looking for a career where hard work is valued, and your ideas and feedback are part of the way we operate daily? Want to bring your skills to a company that encourages teamwork and champions continued education and process improvement? Atlas Tech, a veteran-owned IT company serving multiple DoD customers in support of America's warfighters, is seeking an experienced Subject Matter Expert (SME) specializing in Kubernetes and cloud native infrastructure. The ideal candidate will bring deep hands on knowledge of container orchestration, cluster operations, automation frameworks, and modern DevOps practices. Experience with multi cluster environments, service mesh, and cloud provider Kubernetes platforms is highly valuable. This role focuses on designing, implementing, and optimizing enterprise grade Kubernetes environments to drive scalability, reliability, and operational excellence." That's substantive. Responsibilities: The "You Will:" list. We need to convert each bullet into

• . List: - Serve as the primary technical authority for Kubernetes strategy, operations, and best practices. - Architect, deploy, and manage Kubernetes clusters across bare-metal, virtualized, and multi-cloud environments. - Leverage GitOps delivery pipelines using Argo CD (or Flux) to automate infrastructure state, cluster add-ons, and workload deployments across multi-cluster environments. - Configure, tune, and troubleshoot cluster networking, including Container Network Interfaces, ingress controllers and service mesh architectures. - Build and optimize enhance monitoring, logging, and tracing frameworks to ensure cluster reliability and workload visibility. (Note: phrase "Build and optimize enhance" seems typo; we keep as is.) - Troubleshoot complex cluster issues, including networking, scheduling, performance tuning, and node health. - Collaborate with application teams to onboard workloads, design deployment patterns, and optimize resource usage. - Drive documentation, standards, and reusable automation templates for repeatability across environments. - Provide knowledge transfer, training, and mentorship to junior engineers and cross functional teams. Requirements: "You Have:" list. - Must be a US Citizen. - Must currently possess and maintain a Department of Defense (DoD) Secret Level Security Clearance. - Extensive hands-on Kubernetes experience, including cluster operations, workload deployment, and infrastructure components. - Familiarity with cloud platforms providing managed Kubernetes (AKS, EKS, GKE). - Excellent communication and documentation skills. - Solid understanding of containers and container build processes (Docker, Podman, Buildah, etc.). - Strong troubleshooting skills for cluster networking, storage, and control plane issues. - Experience with service mesh technologies (Istio, Linkerd) or ingress controllers (NGINX, HAProxy, Traefik) - Experience with Helm charts, Kustomize, and Kubernetes Operators templating/packaging mechanism. - Knowledge of Kubernetes security tooling (OPA/Gatekeeper, Kyverno, Falco). - Strong skills with automation tooling (Ansible, Terraform, or similar). - Proficiency with Git, Jenkins, YAML, CI/CD pipelines, and DevOps workflows. - Familiarity with DoD/DoW compliance automation (DISA STIGs, SCAP, RMF) - Strong communication skills with the ability to explain complex concepts clearly (duplicate of communication? but we keep.) Qualifications: Education/Experience and certifications. - Education/Experience: BS Degree in relevant technical field or combination of education and experience - Ability to obtain the following certs within 3 months of start date: CompTIA Security+ CE, Professional Scrum Developer certification or Certified Scrum Developer certification - 3+ years of dedicated, hands-on experience designing, provisioning, and administering production Kubernetes environments. - 5+ years experience working with a wide range of IT products We could also include certifications nice-to-have under "We’d be Impressed if You Had:" as Qualifications or Skills? Could be under Qualifications as "Preferred". But we have a section for Qualifications; we can include both required and preferred? The instruction: Prefer a few substantive sections over many thin ones. We could combine Requirements and Qualifications into one? But we have separate headings allowed. We'll keep Requirements (mandatory) and Qualifications (education/experience/certs). Skills could be technical skills list (maybe from Requirements). But we already have many technical items in Requirements. Could create Skills section for things like "Kubernetes, Docker, Helm, etc." but that would duplicate. Better to keep Requirements as the list of must-haves, and Qualifications as education/experience/certs. Skills maybe not needed. Benefits: "Atlas Tech offers a competitive salary, generous benefits package, and an opportunity to make a positive impact in your own community." Also culture awards: recognized top 25 Best Places to Work, US DOL Hire Vets Gold Award. Also core values: Learning; Teaching; Passion; Flexibility. Also quotes from team members. We can put Benefits section with bullet list: - Competitive salary - Generous benefits package - Opportunity to make a positive impact in your community - Recognized as a top 25 Best Places to Work in South Carolina and Virginia for three straight years - US DOL Hire Vets Gold Award recipient since 2020 - Core values: Learning, Teaching, Passion, Flexibility - Employee testimonials (quotes) Pay: Could be just "Competitive salary" but we already have that in Benefits. To avoid duplication, we could put Pay section with "Competitive salary" and Benefits section with other benefits. But the instruction says prefer few substantive sections over many thin ones. Having both Pay and Benefits might be thin. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state competitive salary and generous benefits package. Could combine into Benefits section and omit Pay. But they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state them, but we could still choose to not create a Pay section if we feel it's redundant. The instruction: "Prefer a few substantive sections over many thin ones." So we should avoid creating a Pay section if we can incorporate that info into Benefits. So we will have Benefits section that includes competitive salary, generous benefits package, etc. Schedule: Telework up to 2 days per week; Atlas reserves right to adjust schedule. Travel Up To - 10%. We can put Schedule section with bullet: - Telework up to 2 days per week (subject to adjustment per customer needs) - Travel up to 10% Now About the role: we already have a paragraph. Now we need to ensure we don't repeat any content. Let's craft HTML. We'll start with

  About the role

  then

  ...

  Then

  Responsibilities

  • ...
  ...
  Then

  Requirements

  ...
  Then

  Qualifications

  ...
  Then

  Benefits

  ...
  Then

  Schedule

  ...
  We might also include