SRE Leadership and Culture
Learn to lead reliability without authority: run blameless reviews, grow on-call engineers, shape designs early, and win support for reliability work.
What You'll Learn
Understanding Why Technical Skill Alone Stops Scaling
You joined acme-shop as its first SRE. Over the last modules you found the file descriptor leak, set checkout's SLOs, ran the first real incident...
Running Blameless Postmortem Reviews as a Facilitator
The difference between writing a postmortem and running the review Writing a blameless postmortem is a solo skill, covered in Incident Management and...
Building On-Call Capability in Junior Engineers
Why just adding them to the rotation fails Putting a junior engineer on the pager and letting them learn under fire produces one of two bad outcomes.
Influencing Architecture Decisions Before Code Is Written
Why influence has to happen before the design is final By the time a production readiness review happens, the architecture is largely fixed.
Making the Business Case for Reliability With Error Budget Data
Why this feels risky does not work Leadership hears "this is risky" from every team about every feature.
Having the Toil Budget Conversation With Management
Why toil is harder to argue than outages An outage makes its own case. Toil does the opposite: it looks like normal, competent work.
Skills You'll Master
Curriculum Index9 topics
Understanding Why Technical Skill Alone Stops Scaling
You joined acme-shop as its first SRE. Over the last modules you found the file descriptor leak, set checkout's SLOs...
Running Blameless Postmortem Reviews as a Facilitator
The difference between writing a postmortem and running the review Writing a blameless postmortem is a solo skill...
Building On-Call Capability in Junior Engineers
Why just adding them to the rotation fails Putting a junior engineer on the pager and letting them learn under fire...
Influencing Architecture Decisions Before Code Is Written
Why influence has to happen before the design is final By the time a production readiness review happens, the...
Making the Business Case for Reliability With Error Budget Data
Why this feels risky does not work Leadership hears "this is risky" from every team about every feature.
Having the Toil Budget Conversation With Management
Why toil is harder to argue than outages An outage makes its own case.
Recognizing the Senior-to-Staff Inflection Point
What changes between senior and staff impact Two engineers with identical technical depth can have very different reach.
Practicing Influence Without Authority in a Lab
There is nothing to install and no cost. Everything below is written material and role-play, and the outputs feed the...
Quick Reference and Common Mistakes
Quick reference Common mistakes Staying silent while a review drifts into blame is the most damaging facilitator habit.
Career Impact
Roles that use the skills in this module.
Site Reliability Engineer
DevOps Engineer
Platform Engineer
Next Modules
Related Guides
Practice on the Coding Sheet
Not a software engineer sheet. Every problem comes from real DevOps, SRE, Platform and Cloud interviews, from your first script to a system you build yourself.
Open the Coding SheetFrequently Asked Questions
Yes. Influence without authority is a set of learnable habits: facilitating reviews, teaching on-call skills, asking sharp questions in design reviews, and translating risk into business language. Staff-level SREs do most of their work this way.
The written document sets the intent, but the live facilitator enforces it. They restate the goal, ask what the system allowed instead of why a person acted, and redirect blame language the moment it appears.
You earn the invite. Ask a few sharp reliability questions that save the team real rework, then point back to those saves later. Blocking designs or nitpicking unrelated details loses the seat quickly.
Use numbers the business already agreed to. Show how many minutes of error budget remain, what similar launches cost before, and what your error budget policy says happens next. Avoid saying only that something feels risky.