Home · Jobs · Kubernetes SRE

Kubernetes SRE Jobs.
SLOs, GitOps, on-call.

Reliability-focused Kubernetes roles — EKS, GKE, AKS, Argo CD, Prometheus, Istio. SLO ownership and on-call rotation expected. US and remote-friendly only.

—SRE roles now
9Sources
12hRefresh
SLO+ On-call

Open Kubernetes SRE roles

Loading current roles…

Browse all jobs →

What "Kubernetes SRE" looks like in these listings

Real Kubernetes-SRE work is more than running kubectl. The postings here ask for SLO ownership, error-budget driven prioritization, observability stack expertise (Prometheus / Grafana / OpenTelemetry), and one runtime specialty — networking (Cilium, Istio, Linkerd), security (OPA, Kyverno), or storage (Rook, Longhorn).

GitOps is increasingly the default — Argo CD or Flux. Custom controllers and operators appear in Senior+ postings. We tag roles where on-call is mentioned so you know what you're signing up for before applying.

Common questions

What's the difference between SRE and DevOps roles?
SRE roles emphasize reliability, on-call, error budgets, observability. DevOps emphasizes pipelines, IaC, developer enablement. Both share Kubernetes; this page leans SRE.
Which Kubernetes ecosystems show up most?
EKS dominates AWS shops, GKE dominates Google shops, AKS appears in enterprise. Service mesh: Istio, Linkerd. GitOps: Argo CD, Flux.
Do these roles require deep Kubernetes internals?
Senior and Staff roles do — etcd, scheduler internals, CNI/CSI plugins, custom controllers. Mid-level roles ask for solid k8s usage + one specialty.