Select your current position
Pick a role and level — we'll show the growth path, skills and gap analysis.
Development path
Junior
0-2 years
Responsibility: Monitoring SLI/SLO. Participating in on-call rotation. Writing runbooks. Automating routine operations. Incident analysis.
Key skills:
Middle
2-5 years
Responsibility: Defining SLI/SLO/SLA. Designing monitoring. Capacity planning. Automating incident response. Post-mortem analysis.
Key skills:
Senior
5-8 years
Responsibility: Designing highly available systems. Chaos engineering. Performance engineering. Error budgets. Coordination with development.
Key skills:
Lead / Staff
7-12 years
Responsibility: SRE strategy. Reliability culture. SLO standards. Incident management processes. Coordination with product.
Key skills:
Principal
10+ years
Responsibility: Enterprise reliability strategy. Multi-region architecture. SRE culture at scale. Industry best practices.
Key skills:
Gap analysis: skills to develop
To reach the next level you'll need to develop:
Applies GitOps for SRE tasks: configures monitoring and alerting through GitOps (Prometheus rules as code), manages SLO definitions in Git, implements emergency procedures through Git-based runbooks. Ensures observability for GitOps sync status.