There is no magic number — but there is a curation method. When more certifications help, when they hurt, and a five-question filter for deciding what stays.
Short answer: as many as directly support the job you are applying for — usually three to five for experienced professionals, and rarely more than six even for early-career candidates leaning on credentials. The right question is not "how many do I have?" but "how many does this application need?" Your resume is not a trophy cabinet; it is an argument, and every certification on it should be a piece of evidence for that argument.
Before we go further, a boundary note: there is no official standard for any of this. No certification body or recruiting authority publishes a "correct" number — what follows is editorial judgement about how selection works, built around one principle: relevance beats volume. This article deals only with how many and which. How to format each entry is covered in how to put certifications on your resume the right way, where the section should sit is covered in where certifications go on a resume, and lapsed credentials have their own guide.
It feels safe to include every credential you have ever earned — you worked for them, and surely more evidence is better? Three problems with that instinct:
Dilution. A reader scanning your certifications section gives it seconds. If your strongest, most role-relevant credential sits in a list of nine, it gets one-ninth of that attention. Curation is how you control what gets seen.
Signal confusion. A list that spans desktop support, digital marketing, project management, and cloud security does not read as "versatile" — it reads as undecided. Recruiters shortlist for a specific role, and a scattered list makes it harder to see you in it.
The perpetual-student read. A long credential list next to a thin experience section can suggest someone who collects exams instead of applying them. That downside case — what a bloated list signals and how to prune it — is dissected in when having too many certifications can hurt your resume, so we will not relitigate it here; the flip side, when stacking additional credentials genuinely adds employability, is covered in do multiple certifications make you more employable?
Run each certification you hold through these questions for each application. It stays on the resume only if it clears the bar.
If the posting names the credential or its subject area, it stays — full stop. Certifications named in job postings also matter for automated screening, since applicant tracking systems match on those keywords (how that filter works is its own topic).
A foundational credential earns its place early in a career and quietly retires later. If you hold an advanced certification in a domain, the entry-level one beneath it usually adds nothing — the advanced credential implies the foundation. Exception: keep a lower-level credential when it covers a different domain the role also touches.
One credential from a well-recognised provider outweighs several from providers a recruiter has to look up. When trimming, unrecognised issuers go first. If you are unsure how a given credential is regarded, browsing where it sits among providers in a certification exam directory can help you gauge whether it is a recognised industry exam or a niche course certificate.
Anything on the resume is fair game in an interview. If a certification is so old you could not survive five minutes of questions on it, either refresh before you apply or leave it off. (Formally expired credentials are a separate, wording-sensitive case — see the expired certification guide.)
Every kept credential should tell the reader something the others do not: a different domain, a higher level, a vendor the employer actually uses. Two certifications that prove the same thing are one certification and one line of clutter.
These are working heuristics, not rules — the filter above always wins over any number.
Career-changers and early-career candidates: 2–4. Credentials are doing heavy lifting here, standing in for experience you do not yet have, so they earn more space. Even so, they should converge on one target role. Three certifications pointing at the same career read as a plan; six pointing in six directions read as a search.
Experienced professionals: 2–5. Your experience section is now the main evidence; certifications corroborate it. Keep the ones that are current, senior, and relevant, and let superseded stepping-stones go. A fifteen-year veteran listing their earliest entry-level credential is answering a question nobody asked.
Highly certified specialists: cap the visible list, keep the rest elsewhere. If you legitimately hold ten relevant credentials — common in consulting and some security roles — show the strongest five or six and move the remainder to your LinkedIn profile or a portfolio page, which have no space constraints. A line such as "full list of certifications available on LinkedIn" loses nothing. Everything a resume drops can live on your professional profiles, where completeness is a virtue rather than clutter.
Regulated or compliance-driven roles: list every mandated credential, always. Where a licence or certification is a legal or contractual requirement for the role, it is not subject to curation. Trim around the mandatory ones, never among them.
A systems administrator with six years' experience holds seven credentials: an entry-level IT support certification, two networking certifications (one basic, one from the vendor the target employer uses), a cloud administrator certification, a security fundamentals certificate from a little-known online academy, a project management certificate, and a recently earned security certification from a major body.
Applying for a security-leaning infrastructure role, the filter keeps four: the vendor-matched networking credential (question 1), the cloud certification (1 and 5), the major security certification (1, 3, 4), and the basic networking credential only if the advanced one is from a different domain — otherwise it drops (question 2). The entry-level support certificate drops (superseded by six years of experience), the unknown-academy certificate drops (question 3, and question 5 — the major security credential covers that signal), and project management drops for this application but returns the moment a posting mentions coordinating projects. Same person, different application, different list. That is the whole method.
Notice what never happened in that example: nobody counted to a target. The four survived a relevance filter; the count was a consequence. So resist both anxieties — that you have "too few" (two current, relevant certifications is a perfectly strong section) and that dropping earned credentials wastes them (they are not deleted from your career, merely not printed on this page). Ask what this application needs proven, keep the credentials that prove it, and let the number be whatever the argument requires.
Exam facts in this guide were checked against official certification-provider pages on . Fees, exam codes and policies change — confirm on the provider’s own site before you book.
Put it into practice
Reading about an exam only takes you so far. Work through practice questions for your certification and find the gaps before exam day does.
·10 min read
A five-step decision process for choosing a professional certification: goals, market demand, true cost, prerequisites and renewal — with a comparison worksheet.
Continue reading·12 min read
The strongest professional certifications for 2026, ranked on demand, recognition and cost of ownership — with the year's retirements and AI-driven changes factored in.
Continue reading·8 min read
How certifications actually influence recruiters when you change employers, which types move offers upward, and how to time one around a job search.
Continue reading
