Drawn from real Azure cloud-engineer job postings and the questions hiring panels reach for, categorised by topic — and every one mapped to the class that answers it, so a weak answer is one click from becoming a strong one.
This is not a memorisation list. Interviewers can tell a recited answer from an understood one in a sentence. Use each card two ways: cover the "what they're really testing" line and answer the question aloud, then read the line and the class it points to. The point is not to have the answer — it is to have built the thing the answer describes.
The warm-up round. Panels use it to sort people who memorised definitions from people who can reason about trade-offs — so answer with a decision, not a dictionary entry.
Where mid-level interviews get real. Identity is the security boundary of the cloud, and panels probe whether you grant the narrowest access at the lowest scope by instinct.
The depth most self-taught candidates are missing, and the panel knows it. Expect a whiteboard and "draw me the request path."
Bread-and-butter questions where the tell is cost-awareness: can you size to the workload rather than to fear?
The two-salary-band divide. Panels want to hear that your infrastructure is text, reviewed and reproducible — and that you can defend a tool choice with a rule, not a preference.
The questions with the sharpest right answers. One in particular — how the pipeline authenticates — separates candidates who store a secret from those who don't.
Where operational maturity shows. Panels want the person who reads the invoice like telemetry and whose pager means something.
Answer these with a posture, not a product list — the difference between naming a medicine cabinet and describing your health.
The market's vaguest requirement — "AI a plus" — and your chance to answer it with infrastructure instead of a chat window.
The round candidates underprepare and panels weight heavily. Answer in the shape of a real story — situation, action, result — and let your capstones supply the specifics.
"Do you have any questions for us?" is not the end of the interview — it is part of it, and the strongest candidates treat it as their own diligence. Good questions signal seniority and, just as importantly, tell you whether to accept the offer. Ask a few of these; then listen to how they answer, not only what they say.