👨🏻 Brother Talk — Phase 00, Off the Record

No slides, no certification rubric. This is me, your brother, telling you the things people only say after the second coffee. Read it once now, and again the week before your interview.

Listen. You've probably been told that becoming a principal Azure engineer means collecting certifications — AZ-104, then 204, then 305, 500, 700 — and then you're "principal." It doesn't work like that. I've watched people with the full alphabet of badges still get stuck at senior, because nobody told them the secret:

The portal is the easy part. The judgment is the job.

Here's the thing that took me too long to learn. When a director says "architect our Azure platform," they are not testing whether you know which blade to click or which az flag to pass. They assume you can find the button. What they're watching is: do you compose the SLA before you promise four nines? Do you say "that's 4 minutes a month, here's the multi-AZ that buys it and here's the bill"? Do you name the pillar you're trading instead of hand-waving "it'll be reliable and cheap"? That move — pricing a tradeoff out loud — is the whole game. Everyone else in the room is reciting service names. You're doing engineering.

So let me give you the mindset shifts, brother to brother.

Internalise that there's one front door, and it changes everything. The single most freeing realization in this whole track is that every Azure write — VM, role assignment, policy, private endpoint — is the same shape: an idempotent PUT to a resource ID through ARM. Once you hold that, the 15 services ahead stop being 15 manuals. Each one is just "what does this provider do after ARM hands it the request, and what's its data plane?" People who never grasp this learn Azure as a thousand disconnected portal recipes and drown. People who grasp it learn one system with fifteen plugins. Be the second kind. That's what this phase is for.

Stop saying "highly available" and "scalable." I mean it — those words are banned for you now. Every time you want to say "highly available," say a number: "99.99 %, which is 4.32 minutes a month, composed from a zone-redundant data layer." Every time you want to say "scalable," say "sized to 6× average, sheds load via the rate limiter past that." The moment you do this you sound three levels more senior, because you've revealed that availability is a budget you compose, not an adjective you sprinkle. A junior wants everything multi-region. A principal knows multi-region is the most expensive nine on the menu and orders it only where a region outage is actually in the threat model.

Fall in love with the boring pillar: operational excellence. Everyone optimizes performance and reliability because they benchmark well and demo nicely. Nobody brags about "this is easy to debug at 2 a.m." But operability is the pillar that decides whether your platform survives, because a system runs for years and gets debugged thousands of times. The "elegant" private-endpoint-everywhere design that takes a DNS PhD to troubleshoot is a liability. The boring design any on-call can reason about is an asset. Choose boring on purpose — it's a flex, not a compromise. (And when the WAF review asks you to score it, the boring one quietly wins the operational-excellence pillar that everyone else forgot to weight.)

Learn the control-plane/data-plane split until it's reflex. This is the one that makes you look senior in seconds. The moment someone says "I'm an Owner but I'm getting 403 on the blob," and you say "right, Owner is control plane — you need a data role like Storage Blob Data Reader, or you're falling back to the account key" — you've just diagnosed in one breath what others debug for an hour. It's not because you're smarter. It's because you hold one distinction they never internalized. Collect distinctions like that. They're the whole signal.

Write the ADR even when nobody asks. Here's a career hack that feels like overhead and pays off enormously: when you make a real architecture call, write the one-pager — context as numbers on the five pillars, the decision, the alternatives, the deciding pillar, and what would change your mind. Do it even for decisions nobody requested documentation for. Six months later when someone asks "why are we single-region?", you don't defend it from memory and emotion — you point at the doc and say "here was the composed SLA and the cost; have the numbers changed?" You become the person whose decisions are legible. That person gets trusted with bigger decisions. That's the ladder, and it's quieter and surer than chasing another badge.

The honest truth about this role's difficulty: it's hard because it's wide, not because any one piece is deep beyond reach. Nobody is born knowing ARM and Entra and networking and Service Bus and Durable Functions. The people who got here didn't have bigger brains; they had a framework — one control plane, one address space, five pillars, two SLA formulas, a three-term bill — that let them absorb each new service as "oh, this is the messaging slot, here's its data plane, here's how it scores on the pillars." That framework is this entire phase. Internalize it and the other 15 phases stop being 15 unrelated services and become one platform you already understand.

One more thing, and it's the most important. You don't have to be the smartest person in the room to be the principal in the room. You have to be the one who turns vague fear — "will this scale? is this secure? what will it cost?" — into specific, answerable questions with numbers attached. Calm comes from numbers. When the room is panicking about "can this survive a region outage," and you say "the data layer can't replicate that far without breaking consistency, so active/active is off the table; here's the multi-AZ that gets us 99.99 % and here's the egress cost if we want DR to the paired region" — you're not smarter than them. You just did the arithmetic they were too anxious to do. That's leadership in this job. It's learnable. It starts with the lab in this phase.

Go build the modeler. Then come find me in Phase 01 — that's where we make the deployment graph and idempotency click, the stuff everyone name-drops and quietly doesn't understand.

— your brother 👨🏻