About The Role
The role keeps production systems running at scale - owning the reliability, observability, and performance of infrastructure that serves millions of requests per day across cloud and on-prem environments.
This is a hands‑on engineering position, not a ticket queue. The team treats operations as a software problem: SLOs are written, error budgets are enforced, and automation replaces toil wherever it exists.
Key Responsibilities
- Build and maintain scalable infrastructure on Kubernetes (EKS/GKE), Terraform, and AWS/GCP, treating everything as version‑controlled code
- Design and enforce SLOs, SLIs, and error budgets; drive incident response, post‑mortems, and concrete reliability improvements from every outage
- Instrument services with Prometheus, Grafana, and OpenTelemetry to deliver actionable dashboards and alerting across the stack
- Reduce toil through automation in Python and Go - capacity planning, failover, auto‑remediation, and deployment tooling built on CI/CD pipelines (GitHub Actions, ArgoCD)
- Optimize system performance at every layer: Linux tuning, load balancing, database scaling, caching strategies, and cost‑efficient cloud usage
- Lead blameless incident reviews and serve as primary responder on a rotating on‑call schedule with real compensation for pages
- Partner with product and platform engineers on system design reviews, capacity modeling, and production readiness for new services
What We Are Looking For
- 3–8 years of experience in SRE, DevOps, or infrastructure engineering, including operating large‑scale production systems
- Deep hands‑on expertise with Kubernetes, Docker, and at least one infrastructure‑as‑code tool (Terraform, Pulumi, CloudFormation)
- Strong programming or scripting skills in Python, Go, or Bash for tooling and automation
- Production experience with observability stacks: Prometheus/Grafana, Datadog, or Splunk, including building custom metrics and alerts
- Proven track record running on‑call, leading incident response, and writing rigorous post‑mortems that drive systemic fixes
- Solid grasp of distributed systems fundamentals: consistency, availability trade‑offs, DNS, load balancing, and failure modes at scale
- Bonus: Experience with service meshes (Istio, Linkerd), GitOps workflows, multi‑region failover architectures, chaos engineering, or a background in backend software engineering. Bachelor's degree in CS or equivalent practical experience.