Certifications that actually matter

Cloud certifications are a reasonable signal and a poor proxy. They tell you someone has covered a defined body of material and passed an exam on it. They do not tell you whether that person has run anything in production, made a bad decision and had to live with it, or been on call when it failed.

Used carefully, they help. Used as a filter, they screen out good engineers and let through people who are good at exams.

What the levels actually mean

Both major platforms structure certifications similarly, and the shape is worth understanding.

Foundational certifications cover concepts and terminology. They are genuinely useful for people who work near cloud without building on it: project managers, procurement, account managers, sales engineers. They are not a meaningful signal for an engineering role.

Associate certifications cover practical use of the core services. This is the level where the material starts to correspond to the work. An associate-level certification suggests someone can find their way around the platform and knows what the common services do.

Professional and expert certifications cover architecture and design, usually with scenario-based questions and significantly harder exams. They demand a broader view (cost, resilience, migration strategy, operational trade-offs) and are harder to pass without real exposure.

Specialty certifications cover a domain in depth: networking, security, data, machine learning. These are the most informative, because the material is narrow enough that passing implies genuine familiarity.

Mapping certifications to work

Rather than asking which certification is best, ask what the role actually needs.

Building and running workloads day to day. An associate-level certification on the relevant platform is a fair baseline. It suggests the person knows the service catalogue and the common patterns.

Designing an estate or leading a migration. The professional or expert architecture certification is the relevant one. The material covers exactly the trade-offs the role requires.

Network design, hybrid connectivity, complex routing. The networking specialty. This is one of the few certifications that is difficult to pass without having done the work, which makes it a stronger signal than most.

Security engineering in cloud. The security specialty on the relevant platform. Note that it covers platform security specifically, not security generally. It is not a substitute for broader security experience or a vendor-neutral qualification.

Data platform work. The database or data specialty, depending on the platform's naming.

What a certification does not tell you

Whether they have operated anything. Exams test design and configuration knowledge. They do not test what someone does at two in the morning when the runbook does not match reality.

Whether they can work within constraints. Certification material assumes a greenfield where the recommended approach is available. Most real work happens inside a legacy estate where it is not, and the skill is finding the acceptable compromise.

Whether it is current. Certifications expire, but the underlying knowledge decays faster than the certificate does. Someone certified two years ago who has not touched the platform since knows less than the date suggests.

Whether they can explain it. Multiple-choice exams do not test communication, and a large part of senior cloud work is explaining a trade-off to someone who will fund it.

How to use them when hiring or buying

As a filter for a shortlist, not a requirement. Requiring a specific certification removes experienced engineers who never bothered and admits people who studied for it. Treat it as one input.

As a starting point for a conversation. The most useful interview question about a certification is not what it covered but what surprised them, or what they have since found to be wrong or oversimplified in practice. Someone with real experience will have an answer immediately.

As a check on partner claims. When buying from a provider, certifications held by the organisation are a different signal from certifications held by the people who will actually do your work. Ask specifically about the team assigned.

For your own team

If you are deciding what to fund, a few things make certification programmes worth the money.

Tie it to work that is coming. Certification taken shortly before doing the work sticks. Certification taken speculatively fades.

Prefer specialty over breadth for experienced engineers. Someone who has run the platform for three years learns more from the networking or security specialty than from a general architecture exam covering material they already use daily.

Do not treat the certificate as the outcome. The point is the knowledge, and the exam is a deadline that makes people study. Pair it with something real (a design review, a proof of concept, a piece of the estate to improve) so the knowledge lands somewhere.

Budget for the renewal. Certifications expire on a cycle. A programme that certifies everyone once and never again produces a team whose credentials quietly stop being true.

The short version

Associate level suggests familiarity. Professional and expert levels suggest breadth and design judgement. Specialty certifications are the strongest signal because the material is narrow enough that passing is hard to fake.

None of them substitutes for asking someone to describe something that went wrong and what they did about it. That question tells you more in five minutes than a list of credentials does.