Certified, But Not Job-Ready
I hold nine AWS certifications, so take this as said by someone who thinks they are worth having: we have confused being certified with being ready to do the job, and that confusion costs people months. The strange part is that AWS has never claimed otherwise. The case against treating a badge as proof of readiness is written on Amazon's own policy page. This essay reads what the exam guides actually say, shows what the exam measures and what it never claimed to, and ends with the work that turns a certification into evidence. The exercises save in your browser as you go.
The badge arrives. The LinkedIn post does well — better than anything you've posted in a year. Then the week passes, and the applications you sent with “AWS Certified” newly in the headline come back the same way the ones before them did. Nobody tells you what's missing, so the obvious conclusion is that one certification wasn't enough.
I want to be careful here, because the advice that follows is usually delivered by people with nothing invested in the thing they're dismissing. I have nine. They gave me structure when I had none, a vocabulary for talking to engineers, and something measurable to aim at when nothing else about the transition was measurable. I'd recommend them to anyone entering cloud. None of that is in question.
“There is no true substitute for experience.” That is not my line. It is AWS, on its own certification policy page, under its own heading about recommended experience [1]. The company that sells the exam says the exam does not replace the thing you're hoping it will replace.
Read what AWS says about its own exams
Almost nobody does this, and it takes ten minutes. Every AWS exam guide opens with a section called Target candidate description, and it is the most honest description of a certification's limits you will find anywhere. For the Solutions Architect – Associate it reads:
The target candidate should have at least 1 year of hands-on experience designing cloud solutions that use AWS services.
— AWS Certified Solutions Architect – Associate (SAA-C03) exam guide [2]
Read that as the exam's authors intended it. The paper was not designed to prove you can do the work. It was designed to be taken by somebody who already does the work, as a way of validating what they know. Everything that feels wrong about passing it from a standing start — the sense that you have a credential for a job you've never done — is not a flaw in you. It is the exam being used outside the population it was written for.
One thing I have to be exact about, because the internet usually isn't: these are recommendations, never requirements. AWS is explicit that “All AWS Certifications may be earned without completing specific prerequisites” [1]. Nobody is checking. The recommendation is advice about whether the exam will mean anything, not a gate.
The Cloud Practitioner guide is the interesting counterexample, and it cuts the other way. Its target candidate has “up to 6 months of exposure to AWS Cloud design, implementation, and/or operations” [3] — a ceiling, not a floor. That exam genuinely is built for people starting cold, and if it is your first, nobody is suggesting you should have had a year of experience first. What that guide does do is list, in writing, the tasks its candidate is not expected to be able to perform:
- Coding
- Designing cloud architecture
- Troubleshooting
- Implementation
- Load and performance testing
The entry-level AWS certification states on its own exam guide that troubleshooting, implementation and architecture design are out of scope. Those three are most of what the job is. Nobody is hiding this — it's on the page, and almost nobody reads it before deciding the certification will make them employable.
What the Solutions Architect exam actually measures
The guide publishes its four domains and their weightings. Look at the verbs rather than the nouns [2]:
- Design Secure Architectures — 30% of scored content
- Design Resilient Architectures — 26%
- Design High-Performing Architectures — 24%
- Design Cost-Optimized Architectures — 20%
Four domains, one verb. Nothing in the exam's own description of itself claims to measure building, operating, or recovering. AWS's product page for the same exam adds, plainly, that “This exam does not require deep hands-on coding experience” [2]. The certification is doing exactly what it says. The mismatch is entirely in what we read into it.
It can test whether you recognise a highly available architecture.
It can test your understanding of IAM policy evaluation.
It can test which service is cheaper for a given workload.
It can test the right answer among five.
Since your last certification, what have you actually done with it?
The treadmill
You know the shape of it. Cloud Practitioner. Not ready, so Solutions Architect Associate. Passed — still not confident, so maybe Developer. Or CloudOps. Or Security. Months pass, and the collection grows while the evidence of what you can do stays exactly where it was.
I'm not going to pretend there's a magic number after which certifications stop counting; I have nine, which disqualifies me from that argument entirely. The problem was never the count. It is that the next certification is the most comfortable way to avoid the skill you haven't practised — it has a syllabus, a date, a price and a pass mark, and the thing you're actually avoiding has none of those. Studying feels like progress because it is measurable. That's exactly what makes it such a good hiding place.
Be honest about the next one you're considering. Which is it?
What job-readiness looks like, in six questions
Take an aspiring Cloud Engineer who has just passed the Solutions Architect Associate. Instead of booking the next exam, they build and deploy something small — their own decisions, not a tutorial's — and in doing so they have to answer six questions the exam never asked them.
Score yourself against something you have actually built. Tick only what you could answer today, out loud, without opening the console first.
Tick what you can defend under questioning — it saves as you go.
Notice that none of the twelve requires a job. Every one can be answered by somebody working alone on a weekend, and none of them can be answered by passing an exam. That gap — between what you can prove without employment and what a certification proves — is the whole of the problem and most of the solution.
A personal project is not professional experience and nobody should pretend it is: no customers, no deadlines, no teammates, no pager. The point is not to pass it off as a job. It is that the habits a job demands can be practised before you have one — and that a person who has practised them interviews like a different candidate.
The question to ask instead of “which one next?”
That's the question I'm asked most, and I think it's the second question. The first one is:
What can I do today that I couldn't do before I earned this?
Five follow-ups make it concrete, and they are roughly what an interview is made of. Can you design something independently? Can you implement it? Can you troubleshoot it when it misbehaves? Can you explain the trade-offs you accepted? And can you explain the whole thing to somebody who doesn't share your technical background — a manager, a client, a stakeholder who only wants to know what it costs and what happens if it breaks?
That last one is the quiet differentiator, and it's the one no exam has ever tested. It is also, in my experience of sitting on the other side of the table, the skill that most often decides between two technically similar candidates.
The honest counter-argument
I checked the evidence for this essay properly, and it would be dishonest to report only the half that agrees with me.
Certifications do gate real jobs. In ISC2's survey of 929 cybersecurity hiring managers, when asked which attributes were “critical”, certifications came out fractionally above IT experience — 47% against 44% [6]. Consultancies and partners often need certified staff to hold their partner status, which makes your badge commercially valuable to them in a way no project is. If a job advert names a certification, the certification is not optional, and no amount of portfolio craft substitutes for it.
And the strongest numbers against certifications come from people who sell them, which is the part worth knowing. The Linux Foundation found hiring managers rating hands-on experience extremely or very important at 73%, against 31% for certifications [4] — published by an organisation that runs a major certification programme, against its own commercial interest, which is precisely why it's the most credible figure in this essay. Pluralsight found 77% of executives had seen somebody complete training or earn a certification and still be unable to do the job [5] — from a company that sells hands-on labs, so read it knowing what it's selling.
The two publishers in this field with no commercial stake in certification at all — the UK government's skills research and Indeed's Hiring Lab — publish no figure on how much employers weight certifications. What the UK study does record, from recruitment agents, is “a sense of 'certification fatigue' among cyber security professionals due to the proliferation of paid certifications” [7]. Make of that what you will; I've reported it because leaving it out would have been the comfortable choice.
One more, because it reframes the entry question entirely. ISC2 asked 16,029 practitioners how they got into cybersecurity. IT experience was the route for 56%. Certifications were the route for 6% [8] — in a certification body's own workforce study.
The expiry nobody plans for
Here is the part the treadmill never accounts for. An AWS certification lasts three years [9]. After that you either retake the current version of the exam, which buys another three, or you keep it alive through AWS Skill Builder activities — which buys one year at a time and requires a paid subscription for as long as you want the badge to stay valid [9].
Now do the arithmetic on a collection. Nine certifications is not nine achievements sitting safely on a profile; it is a recurring obligation with a renewal calendar. I know, because it's mine.
And the ground moves underneath them. AWS has been shrinking its own Specialty range: six of them existed in early 2024, three were retired that April, Machine Learning – Specialty went in March 2026, and Advanced Networking retires on 31 December 2026 — leaving Security as the only Specialty certification from January 2027 [10]. AWS gave the reason itself:
We see the opportunity to serve our customers better by reducing the number of specialty certifications and enhancing our offerings at the foundational, associate, and professional levels.
— AWS Training and Certification blog, 30 January 2024 [10]
A certification rents its relevance: three years, renewable, and the vendor can retire the exam under you. The system you designed, broke, fixed and wrote up does not expire, cannot be retired by anyone else, and gets more valuable as you add to it. Both are worth having. Only one compounds.
Give the certification a purpose beyond the exam
So no, don't stop. I'd still recommend AWS certifications to anyone entering cloud, for the same reasons they worked for me: structure when you have none, concepts you would otherwise skip, a shared vocabulary, and credibility that opens some doors outright. Change the sequence, not the decision.
The usual loop: study → pass → study → pass → apply
The one worth running: choose a role → learn → certify → build → break → document → apply
You do not need to finish the loop before applying
The test of whether a certification had a purpose
A milestone, not a destination
If you've just earned your first certification, celebrate it properly — it was real work, done in evenings you could have spent otherwise, and most people who say they'll do it never do. And if you've earned several and still feel unprepared, I'd gently suggest the answer isn't a sixth. It's putting the five to work.
Certifications taught me what good engineering looks like. Building forced me to practise it — and to answer questions no exam had ever put to me, because the exam had already decided which five answers were on offer. Both earned their place in how I got here. They just did different jobs, and only one of them was ever going to be enough on its own.
Your badge says what you've studied. Your work says what you can be trusted with.
So what can you actually demonstrate right now?
The free capability check maps what you can show, capability by capability, against the role you're targeting — six levels from understanding a thing to operating it at scale — and names the specific evidence that would move you up. It answers the question this essay asks, including where a certification does and doesn't count. Free, no card.
Sources
Every figure was traced to its primary publisher. Where a statistic comes from an organisation that sells certifications, the note says so — that conflict runs through most of the data in this field, and it is part of the finding rather than a footnote to it.
- [1]“All AWS Certifications may be earned without completing specific prerequisites… There is no true substitute for experience.” AWS Certification, Before Testing policy page. aws.amazon.com/certification/policies/before-testing/verified
- [2]“The target candidate should have at least 1 year of hands-on experience designing cloud solutions that use AWS services.” Exam domains: Design Secure Architectures 30%, Design Resilient 26%, Design High-Performing 24%, Design Cost-Optimized 20% of scored content. AWS Certified Solutions Architect – Associate (SAA-C03) exam guide. The product page adds: “This exam does not require deep hands-on coding experience.” docs.aws.amazon.com/aws-certification/latest/solutions-archiverified
- [3]“The target candidate has up to 6 months of exposure to AWS Cloud design, implementation, and/or operations”, and the out-of-scope task list: coding, designing cloud architecture, troubleshooting, implementation, load and performance testing. AWS Certified Cloud Practitioner (CLF-C02) exam guide. docs.aws.amazon.com/aws-certification/latest/cloud-practitioverified
- [4]Hiring managers rating a factor extremely or very important when assessing technical skills: relevant hands-on experience 73%, portfolio of previous project work 52%, certification of skills 31%, formal degree 29%. Linux Foundation, 2026 State of Tech Talent Report. n=400, fielded February 2026, predominantly Europe and APAC. linuxfoundation.org/researchverified — published by a certification body, against its own interest
- [5]“77% of executives have seen an employee finish training or earn a certification and still be unable to do the job.” Pluralsight Tech Skills Report 2026, with Wakefield Research. 1,500 respondents across the US, UK and Australia, fielded June–July 2026; no separate base published for the executive subgroup. pluralsight.com/resource-center/reports/tech-skills-report-2verified — Pluralsight sells hands-on training; read it knowing what it sells
- [6]Among attributes rated critical: IT/cybersecurity certifications 47%, previous IT experience 44%, relevant education 43%. ISC2, 2025 Cybersecurity Hiring Trends. 929 hiring managers across six countries, fielded December 2024. isc2.org/Insights/2025/06/cybersecurity-hiring-trends-studyverified — ISC2 sells certifications; included because it argues against this essay
- [7]“Recruitment agents reported a sense of ‘certification fatigue' among cyber security professionals due to the proliferation of paid certifications.” DSIT, Cyber security skills in the UK labour market 2026, researched by Ipsos and Perspective Economics, published 29 September 2026. UK, cyber only. gov.uk/government/publications/cyber-security-skills-in-the-verified — no commercial stake in certifications
- [8]Primary route into a cybersecurity role: IT experience 56%; cybersecurity certifications 6%. ISC2 2025 Cybersecurity Workforce Study, n=16,029, fielded July–August 2025. isc2.org/researchverified
- [9]“You will be required to update your certification (or recertify) every three years.” Renewal by exam adds three years; maintenance through Skill Builder adds one year and requires an active paid subscription. AWS Certification FAQs and Recertification pages. aws.amazon.com/certification/recertification/verified
- [10]“We see the opportunity to serve our customers better by reducing the number of specialty certifications…” Pam Brown, AWS Certification retirements and launches, AWS Training and Certification blog, 30 January 2024. Machine Learning – Specialty retired 31 March 2026; Advanced Networking – Specialty retires 31 December 2026, leaving Security as the only Specialty certification from January 2027. aws.amazon.com/blogs/training-and-certification/aws-certificverified
- [11]Not included, deliberately: AWS exam pass rates. AWS publishes none for any exam — it publishes a scaled score range and minimum passing scores (700 Foundational, 720 Associate, 750 Professional and Specialty) set by a criterion-referenced standard. Every pass-rate percentage in circulation comes from training vendors, not from AWS. aws.amazon.com/certification/policies/after-testing/checked and excluded