Senior DevOps Platform Engineer
for each heading. Use - for any list of duties/requirements/benefits. Use
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content.
We need to parse the posting.
Key sections:
- 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's prose.
- Responsibilities: List of bullet points under "Key Responsibilities". We need to extract each bullet.
Let's list them:
- 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.
These are responsibilities.
- Required Qualifications: list under "Required Qualifications". Let's extract bullet points.
From text:
"Use your skills to make an impact Experience 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."
We can treat each line as bullet.
- Preferred Qualifications: list under "Preferred Qualifications". Extract bullet points.
"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."
We can include as bullet list under "Preferred Qualifications". However the instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications as a separate heading; we could fold into Requirements or Qualifications. Probably we can combine Required and Preferred under "Requirements" or "Qualifications". But they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections if content exists. We have Required Qualifications and Preferred Qualifications. Could put Required under "Requirements" and Preferred under "Qualifications". Or we could merge. Let's do: Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). That matches headings.
- Skills: Not explicitly listed as separate; but we could extract skills from responsibilities/qualifications. However we should only create a Skills section if posting has real specific content for it. The posting does not have a dedicated "Skills" section; but we could infer from qualifications. However instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Since there is no explicit Skills heading, we should not create a Skills section. We could omit.
- Benefits: There's "Description Of Benefits" paragraph. So we need Benefits section with that prose.
- Pay: There's "Pay Range" with $106,900 - $147,000 per year, plus bonus eligibility. So we need Pay section with that info.
- Schedule: There's "Scheduled Weekly Hours 40". Also maybe mention remote etc. So we need Schedule section with that.
- Additional Information: includes geography remote, internet speed requirements, telephone equipment, work space, travel. This could be part of Schedule? Not exactly. Could be part of "Additional Information" but not a listed heading. We could incorporate into Schedule or maybe a separate section like "Additional Info" but not allowed headings. Probably we can fold minor metadata into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph under maybe "About the role" or separate? Probably we can add a short paragraph after About the role covering remote geography etc. But we need to preserve all substantive information. The remote geography, internet speed, telephone equipment, dedicated space, travel are substantive. We could put them under a section like "Additional Information" but not a standard heading. Since not in allowed list, we should fold into maybe a
under About the role or maybe under Responsibilities? Better to add a
after About the role before Responsibilities, maybe as a short paragraph. The instruction says fold minor metadata into a short
or drop it. This is not minor? It's about remote work requirements. Could be considered minor metadata. We'll include a short
after About the role.
Now we need to output HTML fragment only, no /, no markdown fences.
Structure:
About the role
...
Remote position ... (metadata)
Responsibilities
- ...
...
Requirements
- ...
...
Qualifications
- ...
...
Benefits
...
Pay
...
Schedule
...
We must ensure we don't include empty sections. All have content.
Now craft the content.
About the role paragraph: combine the first paragraph.
Let's write:
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.
Now metadata paragraph: maybe:
This is a remote position located within a specific geography. Employees must have a self‑provided internet connection of at least 25 Mbps download and 10 Mbps upload (wired cable, DSL, or wireless recommended). Humana will provide appropriate telephone equipment. Work must be performed from a dedicated space free of ongoing interruptions to protect member PHI/HIPAA information, and occasional travel to Humana offices may be required for training or meetings.
Now Responsibilities list: each bullet as - .
Now Requirements list: from Required Qualifications.
Now Qualifications list: from Preferred Qualifications.
Now Benefits paragraph: from Description Of Benefits.
Let's copy that 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 paragraph: include pay range and bonus eligibility.
"The compensation range reflects a good faith estimate of starting base pay for full‑time (40 hours per week) employment: $106,900 – $147,000 per year. This job is eligible for a bonus incentive plan based on company and/or individual performance."
Now Schedule paragraph: "Scheduled weekly hours: 40 (full‑time)."
Now ensure we didn't include any boilerplate like Equal Opportunity Employer, About Us, etc. We removed those.
Now output HTML.
Check for any stray text like
for prose. Do not repeat job title as heading. Do not include Job ID etc. Remove boilerplate. Include only sections with real specific content. We need to parse the posting. Key sections: - 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's prose. - Responsibilities: List of bullet points under "Key Responsibilities". We need to extract each bullet. Let's list them: - 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. These are responsibilities. - Required Qualifications: list under "Required Qualifications". Let's extract bullet points. From text: "Use your skills to make an impact Experience 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." We can treat each line as bullet. - Preferred Qualifications: list under "Preferred Qualifications". Extract bullet points. "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." We can include as bullet list under "Preferred Qualifications". However the instruction says we can have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. They didn't list Preferred Qualifications as a separate heading; we could fold into Requirements or Qualifications. Probably we can combine Required and Preferred under "Requirements" or "Qualifications". But they said "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." So we can have both Requirements and Qualifications sections if content exists. We have Required Qualifications and Preferred Qualifications. Could put Required under "Requirements" and Preferred under "Qualifications". Or we could merge. Let's do: Requirements (Required Qualifications) and Qualifications (Preferred Qualifications). That matches headings. - Skills: Not explicitly listed as separate; but we could extract skills from responsibilities/qualifications. However we should only create a Skills section if posting has real specific content for it. The posting does not have a dedicated "Skills" section; but we could infer from qualifications. However instruction: "include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text". Since there is no explicit Skills heading, we should not create a Skills section. We could omit. - Benefits: There's "Description Of Benefits" paragraph. So we need Benefits section with that prose. - Pay: There's "Pay Range" with $106,900 - $147,000 per year, plus bonus eligibility. So we need Pay section with that info. - Schedule: There's "Scheduled Weekly Hours 40". Also maybe mention remote etc. So we need Schedule section with that. - Additional Information: includes geography remote, internet speed requirements, telephone equipment, work space, travel. This could be part of Schedule? Not exactly. Could be part of "Additional Information" but not a listed heading. We could incorporate into Schedule or maybe a separate section like "Additional Info" but not allowed headings. Probably we can fold minor metadata into a short
or drop it. The instruction: "Do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it." So we can include a short paragraph under maybe "About the role" or separate? Probably we can add a short paragraph after About the role covering remote geography etc. But we need to preserve all substantive information. The remote geography, internet speed, telephone equipment, dedicated space, travel are substantive. We could put them under a section like "Additional Information" but not a standard heading. Since not in allowed list, we should fold into maybe a
under About the role or maybe under Responsibilities? Better to add a
after About the role before Responsibilities, maybe as a short paragraph. The instruction says fold minor metadata into a short
or drop it. This is not minor? It's about remote work requirements. Could be considered minor metadata. We'll include a short
after About the role. Now we need to output HTML fragment only, no /, no markdown fences. Structure:
About the role
...
Remote position ... (metadata)
Responsibilities
- ... ...
Requirements
- ... ...
Qualifications
- ... ...
Benefits
...
Pay
...
Schedule
...
We must ensure we don't include empty sections. All have content. Now craft the content. About the role paragraph: combine the first paragraph. Let's write: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.
Now metadata paragraph: maybe:This is a remote position located within a specific geography. Employees must have a self‑provided internet connection of at least 25 Mbps download and 10 Mbps upload (wired cable, DSL, or wireless recommended). Humana will provide appropriate telephone equipment. Work must be performed from a dedicated space free of ongoing interruptions to protect member PHI/HIPAA information, and occasional travel to Humana offices may be required for training or meetings.
Now Responsibilities list: each bullet as