Opscraft
DevOps from zero · Lesson 6 of 6 · 4 min read

Your path from beginner to Senior DevOps engineer

Four stages

Nobody learns all of DevOps at once. This site's topics are arranged in four stages; each builds on the one before.

Enlarge diagram1. Foundations2. Core tools3. Productionplatforms4. Senior skillsDevOps from zeroLinuxPython and BashGitNetworking basicsIP, TCP, TLS, HTTPDNSDocker and ComposeAWS and IAMRoute 53TerraformGitHub ActionsJenkinsBuild toolsKubernetesTroubleshootingAmazon EKSHelm and KustomizeGitOpsPolicy (OPA)DeploymentsObservabilitySRE and incidentsDevSecOpsSystem designInterviews
Figure 1. The four stages of this site, from beginner to senior. Each stage builds on the one before.
Swipe sideways to see all of it, or tap to open it full screen.
  1. Foundations — Linux, the command line, scripting, Git, networking and DNS. Everything else assumes these.
  2. Core tools — containers, a cloud provider (AWS here), infrastructure as code with Terraform, and CI/CD pipelines.
  3. Production platforms — Kubernetes and EKS, Helm, GitOps and safe deployment strategies.
  4. Senior skills — observability, reliability engineering and incident management, security, system design and interviews.

What changes as you grow

Enlarge diagramJuniorcompletes well-defined tasksfollows runbooksfixes pipelines with helplearns the toolsMid-levelowns a service end to endautomates repetitive workhandles on-call alonereviews others' changesSeniordesigns systems, weighstrade-offsleads incidents calmlymentors and sets standardsconnects work to business goals
Figure 2. The tools stay the same; scope and judgement grow. What each level is expected to do.
Swipe sideways to see all of it, or tap to open it full screen.

The tools stay mostly the same; what grows is scope and judgement. A junior engineer completes well-defined tasks. A mid-level engineer owns a whole piece of the platform. A senior engineer designs systems, weighs trade-offs (cost, risk, speed), leads incidents calmly, and makes the whole team better through reviews, documentation and mentoring.

How to practise

Reading is not enough — DevOps is learned by doing and by breaking things safely.

  • Run Linux yourself. A free virtual machine (VirtualBox, UTM), WSL on Windows, or a small cloud server.
  • Use a cloud free tier carefully. Most providers give new accounts free credits or a free tier. Set a budget alert on day one and delete what you create.
  • Build one project end to end, then keep improving it:
Enlarge diagramA small web appany language; one pageand an APIContainerise itwrite a Dockerfile; run itlocallyAdd CItest and build the image onevery pushInfrastructure as codeTerraform: network andclusterDeploy to Kuberneteswith Helm, then try GitOpsObserve ita dashboard and one alert123456
Figure 3. One practice project that touches every stage. Build it once, then keep improving it; it doubles as a portfolio piece.
Swipe sideways to see all of it, or tap to open it full screen.
  • Write things down. A short README for each project, with a diagram, is great practice for interviews and real design reviews.

How to use this site

For each topic: read the lessons in order. Start with the green In plain words box, look at the diagrams, then read the details. Tap any dotted-underlined term to see a plain definition. When you have read a topic, take its three tests (score 15 out of 20 to pass) and practise its interview question out loud. Come back to the dashboard to see which topics need another pass.