About The Role
The role sits on a team that keeps large-scale, distributed production systems running - Kubernetes clusters, event-driven services, and infrastructure that must stay up through deployments, traffic spikes, and failures. SLOs, error budgets, and incident response are daily practice here, not slide-deck concepts.
The work is a genuine mix of engineering and operations: designing reliable infrastructure from scratch, automating away manual toil, and digging through postmortems to find the root cause. The SREs here are trusted with real ownership and ship real code.
Key Responsibilities
Design, build, and maintain cloud infrastructure on AWS or GCP using Terraform, with a heavy emphasis on reproducibility and infrastructure-as-code
Operate and scale Kubernetes clusters in production, including autoscaling, node optimization, and workload placement decisions
Define and measure SLOs/SLIs, manage error budgets, and work with engineering teams to prioritize reliability work against feature velocity
Lead incident response for production outages, drive blameless postmortems, and implement permanent fixes that reduce repeat incidents
Build and maintain CI/CD pipelines (GitHub Actions, GitLab CI, or ArgoCD) enabling safe, frequent, progressive-delivery deploys
Improve observability across the stack with Prometheus, Grafana, and distributed tracing so engineers can diagnose issues in minutes, not hours
Reduce operational toil through automation - self-healing systems, runbook automation, and tooling in Python or Go
What We Are Looking For
3–7 years of experience in SRE, DevOps, or infrastructure engineering roles operating production systems at scale
Deep hands-on expertise with Kubernetes and at least one major cloud provider (AWS, GCP, or Azure)
Strong programming or scripting skills in Go, Python, or Bash for building internal tooling and automation
Experience with infrastructure-as-code tooling (Terraform, Ansible) and GitOps workflows
Solid grasp of networking fundamentals, load balancing, DNS, and Linux systems internals
Track record of leading or participating in production incident response and writing high-quality postmortems
Bonus: Experience with service meshes (Istio, Linkerd), chaos engineering, multi-region failover design, or a BS/MS in Computer Science or related field