$ run as a normal user# run as root (or with sudo)
Pick projects that solve real problems
Use real systems from work (with permission, without company secrets) or realistic copies of them.
| Project | Shows | Phase |
|---|---|---|
| Server health and backup automation | Bash/Python, systemd timers, logging | 1 |
| A company environment in Azure | Identity, networking, VMs, storage, monitoring | 2 |
| Staging environment as code with CI/CD | Terraform, remote state, GitHub Actions, OIDC, scans | 3 |
| The app on a home Kubernetes cluster | Deployments, services, ingress, storage, policies | 4 |
| Secure GitOps platform | Argo CD, signed images, admission policies, Falco | 5 |
| Cloud Resume Challenge (Azure) | Static site + function + database + IaC + CI/CD | Any time |
Present every project the same way
A good README answers the recruiter's questions in 2 minutes.
- What it is, in one sentence, with a diagram.
- Why: the problem it solves.
- How: the tools and the design decisions.
- Security: the controls and why they are there.
- Run it: the commands to build it from zero.
- What I learned: problems and how I solved them.
At work
Put a short demo (GIF or 2-minute video) at the top of the README.
Show it on three channels
The same work, three places.
- GitHub: the code and the README.
- This site: summaries, labs with notes, notes pages, the project pages.
- LinkedIn: short posts about each step — the notes on this site come from those posts.
Prepare for interviews
Practise explaining, not only doing.
- DevOps Exercises (bregman-arie) on GitHub: hundreds of interview questions.
- For every project: explain the design on a whiteboard in 5 minutes.
- Be ready for live tasks: debug a broken Deployment, write a small pipeline, read a Terraform plan.