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 — 40 classes, each one closing that gap, ending in three production repositories you put on the table instead of a certificate.
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 took the posting on the right — the composite of what keeps appearing in mid-level Azure engineer listings — and treated it as a specification. Every requirement was traced to the classes that satisfy it. Nothing was included because it was interesting. Several things were cut because they were.
The two lines circled in red are where most self-taught candidates fail the technical screen. They are given nine classes and a full phase of this bootcamp.
In this trade the build is the examination. Read the class, sit the drills, then produce the artifact. A phase is not complete until the artifact exists in a repository with your name on it.
What the cloud actually is, the Azure resource hierarchy, identity in Entra ID, role-based access, policy, and managed identity — the governance instincts that separate an engineer from someone clicking through a portal.
Virtual networks, compute, storage, load balancing, private endpoints, DNS, and what the Azure portal is actually doing to the Resource Manager API on your behalf. This is the depth most self-taught engineers are missing.
Git, branching strategy, Bicep and Terraform, GitHub Actions federated to Azure without a single stored credential, environments, approvals, runners, scripting. This phase is the difference between two salary bands.
Containers, Azure Monitor, KQL, alerting that people don't learn to ignore, DevSecOps hygiene, FinOps discipline, and three classes on AI — how the systems actually work, then real infrastructure: private networking, quotas, and token cost. Infrastructure lens only. No machine learning theory.
Below is an unedited drill from Class One. Choose an answer; the marking appears with reasoning, the way a good instructor would talk you through it rather than simply crossing you out.
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 →
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, federated authentication, an approval gate before production, zero-downtime slot swaps, secrets in a vault, telemetry flowing, and a budget watching the bill.
Governance before workload: management groups, policies that deny rather than warn, hub-and-spoke networking with private resolution, centralised logging, and an access model written down as code rather than folklore.
An internal assistant on Azure OpenAI, reachable only through a private endpoint, rate-limited at the gateway, its token spend charted on a dashboard, its infrastructure shipped by the same pipeline as everything else.
Class One is open to anyone, right now, with no account and no card. If it earns your attention, sign the card and you'll get one notice each time a new class releases or an existing class is updated — with the build rubrics attached.