Roles · DevOps Engineer · Mid-level
2 core skills, 63 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, Testing & QA.
Grouped by area. The label on the right is the expected depth: Awareness, Working, Advanced or Expert.
Implements GitOps workflow: configures ArgoCD/Flux for automatic synchronization of Kubernetes manifests from Git, organizes Git repository structure (app-of-apps, monorepo vs multi-repo), manages secrets through Sealed Secrets or External Secrets Operator.
Conducts chaos experiments: uses Litmus Chaos or Chaos Mesh for Kubernetes, creates game days with the team. Implements basic experiments: pod kill, network delay, resource stress. Documents hypotheses, execution and conclusions.
Not assessed by the team, but part of the self-assessment and the development plan.
63 skills get a higher expectation or become core when moving from Mid-level to Senior. The biggest jumps first.
} in the open competency matrix: 63 skills across 5 levels. The matrix is free for individuals and stays free.