Zero to SRE
summary
Claims that a junior SRE becomes mid-level within one year by enforcing 20% time for learning, running 4–5 person pods, and using a public engineering leveling doc with measurable expectations (e.g., spend 5–15 minutes searching before asking). Onboarding includes a tailored technical learning plan (Linux, git, AWS/GCP, Docker, Kubernetes), hands-on projects (EC2 web app then CI/CD), paired programming, a three‑month trial, and encouraged certifications (AWS Cloud Practitioner, CKAD). This process is called out as repeatable. culture of error
AI-written summary · about
chapters (16)
- 0:00Intro
- 0:29TEACHFOR AMERICA
- 4:12Guarantee 20% Time for Learning
- 6:34Create a Culture of Error
- 8:17Make engineering teams, not individual engineers, critical to your bottom Line.
- 10:55First Day
- 11:38Engineering Leveling Doc
- 15:13Breaks moderately-sized tasks down into smaller units of work upon request and reviews break- down with senior engineers
- 16:30Prepare a technical learning plan that is aligned with the day-to- day work of your engineers.
- 18:39Develop systems of support and accountability for your junior SRE.
- 21:43Pairing and Real Work
- 24:2790 Day Trial Period
- 25:38Encourage formal Learning through exam prep. a book club, or an online course.
- 26:54Hire more junior engineers!
- 27:27First Year
- 27:56Your company can transforma junior engineer to a mid-level engineer within one year.
related talks
27m20 Years of SRE: Highs and Lows
28mBuilding a Path to the Future: Mentoring New SREs
25mSRE in the Third Age
33mMy Journey to SRE
35mNew Grads Becoming New SREs: Catalyzing a “Circle of Life”...
25mInfra Eng to Staff SRE: A Tale of Developing Yourself in an Ever Evolving...
28mEvolution of SRE and Rising Need of SRE Catalyzers
32mPassing the Torch - Building a New Grad Program to Mentor...