Learn the shell, the repository, containers and the cloud in the order DevOps work uses them, in simulators where nothing you break is real. Every task is checked, and the pathway ends in a release project, a timed assessment across the tools and the interview.
Take the steps in this order. Each step is a set of units from one course, not the whole course: the units this role uses. Open a unit to start its first lesson.
1
The Linux shell
Most DevOps work happens on Linux machines you reach through a terminal. You move around the file system, change files safely, read logs with pipes, search and rewrite text, then handle permissions, failures and scripts with proper error handling.
Infrastructure lives in repositories too, and every change goes through review. You commit and inspect history, branch and merge, keep work in progress aside, sync with a remote and deliver changes as a team.
Many teams ship their services in containers. You build images, configure containers at run time, run a local stack with Compose, then deploy to a cluster with configuration, health checks, resource limits and routed releases.
The cloud is where those containers run. You learn accounts and regions, IAM roles and policies, S3, compute and disks, the network paths between services, and the operations work of monitoring and delivery.
Define resources and module interfaces in HCL, read the proposed plan and inspect state bindings before applying a change. Practice adoption, address moves, drift and recovery with an independent local provider model; hosted HCP runs and real cloud permissions need separate study.
Each project starts from a fictional company's brief and moves between tools the way the job does: what you build in one stage is where the next one starts. Every brief is free to read.
Velomint
GtGitK8Docker and KubernetesAWAWS
Project
Recover from a failed release
Release 2.14.0 broke one bike unlock in three until on-call rolled it back. Revert the bad commit in Git, ship 2.14.1 on Kubernetes behind a readiness probe, add the CloudWatch alarm that would have caught it, and write the incident report.
A patient changed a number in an invoice link and saw a stranger's bill. Read the portal's access log in the shell to find what one session took, fix the endpoint so it checks who is asking, and write the incident note that decides who must be told.
When you finish the units, test yourself across the tools of the job at once: 12 practical tasks in 50 minutes, each in the tool it is about and checked automatically. The clock keeps running if you close the page.
Tool
Tasks
Minutes
Linux and the shell
3
11
Git
3
11
Docker and Kubernetes
3
11
AWS
3
14
How it is scored
Each tool
Ready when you get two thirds of its tasks right or more, Close at one third, otherwise Not yet. A coding task earns the share of its tests that pass.
Ready for interviews
75% or more overall, and every tool at Ready.
Nearly ready
50% or more overall, and no tool at Not yet.
Keep practicing
Anything else. The report lists every task you missed with the lesson that teaches it.
The assessment is free. The result is practice feedback in the Interview Hub's report format, not a hiring decision. Retakes draw different tasks where the question pools allow.
The interview
The Interview Hub runs the DevOps engineer interview round by round, at a fictional employer: you answer out loud or in writing, the interviewer follows up, and the report quotes your answers.
The first unit of every course, with no account: 5 of the 41 units on this pathway. Every project brief is free to read, and the job-readiness assessment is free.
One Course
One course in full. On this pathway that is one of these: Linux and the shell (8 units), Git (7 units), Docker and Kubernetes (8 units), AWS (6 units), Terraform (12 units).
All Access
The whole pathway: every unit, every project stage and spoken interview practice.
A DevOps engineer keeps software moving from a developer’s commit to running in production, and keeps it running. That means build and release pipelines, infrastructure kept as code in Git, containers and clusters, cloud accounts with the right permissions, and alarms that wake someone before customers notice. When something breaks, they find out why from logs and metrics, fix it, and change the process so it doesn’t happen again.
From the shell to the cloud
Everything else runs on Linux, so the shell comes first. Git comes next because every infrastructure change is reviewed and versioned. Containers build on both, and the cloud is where the containers end up. By the AWS step you are using all four together.
Project evidence
The Velomint project is a failed release from start to finish: revert the commit that broke bike rental payments in Git, ship 2.14.1 on Kubernetes behind a readiness probe, add the CloudWatch alarm that would have caught it and write the incident report. That is the shape of a DevOps interview story. The assessment then shows which tool to practice before you apply.
Cloud choice
The pathway project uses AWS. If your target role names Microsoft Azure, use the Azure course alongside the same Linux, Git and container foundations. Practice Azure scope, identities and network controls in its own console. Its resources don’t connect to the AWS project.
Learn one provider well enough to explain a workload before switching. Compare the identity, network and recovery boundaries, then learn the second provider’s actual names and commands. The Azure course also has independent interview practice.
The Google Cloud course offers another provider path with projects, IAM, Cloud Run, Pub/Sub and fixed log evidence. Use its GKE guide to separate cluster configuration from the Kubernetes workload tasks. It does not connect to this pathway’s AWS account.
The OCI course adds an Oracle provider option with compartments, policy statements, VCNs, Object Storage and Autonomous Database configuration. Choose it when those responsibilities match your target work; its account stays separate from this pathway project.
Network and security practice
The networking course adds subnetting, switch and router commands, routing and packet evidence. For alert investigation, the SOC analyst course teaches log searches and incident handoffs. Use the cybersecurity practice path to connect these tasks with Security Labs and application security.
Infrastructure as code
Practice the Terraform course after the cloud and repository steps. A provider object, its recorded state binding and the desired configuration can disagree. Read the plan before choosing an operation, preserve object identity during a refactor and retain the evidence another engineer needs to review a recovery. The course runs a documented local teaching model. Real cloud access, hosted policies and team permissions require a separately authorized environment.
Common questions
Do I need to be a developer first?
No, but you need to be comfortable reading code and writing small scripts, which the Linux units teach. Many DevOps engineers come from system administration or support, others from software. The interviews test the shell, Git and how you reason about failures.
Which cloud should I learn first?
This pathway uses AWS in its release project and cross-tool assessment. Azure, Google Cloud and OCI have separate courses with their own console vocabulary and commands. Start with the provider named in your target jobs. If none is specified, follow the AWS pathway and add another provider after you can explain one complete workload.
How long does it take?
The lessons on this pathway add up to about 77 hours. Each unit ends in a practice set, and several steps add projects and case studies. We don't promise how long getting hired takes.
What does it cost?
The first unit of every course is free, with no account. One Course opens one course in full; All Access opens the whole pathway. The pricing page shows every plan and its price.