§1
The five phases, one line each
Every phase had a job, and each job was the ground the next stood on. Read them as one sentence and the whole bootcamp is visible at once: govern it, build it, automate it, operate it, and prove it.
- Phase One · Foundations
- What the cloud is, when not to use it, and how to govern an Azure estate before it grows. Sealed by Build I — a governed subscription. Recap →
- Phase Two · Core Infrastructure
- Networks, compute, storage, and a private data path — the depth most self-taught engineers miss. Sealed by Build II — a private application. Recap →
- Phase Three · The DevOps Core
- Git, infrastructure as code, and a pipeline that plans on a pull request and deploys on merge with no secret. Sealed by Build III — a GitOps loop. Recap →
- Phase Four · Operate, Secure & AI
- Containers, observability, security, cost, AI as infrastructure, event-driven messaging and serverless functions, and the operations that keep it alive. Sealed by Build IV — eyes and guardrails. Recap →
- Phase Five · Proof & Payoff
- The three capstones that use all four phases at once, and the class that turns them into an offer. You are here.
§2
What the certificate can't show
A certificate says you passed a test. These five instincts — one from each phase — are what it cannot prove and your builds can. They are the difference the whole bootcamp exists to make.
- Govern before you grow
- An estate is laid out for control first, capacity second — because ungoverned growth cannot be governed later without pain.
- Segmentation is trust, decided in advance
- Networks, identities, and scopes are walls you build on purpose, so a single compromise stays a single compromise.
- If it isn't in Git, it doesn't exist
- Every change is a reviewable diff; every environment is a template; nothing important lives only in a click or a memory.
- Guardrails, not reports
- Security and cost are controls in the path — a policy that blocks, a budget that warns — not a spreadsheet read after the damage.
- Evidence, not effort, is the deliverable
- The half a stranger can inspect is the half that counts. A build with your name on the commits outweighs any claim about hours studied.
Evidence, not effort, is the deliverable.
§3
What you can now honestly claim
The full shape of a junior-to-mid cloud engineer, assembled from four phases. Every line is something an interviewer can ask you to prove — and now something the capstones let you.
| You can… | From |
|---|---|
| Lay out and govern an Azure estate — hierarchy, least-privilege RBAC, deny policy, managed identity | Phase One |
| Design the infrastructure beneath a workload — segmented network, right-sized compute, priced storage, a private data path | Phase Two |
| Put all of it in code and ship it through a reviewed, secretless pipeline | Phase Three |
| Run it in production — containers, observability, security, cost control, AI infrastructure, event-driven messaging and serverless, incident response | Phase Four |
| Hand an interviewer three production repositories and walk them through every decision | Phase Five |
Case File · Campux Retail
The estate, from empty tenant to running system
The whole arc, through one client
You watched Campux go from a shop that "wanted to move to the cloud" to a governed, networked, automated, operated Azure estate — one class at a time. Every build was that estate under your own hands, and the capstones are where it becomes portfolio: three repositories that exist, that work, and that carry your name. The bootcamp opened on an interview that died at one sentence. The capstones are why it will not die at yours.
§4
In your head
Five questions, each spanning the whole course — the kind an interviewer uses to tell reading from doing. Answer each in your head, aloud if you can, before you open the thread. These are the ones worth rehearsing until they are reflexes.
"Walk me through something you've built." You have sixty seconds. Where do you start, and what makes the answer land?
The thread · Phases One–FiveStart at one capstone and narrate top-down: the governance it sits on, the network beneath it, the pipeline that ships it, the guardrails that watch it. What makes it land is that every noun is inspectable — a repository, a deploy, a policy that refused something — not a claim. Evidence, walked through.
A workload needs a secret to reach a database. Trace how you would make sure that secret never leaks — from the identity to the pipeline that deploys it.
The thread · Phases One & ThreeThe app uses a managed identity, so there is no stored secret at runtime (Phase One). The pipeline that deploys it authenticates to Azure with OIDC federation, so there is no stored secret in CI/CD either (Phase Three). The same instinct — remove the credential entirely — applied at both layers.
You are handed a new Azure subscription and told "make it production-ready." Name the first four moves, in order.
The thread · Phases One, Two, Three, FourGovern it (hierarchy, RBAC, deny policy), lay the network (segmented VNet, private endpoints), put it in code behind a reviewed pipeline, then wire the eyes and guardrails (a KQL alert, a budget). Governance first, observation last — the order the whole bootcamp taught.
The bill jumped this month and nobody can say why. Walk the path from "surprise" to "controlled," using what you learned across phases.
The thread · Phases Two & FourRead Advisor and the cost view to find the driver (Phase Four FinOps), check for oversized compute or hot storage that should be cool (Phase Two), and put the control in the path so it cannot recur — a budget alert, a lifecycle rule, a per-consumer throttle. The fix is a guardrail, not a one-time cleanup.
An interviewer asks the question the whole bootcamp was built to answer: "Why should we hire you over someone with the same certificate?"
The thread · Phase FiveBecause a certificate is a claim and you brought receipts: three production repositories an interviewer can open, each one governed, networked, shipped, and operated — with the decisions written down. Certified is the floor. Built is the answer.
Notes
- This is a recap of the whole bootcamp, not a single phase — Phase Five's "content" is the three capstones and the class on landing the job, so its review looks back across all four phases that feed them. ↩
- If any capability in §3 does not yet feel true, that is not failure — it is a pointer. The phase that teaches it, and its recap, are one click up, and the capstone that exercises it is one click down. ↩
Turn it into an offer
Your résumé & interview toolkit