Building SRE: Culture from the Outside In
summary
Describes LinkedIn’s concrete SRE culture: require engineers to code for infrastructure and monitor everything so incidents are measurable; automate fixes so the same incident is never manual again; embed SREs with product teams (example: embedded with Apache Kafka team) to speed resolution; run blameless incident reviews and reward postmortem transparency; support career growth and “next play” moves; scale considerations include roughly 1500 applications and tooling like service guard mentioned.
AI-written summary · about
chapters (8)
- 0:00Start
- 6:53What an Sre Needs To Be
- 12:09What Gets Measured Measured Gets Fixed
- 13:09Solve the Problems in Your Architecture
- 14:55Three Kinds of Feedback
- 17:07Strong Technical Leadership
- 17:17Technology Leadership Groups within Linkedin
- 18:37The Next Play
related talks
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
21mSRE: An incomplete guide to cultural Narnia
25mSRE Guiding Principles & Transformational Framework
43mSRE From Inception to Global Scale
41mBuilding an SRE Capability Inside a Large Organization
24mBeing Reasonable about SRE
19mCrafting an SRE Roadmap for Enterprise Success
18mDeploying Humans at the Edge of SRE