AWS certifications are among the most commonly listed credentials in cloud and engineering resumes. But most recruiters treat them as a binary — either the candidate has one or they don't. The reality is more nuanced, and understanding what each level actually means will make you a significantly better judge of cloud talent.
The Three Levels of AWS Certification
AWS structures its certifications into four tiers: Foundational, Associate, Professional, and Specialty. Each represents a meaningfully different level of demonstrated competency.
- AWS Certified Cloud Practitioner (Foundational)
This is an awareness-level certification. It validates that someone understands what AWS services exist and roughly what they do — not that they can use them. For a non-technical role (sales, product, management) this is meaningful. For a technical hire, it tells you very little about hands-on ability.
- AWS Certified Solutions Architect – Associate (SAA-C03)
This is the most common certification you'll encounter. It tests the ability to design distributed systems on AWS — choosing between services, understanding networking, storage, compute, and cost optimization. A candidate who passed this within the last two years has real, usable cloud architecture knowledge.
- AWS Certified Solutions Architect – Professional (SAP-C02)
This is genuinely hard. It requires deep knowledge of multi-account strategies, complex migrations, advanced networking, and organizational design at scale. Candidates with this cert are senior-level cloud architects, not generalists.
- Specialty Certifications (Security, ML, Advanced Networking, etc.)
These are deep dives into specific domains. A Security Specialty cert, for example, tests threat modeling, IAM, GuardDuty, and compliance frameworks at a level beyond the associate track. These signal a specialist, not a generalist.
What the SAA-C03 Actually Tests
Since the AWS Solutions Architect Associate is what you'll see most often, it's worth knowing what the exam actually covers. The current version (SAA-C03) focuses on four domains:
- Designing secure architectures (IAM policies, encryption, VPC isolation)
- Designing resilient architectures (multi-AZ deployments, Auto Scaling, failover)
- Designing high-performance architectures (caching, read replicas, CloudFront)
- Designing cost-optimized architectures (Reserved vs On-Demand, S3 storage classes)
A candidate who scored well here can design a production-grade system on AWS. That's a meaningful signal.
Red Flags to Watch For
Not every AWS certification on a resume is equally credible. Watch for these patterns:
- No date listed. AWS certifications expire every three years. A cert with no date may be stale or lapsed.
- Certification spam. A resume listing 8+ AWS certifications in a two-year period often indicates exam-chasing rather than genuine experience. Real cloud engineers certify as their work demands it.
- Cloud Practitioner only, for a technical role. This is frequently listed to pad credentials. For an engineer position, it's not meaningful.
- No corresponding work history. If someone has the Solutions Architect Professional cert but their work history is all on-premise sysadmin, ask how they got hands-on practice.
How to Use This in a Phone Screen
Rather than asking "tell me about your AWS experience," try these questions based on what the certification actually covers:
- "Walk me through how you'd design a system to handle an unpredictable traffic spike on AWS."
- "What's the difference between using RDS Multi-AZ versus Read Replicas?"
- "How would you reduce costs on a system that's running EC2 On-Demand 24/7?"
If the candidate has genuine SAA knowledge, these are approachable questions. If they struggle, the certification may not reflect their current ability.
Let AI Do the Heavy Lifting
Manually researching every certification on every resume isn't realistic at volume. RecruiterSignal automatically explains what each certification means in context — whether it's credible, whether the expiry matters, and whether it matches the seniority of the role. You get a complete credential briefing without needing to know AWS inside out yourself.