Opscraft
Start here

From zero to Senior DevOps engineer

No background needed. Work through four stages in order. Every topic says what to know first and what you'll be able to do afterwards, and every lesson starts in plain words before it goes deep.

Get a study plan for your goal

Tell us what you're preparing for. AI picks the topics that matter and orders them, then your dashboard shows what to read each week.

Loading the planner…

How to study a lesson

  1. Read the "In plain words" box first. It gives the idea in everyday language with a comparison.
  2. Study the diagrams. Each one shows the idea as a picture. Tap a diagram to open it full screen.
  3. Read the details. Tap any term with a dotted underline for a plain definition. The glossary has all of them.
  4. Try it yourself. Type the commands in a practice machine, such as the Linux lab in your browser. Breaking things in a lab is how DevOps is learned.
  5. Test yourself. Each topic has three 20-question tests. Score 15 or more to pass and unlock the next.
  6. Say it out loud. Answer the topic's interview question as if in an interview, then compare with what a strong answer covers.

Or follow a path for your goal

Each path picks the topics that matter for one goal, in a sensible order. Choosing one sets your study plan; you pick the finish date on the dashboard. These are our suggestions, so check the official exam guide for any certification.

1

Foundations

How computers, Linux, Git and networks work. Everything else assumes these.

2

Core tools

Containers, AWS, Terraform, CI/CD pipelines and web serving: the daily toolkit.

3

Production platforms

Kubernetes, EKS, GitOps, service mesh, safe releases and databases: running software at scale.

4

Senior skills

Observability, reliability, security, platforms, cost, AI workloads and interviews: what makes you senior.

Optional extras

Good to have; some job descriptions ask for them.

Set up a practice lab

  • A Linux machine: WSL on Windows, a free virtual machine (VirtualBox or UTM), or a small cloud server.
  • Docker on your laptop, and kind or minikube for a local Kubernetes cluster.
  • A GitHub account for your code and free CI with GitHub Actions.
  • A cloud account on a free tier or starter credits. Set a budget alert on the first day and delete what you create.
  • An editor such as VS Code.

How long it takes

The lessons are about 25 hours of reading. With labs and tests, plan for roughly three to four times that.

At an hour a day, most people finish the foundations in a few weeks and the whole path in a few months. Going steadily beats cramming: revisit a topic's tests a week later to make it stick.

Already working in DevOps? Skim stage 1, take its tests, and spend your time where you score lowest. The dashboard shows your weak spots.