Senior Azure Kubernetes Engineer
Cognizant · Salem, OR
$113,000–$130,000from the description
Jul 16, 2026
Salem, OR
Jul 21, 2026
What this job asks for AI summary
This role centers on designing, running, and maintaining Azure Kubernetes Service clusters that host healthcare payer workloads, specifically TriZetto QNXT. Day-to-day work spans cluster provisioning, namespace and node pool management, autoscaling, security controls, and observability, alongside Infrastructure as Code authoring and support for containerized .NET applications and SQL Server. It suits an experienced Kubernetes operator with a production AKS background.
Senior level · 5+ years · Remote · Full-time
“or” means any one of them counts — you don't need all of them.
Posted 33 times — it's one opening, so apply once.
We read this from the posting text with AI. Skim the description below before ruling yourself out.
How this req sits in the market our data
Roughly 6,200 people nationally plausibly meet what this posting asks for (software developers). range 3,700–9,200
Applicant volume Moderate — A normal amount of company. The rare requirements below are what will separate a shortlisted application from the rest.
Rare in this occupation — lead with these, and say what you built with them.
What the occupation pays Median $138,970 (middle half $107,524–$175,762). This posting is about at that midpoint.
Estimated from BLS employment for this occupation and area, per-skill prevalence across our listing corpus, and published wage benchmarks — as of Jul 28, 2026. It is a model, not a headcount.
Why we read it this way (8)
The role sits between 15-1252 (Software Developers) and 15-1244 (Network/Systems Admins): the JD emphasises designing, provisioning, and writing IaC (Terraform/Bicep), which leans toward 15-1252, but a significant portion of the work is operating and maintaining existing AKS infrastructure, which leans toward 15-1244. 15-1252 was chosen as primary because the role explicitly requires authoring Infrastructure as Code and Helm charts — shipping artefacts — rather than purely running systems someone else built.
Terraform and Bicep are listed together as 'Terraform and/or Bicep' in the requirements section; Terraform is named first and is the more common tool, so it is the primary skill with Bicep as an alternative.
.NET and ASP.NET Core appear together in the requirements section as a single compound requirement; .NET is used as the primary name with ASP.NET Core as an alternative.
Azure Monitor and Container Insights are listed together; Container Insights is a sub-feature of Azure Monitor and is captured under the Azure Monitor skill.
Azure DevOps and GitOps-based deployment pipelines appear under the 'These will help you stand out' section and are preferred, not required.
Kubernetes/Azure certifications (CKA, CKAD, Azure Administrator) are listed under 'These will help you stand out' and are preferred. CKA is used as the primary name with CKAD as an alternative; Azure Administrator certification is a credential rather than a named technology and is omitted from the skills list.
TriZetto QNXT/Facets experience, PHI-regulated environment experience, healthcare domain background, and batch-workload experience all appear under 'These will help you stand out' but name no specific technology or tool, so they are omitted from the skills list per extraction rules.
Caller marked this a fully-remote role — scored against the national candidate pool.
Read the full posting
The employer publishes the full description on their own site — read it there ↗. Or sign in to read it here — it's free, and it also lets you track this application.