Jump to any problem, company or topic
Every chapter of the Google SRE book, condensed: the definitions, the rules of thumb and the war stories you are expected to know in an SRE or production engineering interview, in the order the book presents them.
What SRE is, why Google invented it, and what the production environment it runs looks like.
The patterns and concerns that shape how an SRE team works: risk, SLOs, toil, monitoring, automation, releases and simplicity.
Running a service day to day: alerting, on-call, troubleshooting, incidents, postmortems, testing, load balancing, overload, consensus, cron, pipelines, data integrity and launches.
Training, interrupts, operational overload, communication, and how SRE engages with product teams.
What other high-reliability industries do differently, the closing argument, and the appendices.