I worked as an SRE at a US startup, at PhonePe, and at KayHosting. Cracking SRE is the guide I wrote from that experience. It covers the concepts, questions, and practical thinking you need to get through SRE interviews.
I used to prepare the way most people do: Linux commands, some Kubernetes, and basic system design. It felt like I was covering everything.
Then I started interviewing, and I got stuck. I knew the material. The questions were just different. They didn't ask for definitions. They asked how I think when things break:
What do you do when latency suddenly spikes?
Where do you start when the dashboards look fine but users are complaining?
How do you debug when you don't have enough information?
That's when I saw the gap.
Cracking SRE is the guide I wish I'd had earlier. It covers:
What SREs actually do day to day
The fundamentals that matter: Linux, networking, and observability
How to approach system design from a reliability perspective
How incidents are handled in real systems
SLOs, error budgets, and RTO/RPO, explained without the usual confusion
What interviews are really testing, and how to approach them
The welcome email can take a few minutes to arrive. Check your spam folder if it doesn't show up.
