Building an SRE Capability Inside a Large Organization
summary
A hardware-first company with 95% revenue from instruments moves from shipping CDs and 6–18 month releases to running SaaS and shipping twice a week by incubating a small SRE team of four permanent FTEs, avoiding contractors, and rotating R&D into operations. The stack uses serverless (Kinesis, Firehose, Redshift) plus GitLab, Jenkins, New Relic, Sentry and Splunk; results are consolidated monitoring/logging, automated builds and a nascent follow-the-sun on-call model that’s working but still early.
AI-written summary · about
chapters (17)
- 0:00Introduction
- 1:05About me
- 5:01Challenges
- 6:38Release cycles
- 7:56Tools
- 10:37Fradulent
- 11:30RD
- 14:25Org Chart
- 15:45Business Case
- 19:07Slides
- 19:43What is SRE
- 21:49SRE for Customers
- 24:59Collaborating throughout the lifecycle
- 30:33Creating a new organization
- 31:18Staffing
- 37:20Where are we
- 39:22Lessons
related talks
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
33mChallenges of Starting an SRE Team from Scratch in an Enterprise
30mThe Path to SRE
43mSRE From Inception to Global Scale
23mSite Reliability Evangelism: Practice Start-up within an Established...
38mThe Smallest Possible SRE Team
18mSRE Engagement Model Transition in Building and Expanding SRE Team
22mBuilding SRE: Culture from the Outside In