Site Reliability Engineer II
Phenom (company site, opens in a new tab)4–8 yrsHyderabadOn-siteDirect career pageEst. 18–32 LPA
Posted 2d ago
Reach people at Phenom
People at this company you can reach
Log in to see who works here
Create a free account or log in to see the people at Phenom you could write to:
- Recruiters & HR
- People in this function
- Work addresses
Your match
Against your primary resume
Log in to see your match score
Create a free account or log in to unlock your CV match score across:
- Role fit
- Experience
- Industry relevance
Protocol Intelligence
How competitive this role is
Competition
Background fit
Strictness
Log in to see why each signal reads the way it does.
Job description
Structured overview of role & requirements
About This Role
- Own reliability of production Kubernetes and AWS workloads, including troubleshooting, automation, and reliability improvements.
- Handle production incidents through structured response, root-cause analysis, postmortems, and MTTR tracking; apply SLI/SLO/SLA and error-budget concepts.
- Execution-focused individual-contributor role requiring independent operational ownership, not just running infrastructure designed by others.
Minimum Requirements
- Work Experience Required: The role description specifies 3–6 years in production SRE or platform engineering with direct on-call/incident-management ownership; the Work Experience section specifies 4–8 years. These ranges conflict.
- Strong Linux troubleshooting and hands-on production AWS ownership across EC2, EKS, VPC, IAM, CloudWatch, and Route53; Kubernetes troubleshooting beyond basic workloads, including CRDs, operators, CSI drivers, and common pod/probe failures.
- Able to write and debug a working script live and unaided (Python or Go preferred; Bash acceptable); must have authored Terraform modules and created at least one Prometheus/Grafana dashboard or alert rule from scratch.
- Production troubleshooting experience with Kafka, Redis, or a relational/NoSQL database at scale; experience with structured incident management, postmortem authorship, MTTR tracking, and SLI/SLO/SLA and error-budget concepts.
Ideal Candidate Profile
- Has independently operated production Kubernetes/AWS systems and can trace issues across the full request path, from public routing through load balancing and ingress to services and pods.
- Combines hands-on debugging with automation and infrastructure design, rather than relying only on existing scripts, Terraform modules, or observability dashboards.
- Has practical production exposure to distributed data systems and incident-driven reliability work; service mesh, CI/CD ownership, AWS cost optimization, DBRE, and container image security are additional advantages.