A DevOps certification path that makes sense
Updated
Foundations, Practitioner, Professional: what each level proves and how the supervised sittings work.
Certifications help when they map to real work and hurt when they map to memorization. The DevOps path here has three levels because the work has three depths: operate the basics, run systems under pressure, design for strangers.
The three levels
Foundations. Linux services, permissions, shell, networking, DNS, TLS, Git, CI, containers, incidents. Hands-on labs prove it, including browser playgrounds for the core set.
Practitioner. Live systems under pressure: orchestrator failures, probes, rollouts, config at scale. Judgment calls with incomplete data, like the real on-call.
Professional. Design for teams you will never meet: access models, supply-chain care, cost awareness, reviews that hold. Entry needs both earlier levels.
How sittings work
Exams run as scheduled supervised sittings in small classes, with automated grading and human review before any pass counts. Fictional sample records on the certifications page show the format honestly; real credentials issue only after a supervised pass.
Checklist: a path worth walking
- Foundations labs done, including the tricky ones.
- Practitioner judgment practiced on incidents, not just reading.
- Professional prerequisites (both earlier levels) completed.
- Portfolio and stories ready beside the certificate.
Related reading
- The program: DevOps program.
- Start at the base: DevOps Foundations.
- How certification works: Certifications.
Straight answers
Frequently asked questions
What does Foundations prove?
Working Linux, networking, Git, CI, container and incident basics, hands on. The base every DevOps role assumes.
How do the exams run?
Scheduled supervised sittings with automated grading plus human review. Dates and seats are published; booking opens with the live checkout.
Is the certificate alone enough for a job?
No certificate is. Pair it with a homelab portfolio and incident stories from real practice.