You watched the tutorials. You passed the exam. And the interview still 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. Class One is open with no account, no email — read it and judge for yourself; a free sign-up continues the rest.
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.
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.
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.
Resource hierarchy, identity, RBAC, policy — the governance instincts that separate an engineer from someone clicking through a portal.
Networks, compute, storage, private endpoints, DNS — the depth most self-taught engineers are missing.
Bicep and Terraform, GitHub Actions federated to Azure without a single stored credential. This phase is the difference between two salary bands.
Containers, monitoring, KQL, DevSecOps, FinOps — and three classes on AI as infrastructure, not theory.
Build the receipts, then go get hired: three portfolio capstones you can hand an interviewer, and the class on turning them into an offer.
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.
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.
Governance before workload: management groups, policies that deny rather than warn, hub-and-spoke networking, an access model written as code rather than folklore.
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.
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.
The forty-two classes teach it; these keep you sharp and land the job. Same track, same price — nothing.
Timed question banks for AZ-900, AZ-104, AZ-400 and more — drawn from the course's own drills.
Sit a paper → Hands-onWrite the real scripts a cloud engineer runs — Azure CLI, Bash, PowerShell, Python.
Open the bench → Get hiredThe questions panels actually ask — plus senior scenarios with model answers.
See the bank → AssetSurvive and shine in your first 90 days — the playbook for the role you just landed.
Read the kit →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 — and they unlock nothing.
Sign the card and you'll get one notice per release — the new class, plus the build rubric an interviewer would grade you against. Nothing else, ever.
Forty-two classes · seven builds · three capstones on the table