12 weeks · intensive
For whoever has a deadline
About 8 hours a week, in 1 cycle focused on the gaps that weigh most.
Career in 2026 and 2027
A DevOps engineer builds and runs the automation that takes code from a commit to production: pipelines, infrastructure as code, containers and the telemetry around them. The role grows from following established workflows to designing the platform and reliability practices other teams build on.
Content reviewed on October 20, 2026
Mid-level
Owns the build, infrastructure and container setup of a service end to end, including how it is observed in production.
You write the Terraform, Ansible and Dockerfiles for a service yourself and answer for them when they misbehave. You also set up the dashboards and logs that tell you something is wrong. Compared with junior, you design the change instead of only applying it.
Average score required: 69%
Terraform Basics
Why: You manage remote state and split a stack safely, so two engineers applying at once or a manual console edit does not corrupt the environment.
Configuration Management
Why: You write idempotent playbooks and detect drift, so a server patched by hand during an incident is brought back to the declared state instead of staying a snowflake.
Docker Fundamentals
Why: You build small images with sensible volumes and networks and compose a local stack, so a service behaves the same on a laptop and in the cluster.
Container Security
Why: You scan images, drop root and keep secrets out of layers, so a vulnerable base image found in a scan is fixed before it reaches production.
Metrics & Dashboards
Why: You expose service metrics and build a RED dashboard, so you can see error rate and latency rising after a deploy rather than hearing about it from users.
Log Aggregation
Why: You ship structured logs to a central store, so during an outage you search one place by request id instead of logging into each host.
Each level of this career maps to a study trail. Read the full topic map for free, then measure your level.
12 weeks · intensive
About 8 hours a week, in 1 cycle focused on the gaps that weigh most.
40 weeks · regular
About 4 hours a week, in 3 cycles. Each cycle carries what was left from the previous one.
A DevOps engineer builds and runs the automation that takes code from a commit to production: pipelines, infrastructure as code, containers and the telemetry around them. The role grows from following established workflows to designing the platform and reliability practices other teams build on.
DevOps Engineer is mapped in 4 levels: Junior, Mid-level, Senior, and Expert. Open each level above to see the skills it must prove.
The plan has 2 paces: 12 weeks per level at about 8 hours a week (intensive) and 40 weeks per level at about 4 hours a week (regular).
A study session on each new topic, at your level.
Hands-on lessons on using AI in your career's daily work.
Each requirement is proven by measurement, not by a checkbox.
At the end of each cycle you see what moved and what carries over.
A short diagnostic measures the skills you already have. The journey starts from there.