Stage 6 · Operate
On-Call Culture & Sustainability
SRE Career Growth
Ladders, competencies, and moving from operator to engineer — building a career in SRE.
SRE Career Paths
SRE offers multiple career paths. You can specialize in infrastructure, move into management, focus on reliability engineering, or transition into platform engineering. The key is understanding what each path requires and choosing intentionally.
career_ladder:
individual_contributor:
levels:
- title: "Junior SRE"
focus: "Learning fundamentals, executing on well-defined tasks"
on_call: "Shadow rotation, then primary with mentor"
- title: "SRE"
focus: "Independent incident response, automation development"
on_call: "Primary rotation, mentoring juniors"
- title: "Senior SRE"
focus: "System design, complex incident response, leading projects"
on_call: "Incident commander, runbook author"
- title: "Staff SRE"
focus: "Cross-team reliability strategy, architecture decisions"
on_call: "Escalation point, game day design"
- title: "Principal SRE"
focus: "Organization-wide reliability strategy, industry influence"
on_call: "Executive escalation, reliability program lead"
management:
levels:
- title: "SRE Manager"
focus: "Team management, on-call staffing, resource allocation"
on_call: "Team coordinator, escalation point"
- title: "Director of SRE"
focus: "Multi-team strategy, budget, hiring, cross-org alignment"
on_call: "Organizational escalation"
- title: "VP of SRE"
focus: "Business alignment, executive communication, strategy"
on_call: "Executive escalation for critical incidents"Competency Model
SRE competencies span technical skills, operational skills, and leadership skills. A well-rounded SRE develops all three. Specialists can focus on one area while maintaining baseline proficiency in the others.
competencies:
technical:
- name: "Systems Knowledge"
levels:
junior: "Basic Linux, networking, container concepts"
mid: "Kubernetes internals, distributed systems basics"
senior: "Deep systems expertise, performance optimization"
staff: "Architecture design, cross-system analysis"
- name: "Programming"
levels:
junior: "Scripts, automation, tool usage"
mid: "Production code, testing, code review"
senior: "System design, API design, library development"
staff: "Framework design, platform engineering"
operational:
- name: "Incident Response"
levels:
junior: "Follow runbooks, escalate appropriately"
mid: "Independent investigation, root cause analysis"
senior: "Incident command, cross-team coordination"
staff: "Process design, game day planning"
- name: "Reliability Engineering"
levels:
junior: "SLO monitoring, alert response"
mid: "SLO definition, error budget management"
senior: "Reliability strategy, capacity planning"
staff: "Reliability program design, organizational strategy"
leadership:
- name: "Communication"
levels:
junior: "Clear status updates, documentation"
mid: "Cross-team communication, stakeholder updates"
senior: "Executive communication, incident leadership"
staff: "Organizational communication strategy"
- name: "Mentorship"
levels:
junior: "Asking questions, learning from others"
mid: "Mentoring juniors, knowledge sharing"
senior: "Team development, culture building"
staff: "Organizational development, talent strategy"Operator to Engineer
The transition from operator to engineer is the most important career move in SRE. Operators respond to incidents. Engineers prevent them. This transition requires shifting from reactive work to proactive engineering.
| Operator Mindset | Engineer Mindset |
|---|---|
| Fix incidents when they happen | Build systems that prevent incidents |
| Follow runbooks | Write runbooks and automation |
| Respond to alerts | Design alerting strategy |
| Scale manually | Build autoscaling |
| Document incidents | Build learning systems |
Promotion Criteria
Promotions in SRE are based on impact, not tenure. Demonstrate impact at the next level through projects, incident response, mentorship, and process improvements. Document your impact clearly.
promotion_evidence:
level: "SRE to Senior SRE"
impact_examples:
- project: "Automated certificate renewal"
impact: "Eliminated 4 hours of quarterly toil"
scope: "Team-wide"
- incident: "SEV1 database outage"
impact: "Led incident response, identified root cause, wrote postmortem"
scope: "Service-wide"
- mentorship: "Onboarded 2 junior SREs"
impact: "Both engineers independent within 6 months"
scope: "Team"
- process: "Designed game day program"
impact: "Quarterly game days, 3 gaps identified and fixed"
scope: "Team"
competencies_demonstrated:
- "Technical: Deep systems knowledge, production code"
- "Operational: Independent incident response, root cause analysis"
- "Leadership: Mentorship, process design, cross-team communication"Skill Development
Develop SRE skills through practice, not just study. Take on-call rotations, lead incident responses, write automation, and participate in game days. Skills are built through doing.
- Take on-call rotations — there is no substitute for real incident experience.
- Lead postmortems — practice root cause analysis and facilitation.
- Write automation — build tools that reduce toil for your team.
- Participate in game days — practice incident response in controlled conditions.
- Contribute to architecture discussions — build system design skills.
- Mentor others — teaching deepens your own understanding.
Mentorship
Mentorship accelerates career growth. Find a mentor who has achieved the level you are targeting. Meet regularly, set goals, and get feedback. Also mentor others — it deepens your own skills and builds team capability.
SRE skills — incident response, reliability engineering, systems thinking — are transferable across companies and industries. Investing in SRE skills is investing in a career that is resilient to market changes.
Mark this lesson complete to store local progress and unlock a cleaner resume path the next time you visit.