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.
Roles · Site Reliability Engineer (SRE) · Mid-level
What a Mid-level } should know
1 core skills, 61 in total. Expectations per skill, and what changes at the next level.
This page lists what a Mid-level } is expected to know and do, skill by skill. Core skills are the ones a manager and peers assess in a review cycle; the rest count only in self-assessment. Main areas: DevOps & CI/CD.
Core skills for a Mid-level
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
DevOps & CI/CD · 1
Additional skills
Not assessed by the team, but part of the self-assessment and the development plan.
What changes at Senior
61 skills get a higher expectation or become core when moving from Mid-level to Senior. The biggest jumps first.
- Algorithms & Complexity: Working → Advanced · becomes core
- Apache Kafka: Working → Advanced · becomes core
- APM Tools: Working → Advanced · becomes core
- ArgoCD: Working → Advanced · becomes core
- Async Programming: Working → Advanced · becomes core
- AWS: Working → Advanced · becomes core
- Capacity Planning: Working → Advanced · becomes core
- Chaos Engineering: Working → Advanced · becomes core
- Code Quality & Refactoring: Working → Advanced · becomes core
- Code Review: Working → Advanced · becomes core
} in the open competency matrix: 61 skills across 5 levels. The matrix is free for individuals and stays free.