Site Reliability Engineer
Posted Updated 1
view
About the Role
We are looking for a mid-level Site Reliability Engineer to join our 24/7 gaming platform team. You will own reliability during your shift, respond to incidents, and contribute to the automation and observability work that keeps our platform stable at scale.
This is a structured shift role — you will know exactly when you are on, with clear handoffs and a full team behind you. No ambiguous on-call creep.
Core Stack
- Cloud Infrastructure: AWS (EC2, EKS, RDS, S3, CloudWatch)
- Container Orchestration: Kubernetes
- Infrastructure as Code: Terraform
- Observability: Prometheus, Grafana, or equivalent
- CI/CD: GitHub Actions / Jenkins or equivalent
- Scripting: Python, Bash
Key Responsibilities
- Own platform reliability and incident response during assigned shift
- Monitor system health, investigate alerts, and coordinate resolution across teams
- Perform structured handoffs with detailed incident and status notes at shift boundaries
- Write and maintain runbooks, post-incident reviews, and operational documentation
- Identify and implement automation to reduce toil and improve system resilience
- Collaborate on SLO/SLA definitions and track error budgets
- Contribute to capacity planning, deployment pipelines, and infrastructure improvements
Requirements
- 2–4 years of experience in SRE, DevOps, or infrastructure engineering
- Hands-on experience with AWS services in a production environment
- Working knowledge of Kubernetes (deployments, services, scaling, troubleshooting)
- Experience writing and managing infrastructure with Terraform
- Solid understanding of Linux systems and networking fundamentals
- Experience with monitoring and alerting tools (Prometheus, Grafana, Datadog, or similar)
- Comfortable working in a shift-based, 24/7 operational environment
- Strong written communication skills for handoffs and incident documentation
Nice to Have
- Experience with gaming platforms or high-traffic consumer applications
- Familiarity with chaos engineering or game day exercises
- Knowledge of CDN management and edge infrastructure
- Experience with Helm, ArgoCD, or GitOps workflows
What We Offer
- Structured three-shift model (morning, afternoon, night) — predictable schedule, no surprise on-call
- Shift allowances for afternoon and night rotations
- Exposure to real scale: millions of concurrent users, live game events, global infrastructure
- Blameless post-incident culture with genuine investment in learning