Senior DevOps Platform Engineer

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements (maybe combine Required Qualifications), Benefits, Pay, Schedule. Also maybe Skills? The posting includes many responsibilities and qualifications. We must not repeat job title. No Job ID. Remove boilerplate: EEO, navigation, etc. Also remove "Additional Information" maybe includes geography, remote, internet speed, telephone equipment, work from dedicated space, travel, scheduled weekly hours, pay range, benefits, about us, equal opportunity. We need to keep substantive info: responsibilities list, required qualifications, preferred qualifications maybe as part of Requirements? The instruction: Use sections only when posting has real, specific content. So we can have sections: About the role (maybe a brief description), Responsibilities, Requirements (including required and preferred qualifications), Benefits, Pay, Schedule. Also maybe Skills? Not needed. We must preserve all substantive information; do not invent or summarize away detail. So we need to include all bullet points from responsibilities and qualifications. Must not omit any detail. Must not add filler like "commensurate with experience". Must not create sections with placeholder text. We need to format using

for section headings. Use

• for any list of duties/requirements/benefits. Use

  for prose. We need to include the pay range and schedule (Scheduled Weekly Hours 40). Also maybe mention remote geography? The Additional Information includes limited geography remote, internet speed, telephone equipment, work from dedicated space, travel. Those are substantive? They are about work arrangement. Should we include them? The instruction: Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The "Additional Information" includes geography remote, internet speed, telephone equipment, work from dedicated space, travel. Those are not boilerplate; they are job details. Should we include them? Possibly under a section like "Work Arrangement" but not listed as allowed headings. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We could put remote details under About the role or maybe under Responsibilities? Not appropriate. Could we create a new heading? The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says "e.g." meaning those are examples, but we should prefer those headings. It says "Use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we should stick to those headings; we can also use Qualifications separate from Requirements? The list includes both Requirements and Qualifications. We could have Requirements for required qualifications, and Qualifications for preferred? Or combine. But we need to include all substantive info. We could have sections: About the role (brief description), Responsibilities, Requirements (required qualifications), Qualifications (preferred qualifications), Benefits, Pay, Schedule. We must not create sections with filler text. So each heading must have real content. Now we need to extract the prose for About the role: The first paragraph: "Become a part of our caring community Humana is looking for a Senior DevOps Platform Engineer to design, implement, and support secure, compliant cloud and DevOps platforms across Azure and GCP. You will ensure enterprise-scale software delivery through modern CI/CD pipelines, Kubernetes platforms, GitOps practices, automation, and developer self-service capabilities. The engineer will provide dedicated ownership of the JFrog platform ecosystem (Artifactory, Xray, and Curation), with a focus on software supply chain security, artifact governance, vulnerability management, and regulatory compliance. As a subject matter expert for JFrog, Argo CD, SonarQube, LaunchDarkly, GitHub, and GitHub Runners, this role will drive platform modernization, security remediation, operational excellence, and developer productivity while ensuring reliable, scalable, and secure platform services across the organization. You will also partner with cybersecurity teams to support application security projects, VIT/CVIT remediation, secret management, and emerging software supply chain security capabilities." That is the About the role description. We'll put that in

  . Now Responsibilities: list bullet points under "Key Responsibilities". We'll convert each line to

  . Need to preserve all details. List: - Design, build, and maintain secure cloud infrastructure on Azure and GCP. - Develop and improve CI/CD pipelines using Azure DevOps, GitHub Actions, Harness, and GitOps practices. - Deploy and manage Kubernetes platforms (AKS, GKE, OpenShift). - Own and administer enterprise DevOps platforms including JFrog Artifactory, Xray, Curation, Argo CD, SonarQube, LaunchDarkly, GitHub, and GitHub Runner infrastructure. - Implement software supply chain security, artifact governance, dependency governance, vulnerability management, and secure software delivery practices across enterprise CI/CD ecosystems. - Provide dedicated expertise for emerging software supply chain security capabilities, including JFrog Curation and related governance controls. - Support application security initiatives, VIT/CVIT remediation efforts, secret remediation requirements, and enterprise compliance mandates. - Maintain security controls across Azure DevOps, GitHub, Build Agents, and GitHub Runner platforms that support enterprise software delivery. - Partner with security organizations to rapidly assess, prioritize, and remediate newly identified vulnerabilities impacting developer platforms and CI/CD services. - Design and support feature flag management and progressive delivery capabilities using LaunchDarkly. - Develop automation and self-service solutions using PowerShell, Bash, Python, and AI-assisted engineering tools. - Ensure HIPAA, SOC2, and regulatory compliance across DevOps platforms and processes. - Configure and support enterprise build agents and runners across Linux, Windows, and GitHub Runner environments. - Provide L3 support, incident response, root cause analysis, and on-call support for critical platform services. - Lead platform modernization initiatives while ensuring security, compliance, reliability, and operational stability are maintained. - Create engineering standards, documentation, reusable templates, and developer enablement resources while participating in Agile delivery practices. Now Requirements (required qualifications): list bullet points under "Required Qualifications". We'll preserve all. List: - 7+ years of experience in IT infrastructure, platform engineering, or operations. - 5+ years of hands-on DevOps engineering experience. - Experience designing and supporting cloud infrastructure on Azure and GCP. - Strong experience with Infrastructure as Code (Terraform). - Experience building CI/CD platforms using Azure DevOps, GitHub Actions, Harness, and GitOps practices. - Hands-on experience with Kubernetes platforms including AKS, GKE, and OpenShift. - Experience administering and supporting enterprise DevOps platforms including JFrog Artifactory, Xray, Curation, Argo CD, SonarQube, LaunchDarkly, GitHub, and GitHub Runner infrastructure. - Experience implementing software supply chain security, dependency governance, vulnerability remediation, secret management, and secure software delivery practices. - Experience supporting application security programs, VIT/CVIT remediation efforts, and enterprise compliance initiatives. - Strong Linux/Unix administration and Windows administration experience. - Advanced scripting skills in PowerShell, Bash, and Python. - Experience with GitHub Copilot, Claude Code, or similar AI-assisted development tools. - Familiarity with managing, observability, and platform reliability practices. - Experience supporting enterprise-scale DevOps platforms and developer enablement projects. - Experience operating within HIPAA, SOC2, or other regulated compliance environments. Now Preferred Qualifications: list bullet points. List: - Experience supporting large-scale enterprise DevOps platforms. - Experience leading enterprise DevOps platform modernization, onboarding, adoption, and governance initiatives. - Familiarity with DORA metrics and DevOps maturity models. - Experience integrating automated testing, security scanning, compliance controls, and software supply chain security capabilities into CI/CD pipelines. - Experience supporting healthcare technology platforms or other regulated industries. - Azure, GCP, Kubernetes, Terraform, GitHub, or related cloud certifications. - Experience with software supply chain security governance frameworks, SBOM management, and dependency governance. - Healthcare industry experience preferred. Now Benefits: The "Description Of Benefits" paragraph. We'll put that in

  under Benefits heading. Paragraph: "Humana, Inc. and its affiliated subsidiaries (collectively, “Humana”) offers competitive benefits that support whole-person well-being. Associate benefits are designed to encourage personal wellness and smart healthcare decisions for you and your family while also knowing your life extends outside of work. Among our benefits, Humana provides medical, dental and vision benefits, 401(k) retirement savings plan, time off (including paid time off, company and personal holidays, paid parental and caregiver leave), short-term and long-term disability, life insurance and many other opportunities." Now Pay: The pay range paragraph. We'll put that in

  under Pay heading. Paragraph: "The compensation range below reflects a good faith estimate of starting base pay for full time (40 hours per week) employment at the time of posting. The pay range may be higher or lower based on geographic location and individual pay will vary based on demonstrated job related skills, knowledge, experience, education, certifications, etc. $106,900 - $147,000 per year This job is eligible for a bonus incentive plan. This incentive opportunity is based upon company and/or individual performance." Now Schedule: The "Scheduled Weekly Hours 40". Also maybe mention remote? But schedule section only for hours. We'll put

  Scheduled Weekly Hours: 40.

  We also have Additional Information about remote geography, internet speed, telephone equipment, dedicated space, travel. Should we include those? They are not covered by allowed headings. Could we incorporate them into About the role or Responsibilities? Not really. The instruction says "Prefer a few substantive sections over many thin ones." It didn't forbid adding other sections, but gave examples. It said use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). That suggests we should limit to those headings. However, the remote geography etc. is substantive. Should we drop it? The instruction: "Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions." The remote geography etc. is not boilerplate; it's job details. But we have no heading for it. Could we put it under About the role as additional prose? Possibly we can add a sentence about remote work etc. within About the role paragraph. But the About the role currently is a description of the role; we could extend it to include work arrangement details. However, that might be mixing. But we can include a separate paragraph under About the role about work arrangement. The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." So we must keep the remote geography, internet speed, telephone equipment, dedicated space, travel. We need to include them somewhere. Since we don't have a specific heading for "Work Arrangement", we could add them under About the role as extra prose. Or we could create a new heading like "Work Arrangement" but that deviates from examples. The instruction says "use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The "e.g." implies those are examples, not an exhaustive list. So we could add other headings if needed. However, they said "Prefer a few substantive sections over many thin ones." Adding a Work Arrangement section would be another section, making more sections. But we could incorporate into About the role to keep sections few. Thus, we can extend About the role paragraph to include: "This is a remote position located within a specific geography. Requires minimum download speed of 25 Mbps and upload speed of 10 Mbps; Humana provides telephone equipment; employees must work from a dedicated space free of interruptions to protect PHI/HIPAA; occasional travel to offices may be required." That preserves details. Now we must ensure we don't repeat the job title.