DevOps Notes¶
General interview-prep notes for a DevOps engineer: the fundamentals first, then every tool built on them. One concept per page, each with a diagram, a free hands-on exercise and hidden-answer questions.
New here? Read How to use these notes first.
How far to trust this. These notes were drafted with an AI assistant. Every page says in its first line whether it is still an AI draft, has been fact-checked by a second AI pass, or has been verified by me. Check anything important against the sources at the bottom of the page.
The two maps¶
- One request, end to end: a request's whole journey from a browser to a container, and what can break at each hop.
- The debugging walk: a fixed order for finding out why something does not work.
Sections, in study order¶
| Section | The question it answers |
|---|---|
| Linux | What is this process doing, and what is it allowed to do? |
| Networking | How does a packet get there, and where can it die? |
| Git | What does Git store, and how do you get out of trouble? |
| AWS identity and network | Who may call what, and which subnet can reach which? |
| Containers | What is a container really, and how do you debug one? |
| Kubernetes | How does a container get scheduled, wired up and kept alive? |
| EKS | What does AWS change about Kubernetes? |
| Helm | How are manifests packaged, and what goes wrong on upgrade? |
| Infrastructure as code | How do you write infrastructure down and change it safely? |
| CI/CD | How does a commit become a running change, and how do you undo it? |
| GitOps and Argo CD | What happens when Git is the source of truth for the cluster? |
| Observability | How do you see what the system is doing? |
| AWS services | Compute, storage, data, and the services that watch them. |
| Service mesh | What does Istio do to traffic between services? |
| Serverless and Fargate | How do you run code and containers without managing servers? |
| Security | Identity protocols, secrets, vulnerabilities and guardrails. |
| Operations | Keeping it up, getting it back, paying for it, changing it safely. |
| Data stores | What an operator needs to know about the databases behind the services. |
| Interview kit | Turning what you know into answers. |
Find something¶
Use the search box at the top, or the Glossary. Every interview question in these notes is listed in the question index.