Skip to content
CAMPUX Cloud Bootcamp
Field notes · Careers
Passed AZ-900, No Interviews

You passed the AZ-900 and still aren't getting interviews. Here's why.

By Captain O7 min read

You studied for weeks, sat the exam, saw the pass screen, and updated your profile that night. Then the applications went out and nothing came back. It stings, and it is worth being honest about what the cert did and did not buy you.

New to cloud? CAMPUX is a free, build-first course. Start here →

Here is the uncomfortable part first: the AZ-900 is a foundations exam. Microsoft designs it to prove you can describe cloud concepts and core Azure services, and it calls the credential "a common starting point in a journey towards a career in Azure." Read that carefully. It is a starting point, and it measures whether you can describe things. Nobody gets paid to describe Azure. They get paid to build it, run it, and fix it at 2am when a deployment fails. AZ-900 does not test any of that, and hiring managers know it, which is why the pass alone rarely moves the needle for an engineering role.

AZ-900 shows awareness, not ability; a role-based cert plus real projects is what starts the interviews.why it stallswhat changes itresume:• AZ-900 (foundations)• "studying Azure"• no hands-on to showawareness, not abilityresume:• AZ-104 (role-based)• 2–3 real projects• portfolio + outcomesproof they can hirerewrite the resume around what you built, not the badge
Figure 1 — The AZ-900 proves you know the vocabulary, not that you can build anything, so on an engineer resume it rarely moves the needle by itself. The resumes that start getting interviews trade "studying Azure" for a role-based cert, two or three real projects, and a portfolio — and are rewritten around outcomes you produced rather than the badge you earned.

What the AZ-900 actually signals

The exam is 45 minutes and covers three areas: describe cloud concepts, describe Azure architecture and services, and describe Azure management and governance. It is a vocabulary test. Passing it tells an employer that you know what a virtual network is, that you can explain the shared responsibility model, and that you understand roughly how billing works. That is genuinely useful — it means a manager does not have to teach you the words before teaching you the work.

What it does not signal is the thing a junior cloud job is about: can you log into a portal, stand up resources, wire them together, and troubleshoot them when they misbehave. It says nothing about whether you have ever touched the Azure CLI, written a line of Bicep, or debugged a failed deployment. For non-engineering roles that sit next to the cloud — support, technical sales, account management — the vocabulary can be enough. For the junior admin or cloud engineer seat you are probably aiming at, it is the price of entry, not the ticket. I wrote more about that trade-off in is the AZ-900 worth it, and the short version is: worth it as a first step, oversold as a finish line.

Nobody gets paid to describe Azure. They get paid to build it and fix it.

Why the resume stalls

Two things are usually happening at once. The first is a supply problem. AZ-900 is the most-taken Azure exam on earth, so a huge share of the entry-level pile holds the same badge you do. It gets you past an automated keyword filter and then puts you shoulder to shoulder with thousands of people who look identical on paper. Nothing about the cert makes you the obvious pick.

The second is a story problem, and this one you control. Most stalled resumes are built around the certificate instead of around outcomes. The document reads like a transcript: a list of exams passed, courses finished, topics studied. A hiring manager scanning it for six seconds learns what you consumed, not what you can produce. Flip it. A line that says "built a three-tier web app on Azure with a private database and a firewall, scripted end to end in Bicep" tells them you can do the job. A line that says "passed AZ-900" tells them you read about the job. Same candidate, completely different signal.

The tell that sinks entry-level resumes

If a stranger reads your resume and cannot name one thing you built, the resume has failed, no matter how many certs are on it. Certs belong in a small line near the bottom. The top third should be projects with outcomes: what you built, what it does, and a link to the code or a write-up. If you cannot fill that top third yet, that is the real gap — and it is fixable in a few weekends, not a few years.

The next moves, in order

You have four levers, and pulling them in this order works better than doing them at random.

Go role-based with AZ-104. The natural step up is the Azure Administrator Associate. It is not another vocabulary test — Microsoft expects hands-on experience with virtual networks, storage, compute, identity, security, and governance, and the exam assesses you on managing and deploying real resources. It also maps to a job title employers really do post: Azure Administrator. If your target is development instead, AZ-204 is your branch; if it is security, look at SC-900 then SC-200. For most people reading this, AZ-104 is the one that changes how recruiters read your profile.

Build two or three real projects. Open a free Azure account and make things. Deploy a small app with a database. Put it on a private network behind a firewall and connect to it properly. Script the whole thing with the CLI or Bicep so it stands up from nothing with one command. Break it on purpose and fix it. These are not toy exercises — they are the exact tasks a junior admin does in week one, and doing them now is how you get the experience the job posting demands before anyone has hired you.

Turn the projects into a portfolio. A project nobody can see does not count. Push the code to GitHub, write a short README for each build that explains the goal, the architecture, what went wrong, and how you solved it. A screenshot and a diagram go a long way. This is the proof that separates you from the identical AZ-900 pile — evidence a stranger can click through and verify.

Rewrite the resume around what you built. Now the resume has raw material. Lead with the projects and their outcomes, keep the certs as a supporting line, and target roles that match your level rather than reaching three rungs up. If you want a structure to copy, the résumé templates are built exactly this way, and the full sequence of applying, following up, and interviewing is laid out in the job-search plan.

The takeaway

The AZ-900 did its job. It gave you the language of the cloud and got you through the door of the vocabulary. It was never going to get you interviews by itself, because it does not answer the only question a hiring manager cares about: can this person do the work. You answer that with a role-based cert that assumes hands-on skill, a small stack of real projects that prove it, a portfolio that lets a stranger check, and a resume that leads with what you built instead of what you studied. Do those four things and the same AZ-900 on your profile stops being background noise and starts being the first line of a story that ends in a callback.

Questions people also ask

Can you get a job with just the AZ-900?

Sometimes, but rarely for an engineering role. AZ-900 is a fundamentals cert that shows you understand cloud vocabulary, so it can help for cloud-adjacent support, sales, or account roles. For a junior cloud or Azure administrator job, hiring managers expect evidence you can build and troubleshoot something, which AZ-900 does not provide on its own.

Is AZ-900 enough to get an interview?

On its own, usually not, because thousands of applicants hold it and it signals awareness rather than skill. It gets you past a keyword filter, then a resume with no projects and no outcomes stalls next to candidates who show real work. Pair it with two or three hands-on projects and the same cert starts pulling interviews instead of silence.

What certification should I get after AZ-900?

For most people it is AZ-104, the Azure Administrator Associate. It is role-based, it maps to a real job title employers hire for, and it forces you to work with virtual networks, storage, compute, identity, and governance rather than just describe them. If you are aimed at development choose AZ-204, and if security is your target look at SC-900 then SC-200.

How do I get cloud experience with no job?

Build things in a real Azure account and document them. Deploy a small web app with a database, wire up networking and a firewall, script it with the CLI or Bicep, then write up what you built, what broke, and how you fixed it. Two or three of these projects, published with diagrams and code, become the experience your resume is missing.

Why am I getting no interviews with cloud certifications?

Almost always because the resume is built around certificates instead of outcomes. A list of exams tells a hiring manager what you studied, not what you can do. Rewrite each line around something you built or fixed and its result, add a portfolio link, and target roles that match your level. The certs then support the story rather than being the whole story.

Further reading — the Microsoft docs
Your next class · free
You've read the idea. Class 42 — Landing the Job is where you build it, hands-on — no account needed.Start Class 42 →
Captain O
Founder & instructor · CAMPUX Cloud Engineering Bootcamp
Back to all field notes →