Infra Eng to Staff SRE: A Tale of Developing Yourself in an Ever Evolving...
summary
An infrastructure engineer recounts moving into a staff SRE role by adopting observability practices (golden signals, error budgets), learning golang and running 38 clusters in production, and earning a CKAD certification to overcome imposter syndrome. The claim: there is no single path to staff level—technical depth helps but so do empathy, cross-team coordination, and shipping work that increases delivery velocity. Concrete results: fewer handoffs, clearer feedback loops, and measurable platform adoption.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:48Soft Skills Talk
- 5:43How does this journey begin
- 7:54Why SRE
- 9:59Change Mindset
- 11:29Mapping Out the Journey
- 16:08Imposter Syndrome
- 19:02Live Negotiating
related talks
26mFrom Nothing to SRE: Practical Guidance on Implementing SRE in Smaller Organisations
29mZero to SRE
33mMy Journey to SRE
31mConfessions of an SRE Manager
25mSRE in the Third Age
27m20 Years of SRE: Highs and Lows
13mSucceeding as the Lone SRE in a Small Team
52mThe Only Constant Is Change: Lessons from a 25 Year SRE Career
