Site Reliability Engineer

About The Role The role owns the reliability of production infrastructure serving millions of requests per day — Kubernetes fleets, multi-region cloud deployments, and the observability stack that keeps them measurable. You will work directly with platform and product engineering teams to drive SLOs, automate away toil, and turn incidents into durable systems improvements. The team treats reliability as an engineering discipline, not an ops afterthought. Key Responsibilities Own SLO definition and error budget management for critical services, driving reliability reviews with product and platform teamsBuild and maintain observability infrastructure — Prometheus, Grafana, and distributed tracing — with actionable alerting that stays ahead of user-facing impactDesign, run, and continuously improve incident response: participate in the on-call rotation, lead postmortems, and track remediation to completionAutomate infrastructure provisioning and configuration with Terraform and Ansible across AWS (EKS, RDS, VPC networking)Reduce toil through tooling: self-service runbooks, automated failover, capacity planning, and progressive delivery pipelines with Argo RolloutsConduct chaos engineering experiments and load tests to validate resilience assumptions before failures happen in productionHarden security and compliance posture of production systems — least-privilege IAM, secrets rotation, and audit-ready infrastructure changes What We Are Looking For 3–7 years of experience in SRE, DevOps, or infrastructure engineering, including on-call ownership of production systems at meaningful scaleDeep hands-on expertise with Kubernetes in production — operating clusters, debugging workloads, and managing upgradesStrong programming or scripting skills in Python, Go, or Bash for building automation and toolingProduction experience with at least one major cloud provider (AWS, GCP, or Azure), including networking, IAM, and cost awarenessFluency in observability tooling (Prometheus, Grafana, Datadog, or OpenTelemetry) and in writing alerts that are worth being woken up forBS in Computer Science or equivalent practical experience; a track record of blameless postmortems and systems-level debuggingBonus: experience with service mesh (Istio/Linkerd), GitOps tooling, database operations (PostgreSQL/Redis), or contributions to open-source infrastructure projects