0% completed
Course Introduction
On This Page
Who the Course Is For
What a DevOps Engineer Does
The Running Example
How the Course Is Organized
How Drills, Exercises, and Assessments Work
Where to Practice Commands
Using the Course in 2, 4, or 8 Weeks
Key Takeaways
This course does four things:
- It prepares you for DevOps and site reliability engineering (SRE) interviews by teaching the work through the rounds that test it.
- It explains how each system behaves, with numbers, so that you can reason about a failure you have not seen before.
- It shows what a mid-level answer contains and what a senior answer adds.
- It works through the follow-up questions that interviewers ask after your first answer.
It also leaves three things out. It does not define every tool or teach a tool from its first command, and it does not prepare you for a certification exam. It also cannot give you a live server in the browser, because the course player cannot run a shell.
The sections below explain who the course serves, how its chapters fit together, and how to use it in the time you have.
Who the Course Is For
The course is written for working engineers who already use DevOps tools and are preparing for DevOps or SRE interviews. Most readers have about 2 to 8 years of experience in DevOps, SRE, cloud, or infrastructure work. The course also serves engineers who are aiming for platform engineer or production engineer roles. Those jobs share most of the same skills and rounds.
You are expected to know what Git, a container, and a cloud account are. You may still find it hard to explain, under questioning, why a container keeps restarting or why a release that passed every check still slowed the site. The course teaches that kind of explanation.
What a DevOps Engineer Does
A DevOps engineer builds and runs the systems that carry software safely into production and keep it reliable there. Production is the environment that real customers use. The work includes the automated pipeline that builds, tests, and deploys each change, and the infrastructure that the software runs on. It also includes the monitoring that shows whether a change helped or harmed customers.
The job is judged by results rather than by tools. A team that releases small changes many times a day, rarely breaks production, and recovers within minutes has a working delivery path, whichever tools it uses. The work draws on six skills: systems knowledge, automation, infrastructure, delivery, reliability, and communication.
The Running Example
Many lessons return to one online grocery company, so that each new topic builds on numbers you already know. The company has 60 software engineers, 14 services, and about 30,000 orders a day. At the start, it releases every second Tuesday night, and about 1 release in 4 breaks something that customers can see.
Over nine months, its first DevOps engineer replaces that schedule with about 25 small deployments each working day. Later lessons use the same company to speed up its build checks, manage its cloud resources with Terraform, measure its checkout service, and respond to its incidents. Other lessons use short examples of their own where the grocery company does not fit.
How the Course Is Organized
The chapters move from the job, to the tools and systems that it uses, to the rounds that test it, and then to full practice. The diagram shows every chapter in reading order.
- The job and its foundations. What a DevOps Engineer Does explains the role, related job titles, the path from a code change to production, and how interview loops test the job. Linux and Networking Fundamentals covers how Linux runs programs and how a request crosses the network. The Troubleshooting Round applies that knowledge to failures, and Coding and Scripting covers the small programs that these rounds ask for.
- The tools of the job. Containers and Kubernetes, CI/CD and Safe Releases, Terraform and Infrastructure as Code, and Cloud Fundamentals Through AWS each explain how a tool works, how it fails, and which choice to make.
- Running production. Observability and SLOs covers measurement and reliability targets. Reliability Engineering Practices covers the regular work that keeps a service within those targets: automation, capacity, overload, and on-call readiness. Incident Response and Postmortems covers what a team does when production fails. The Infrastructure Design Round and Security and the Software Supply Chain follow.
- Practice. Behavioral Answers and Project Review prepares the stories that you tell about past work. Take Home Tasks and Full Practice Interviews then runs complete loops at mid and senior level. The optional AI Infrastructure and Operations Agents covers a newer area whose tools change quickly.
Most lessons teach the subject first and keep interview advice in one section near the end, called Using This in an Interview. The chapters named after a round are different, because the round itself is their subject.
How Drills, Exercises, and Assessments Work
Three lesson formats give you practice inside the course, in addition to the practice questions that end each lesson.
Drills. Each drill in The Troubleshooting Round begins with the interviewer's words and what you are told. It then investigates step by step: what the candidate says, the command, the output that the interviewer gives, and what that output shows or rules out. Before you read the steps, write your own plan, and then compare the two.
Exercises. Coding and Scripting contains exercises whose starter code runs in the browser when you press Run. The player runs Python 3.12 with the standard library only. Each program ends with checks that print PASS or FAIL, so the starter shows failing checks, and you finish when every check passes. Hints and a full solution stay hidden until you open them.
Assessments. Every chapter from Linux and Networking Fundamentals through Behavioral Answers and Project Review ends with an assessment. Each attempt draws ten questions from a larger bank, so a second attempt covers different material. Most questions give you evidence, such as a symptom or a few lines of output, and ask what it rules out or what to do next. A final assessment follows the practice interviews.
Where to Practice Commands
The course player cannot run a shell, so you cannot type Linux, Kubernetes, or Terraform commands inside the course. Troubleshooting practice in the course is therefore written. The drills give you the output that a real system would show, and you decide what it means and what to check next.
Typing the commands yourself happens outside the course. The four layers below build different abilities.
| Layer | Where it happens | What it builds |
|---|---|---|
| Written drills | In the course | The order of an investigation and the reading of output |
| Python exercises | In the course, with a Run button | Small working programs under time pressure |
| Local practice | A Linux virtual machine, Docker, and kind on your own computer | Typing commands and repairing failures you cause on purpose |
| Outside practice sites | Free tiers of sites such as SadServers and iximiuz Labs | Repairing a broken server that someone else prepared |
kind (Kubernetes in Docker) runs a small Kubernetes cluster inside containers on one computer, with each container acting as one machine of the cluster. After a drill, repeat its failure locally: fill a disk, stop a service, or break name lookup, and then investigate with the drill's commands.
Using the Course in 2, 4, or 8 Weeks
Choose the plan that fits the time before your interviews. The course has 77 lessons after this one.
| Time | Plan |
|---|---|
| 2 weeks | Week 1: What a DevOps Engineer Does, The Troubleshooting Round, Coding and Scripting, and the tool chapter that matches the job description. Week 2: Reliability Engineering Practices, Incident Response and Postmortems, The Infrastructure Design Round, Behavioral Answers and Project Review, and the practice interviews. Read Linux and Networking Fundamentals when a drill shows a gap. |
| 4 weeks | About 19 lessons a week. Week 1: the job, Linux and networking, and troubleshooting. Week 2: coding, Kubernetes, and CI/CD. Week 3: Terraform, AWS, observability, and reliability practices. Week 4: incidents, infrastructure design, security, behavioral answers, and the practice interviews. |
| 8 weeks | About 10 lessons a week in reading order, with every chapter assessment, plus local practice and an outside practice site each week. Add the optional chapter if the role involves AI workloads. |
In every plan, say your answers aloud. An answer that reads well on the page can still become unclear when you must speak it and then answer a follow-up question.
Key Takeaways
- The course teaches the DevOps and SRE jobs through the rounds that test them, with mechanisms and numbers rather than definitions.
- One grocery company appears in many lessons, so its numbers build from lesson to lesson.
- Drills, Python exercises, and chapter assessments give practice inside the course, while commands are practiced locally and on outside sites.
- Choose the 2, 4, or 8 week plan that fits the time before your interviews.
The first lesson, What a DevOps Engineer Does, follows the grocery company's first DevOps engineer through nine months of work and shows how the company measured the result.
Reading Progress
0%
On This Page
Who the Course Is For
What a DevOps Engineer Does
The Running Example
How the Course Is Organized
How Drills, Exercises, and Assessments Work
Where to Practice Commands
Using the Course in 2, 4, or 8 Weeks
Key Takeaways