42 classes · 7 builds
Free — all of it
Certified.
Still not hired.
You watched the tutorials. Maybe you passed the exam, maybe you're just getting started. Either way the interview dies at the same sentence: "Walk me through something you've built." This bootcamp was built backwards from real job postings — 42 classes, each one closing that gap, ending in three production repositories you put on the table instead of a certificate.
Free, forever — every class, no card. All 42 classes are open with no account and no email — read the whole course and judge for yourself; a free sign-up just saves your progress and keeps your record. Table of contents →
Five phases
& drills
4 milestone · 3 capstone
AZ-900 · 104 · 400
We marked up the job posting first, and wrote the course second.
A cloud engineer is not hired for knowing what a virtual network is. They are hired because someone believes they can be handed production on a Tuesday and not break it by Thursday.
So we treated the posting on the right — a composite of mid-level Azure engineer listings — as a specification. The two lines circled in red are where self-taught candidates fail the technical screen. They get nine classes and a full phase.
Cloud Engineer (Azure)
Don't read about the method. Sit thirty seconds of it.
An unedited drill from Class One. Choose an answer — the marking talks you through it.
MEMORANDUM — Cloud migration, executive summary
1. Cloud shifts our spend from CapEx to OpEx.
2. Capacity scales automatically for seasonal traffic spikes.
3. Once we migrate, the provider secures our data and user accounts.
4. Pay-per-use means idle capacity stops costing full price.
Line three. Under the shared responsibility model your data and your identities never transfer to the provider. Microsoft secures the cloud; you secure what you put in it. This matters more than it sounds — the overwhelming majority of cloud breaches are not the provider being compromised, they are a customer's storage account left open or an account holding a role it never needed.
Had that memorandum reached the board unchallenged, the security budget would have been written as zero. The full class is free →
No class ends in a quiz score.
Every class ends in something you built.
Five phases. Each one ends in something you built.
In this trade the build is the examination. A phase is not complete until the artifact exists in a repository with your name on it. Every phase closes the same way: a one-page recap that draws the classes together, then a build that proves them.
Phase OneFoundations
Resource hierarchy, identity, RBAC, policy — the governance instincts that separate an engineer from someone clicking through a portal.
Phase TwoCore Infrastructure
Networks, compute, storage, private endpoints, DNS — the depth most self-taught engineers are missing.
Phase ThreeThe DevOps Core
Bicep and Terraform, GitHub Actions federated to Azure without a single stored credential. This phase is the difference between two salary bands.
Phase FourOperate, Secure, and the AI Question
Containers, monitoring, KQL, DevSecOps, FinOps — and three classes on AI as infrastructure, not theory.
Phase FiveProof & Payoff
Build the receipts, then go get hired: three portfolio capstones you can hand an interviewer, and the class on turning them into an offer.
Three capstones. Three résumé lines with receipts attached.
Each is a public repository, a grading rubric, and a sheet listing precisely what an interviewer will ask you about it. Nothing here is a toy.
The Enterprise Web Platform
A three-tier application delivered entirely through pipelines — infrastructure as code, an approval gate before production, secrets in a vault, a budget watching the bill.
The Miniature Landing Zone
Governance before workload: management groups, policies that deny rather than warn, hub-and-spoke networking, an access model written as code rather than folklore.
The AI Workload
An internal assistant on Azure OpenAI behind a private endpoint, rate-limited at the gateway, its infrastructure shipped by the same pipeline as everything else.
Anyone can verify it against a public registry.
The three capstones above are the proof you can do the job; the certificate is the receipt. Finish all 42 classes and you earn one — stamped with a unique ID anyone can check against a public registry, so it can't be faked or claimed by someone who didn't do the work.
Not just classes — the practice and assets that get you hired.
The forty-two classes teach it; these keep you sharp and land the job. Same track, same price — nothing.
Exam practice
Timed question banks for AZ-900, AZ-104, AZ-400 and more — drawn from the course's own drills.
Sit a paper → Hands-onAutomation practice
Write the real scripts a cloud engineer runs — Azure CLI, Bash, PowerShell, Python.
Open the bench → Get hiredInterview
The questions panels actually ask — plus senior scenarios with model answers.
See the bank → AssetOn the job
Survive and shine in your first 90 days — the playbook for the role you just landed.
Read the kit → Get hiredJob-search plan
A dated, week-by-week 6-month job-search plan you run while you learn — when to apply, weekly targets, a referral playbook.
Open the plan → Get hiredSkills radar
The skills showing up in real Azure, cloud and DevOps postings right now — each mapped to the class that teaches it.
Read the radar → AssetRésumé
ATS-safe single-column templates with one-click PDF, Word and Google Docs export.
Build yours →I run this in production. Now I'm handing it to you.
I'm Captain O — a Senior Azure Cloud & DevSecOps Engineer. Nine years in enterprise IT, six of them spent entirely on Azure. I build the platforms that keep production running: zero-trust architectures, self-service landing zones, and pipeline frameworks that teams actually adopt.
I didn't start in a data center — I started in a cockpit. Trained as a helicopter pilot, I learned the habits that quietly define good cloud engineering long before I wrote a line of Terraform: run the checklist every time, respect the failure modes, and never trust a system you haven't tested under load. A hard landing is unforgiving; so is a Friday deploy. That same instinct — stable by default, no surprises in production — is how I build Azure platforms now.
I built CAMPUX because I kept meeting people who did everything right — passed the certs, ground through the tutorials — and still got told to “come back when you have experience.” Certified, still not hired. I couldn't fix the whole industry, but I could hand people the exact work I do in production — for free — so they walk into interviews with proof instead of promises.
That's the whole reason this site exists: to close the gap between certified and hired. Every class here is reverse-engineered from real work — not from a syllabus, from the job.
Captain O
Proof you can read today: the labs he ships are public — github.com/kloudcaptain/campux-labs.
Certified and hired.
Learners who did the work, shipped the proof, and landed the role — in their own words. Every one reviewed before it's posted.
Not sure you're ready? Take the honest job-ready check and see exactly where the gap between certified and hired is.
Everything here is free. Two optional paid desks exist for people who want a person on top of the pages — the Live Desk and the Application Desk — optional human help alongside the free course. Nothing on the site is locked behind them; every class, lab, and drill stays free without either one.
Get every update
and its build rubric.
Sign the card and you'll get one notice when something new lands — the practice-lab walkthroughs rolling out now, plus the build rubric an interviewer would grade you against. Nothing else, ever.
New classes & updates
No advertisements. Unsubscribe anytime.
Read Class One.
Judge it yourself.
Read Class One →
Forty-two classes · seven builds · three capstones on the table
