Twelve weekends of Friday-to-Sunday evenings — ten modules, 90 hours of live instruction, and one running system you build yourself, from a bare Git repo to a containerized app deployed on Kubernetes by a pipeline you wrote. For engineers who already know the cloud and want to automate everything that touches it.
This cohort assumes you are technical: you have used a terminal, you have spun up resources in a cloud console, and you are not learning what a virtual machine is. What you are here for is everything that turns those resources into an automated delivery pipeline.
The order is deliberate: every module consumes what the last one produced. By module 10 you are deploying an artifact that was built, scanned, containerized and provisioned by work you did in modules 4 through 9.
Across the twelve weekends, modules 1 to 5 run about a weekend each and modules 6 to 10 rather longer — Docker, ECS, CI/CD, Terraform and Kubernetes get the bulk of the 90 hours. Pace shifts with the room; nobody is left behind to keep a schedule.
What DevOps actually is once you strip the marketing off it: the delivery lifecycle, why handoffs break, and where every tool in this course sits relative to the others. Then we build the shared environment every later module runs on.
The subset of Linux you will type every week: permissions and ownership, packages, processes and systemd services, logs, networking, disks, pipes and text processing, and enough shell scripting to automate a task and read someone else’s script.
Version control as a team practice, not a set of memorized commands. Branching models, pull requests, code review, resolving merge conflicts without panic, and the repository conventions every later module depends on.
How source becomes a shippable thing. Dependency resolution, build lifecycles, and why a versioned artifact — not a folder of files — is what you deploy. We build the same application twice, on two toolchains.
Standing up SonarQube, reading what it tells you, and separating real findings from noise. Quality gates, coverage, code smells and vulnerabilities — configured so a failing gate stops a bad build instead of being ignored.
Images, layers, registries, and the difference between a container and a virtual machine. Writing a Dockerfile that is not 1.2 GB, wiring multiple services with Compose, and handling data, networking and secrets.
What an orchestrator does that docker run cannot. ECR, task definitions and revisions, the two IAM roles everyone confuses, Fargate versus EC2, load balancing, health checks, rolling deployments and autoscaling.
Turning modules 3 through 7 into one automated pipeline. Workflow syntax, triggers, jobs and matrices, caching, secrets management, environments and approvals — build, scan, containerize, push, deploy, on every commit.
Describing infrastructure instead of clicking it. HCL, providers, state and why it matters, variables and outputs, modules, and a safe change workflow — plan, review, apply, destroy — against a real cloud account.
Why orchestration exists and what it costs you. Pods, deployments, services and ingress; config maps and secrets; scaling, rolling updates and rollbacks; and reading logs and events when a pod will not start.
There is no separate final project — the system you build across the twelve weekends is the capstone. One repository whose pipeline builds it, scans it, containerizes it, provisions its infrastructure and deploys it, which you can demo and defend line by line.
A dedicated session on rewriting your CV around what you actually built, and rehearsing the questions it invites — the ones DevOps interviews really ask. Not a placement programme; preparation for the interviews you get.
Seven and a half hours of live instruction every weekend, taught over video rather than pre-recorded. You will be building alongside — expect to share your screen and get unstuck in the room.
Everything in this course runs on free tiers. Where a lab would incur cost, we tear the infrastructure down at the end of the session — and you will learn to check that it is actually gone.
All 12 weekends · all 10 modules · 90 hours of live instruction · capstone project · CV & interview preparation · recordings for 12 months · community access · individually reviewed labs.
Not sure it is the right level? Message me describing where you are now and I will tell you honestly whether this cohort fits.