The certifications section is one of the most over-loaded sections on a typical resume. Candidates include the PMP, two CFA levels, four Coursera courses they finished in 2019, a one-hour LinkedIn Learning completion, an Excel course from 2014, and a personality-test certificate. The result is a 14-line section that signals nothing in particular — and dilutes the few credentials that actually matter.

This post is the cut: what belongs, what doesn't, and how to format the section so the strong credentials don't get lost in the noise.

The decision matrix

Two questions decide whether a certification belongs on the resume:

1. How widely recognized is it? A PMP is recognized by every hiring manager who has ever hired a project manager. "Certified Agile Practitioner from $RANDOM_COMPANY" is not. Recognition determines how much explanation the line needs.

2. How relevant is it to the role you're targeting? A CFA is highly relevant for an analyst role; mostly irrelevant for a frontend engineering role. Relevance determines whether it earns space at all.

The quadrant breaks out as follows:

High recognition + high relevance. List prominently in its own section. PMP for project managers. CFA for buy-side or sell-side finance. CPA for accounting. AWS Solutions Architect Professional for cloud engineers. State-issued licenses (PE, RN, Bar admission) for licensed professions. These belong above the fold and often justify a separate "Certifications" section near the top.

High recognition + low relevance. List once, briefly, somewhere in a credentials block. A PMP on a software engineer's resume is mildly useful keyword bait but doesn't deserve top billing. Don't lead with it.

Low recognition + high relevance. List with the issuing body's full name and, if obscure, a one-line context. Internal-company certifications often live here ("$BIGCO Internal Security Certification — equivalent to CompTIA Security+ scope"). These can be strong signals if you explain them.

Low recognition + low relevance. Skip entirely. This is where the LinkedIn Learning completions, 1-hour Udemy courses, and generic "Certified Excel User" badges live. Listing them dilutes the certifications that actually matter.

What's in, what's out

The list of certifications worth including is shorter than candidates expect.

In:

• Current, role-relevant industry certifications. PMP, CFA, CPA, CISSP, AWS (all levels), Azure, Google Cloud, Salesforce-administrator, HubSpot, Snowflake, Tableau, Six Sigma (Black Belt and above), PHR/SPHR/SHRM-CP for HR, ACSM for fitness, real estate licenses, insurance licenses.
• Active state-issued professional licenses. PE (engineering), RN/MD/RDN (healthcare), Bar admission (law), CPA (accounting), licensed real estate agent, licensed insurance broker.
• Vendor certifications when the JD names the vendor. Salesforce-certified administrator is in if the JD mentions Salesforce. Otherwise, it's probably out.
• Recent reskilling certifications that show pivot work. A Google Data Analytics certificate from someone genuinely pivoting into analytics is meaningful; the same certificate on an experienced data analyst's resume is filler.

Out:

• LinkedIn Learning "completion" certificates for 1-hour courses. These are not certifications; they're attendance confirmations.
• Expired certifications, unless you specifically note you're reactivating them.
• Generic, self-issued, or unverifiable credentials. "Certified Excel User" without a recognized issuing body. Anything you "earned" by paying a fee and watching a video.
• Every Coursera course you ever finished. Two or three relevant ones can go in; sixteen of them dilute everything else.
• Personality-test "certifications" (DISC, MBTI, Predictive Index). These are assessments, not credentials.

The general principle: every line in the certifications section should be something a hiring manager in your field would recognize as a real credential. If you can't say that about a line, cut it.

What the data says

The audit-study data on certifications shows two things:

1. Role-relevant industry certifications move callback rates measurably. In matched-resume studies, including a relevant certification (PMP for PM roles, CFA for analyst roles, AWS for cloud roles) increases callback rates by roughly 15-20% versus an otherwise identical resume without it. The effect is concentrated in fields with formal credentialing — finance, healthcare, IT security, project management, accounting. In creative or non-credentialed fields, the effect is much smaller.

2. Dilution is real beyond ~4 certifications. Recruiters report that resumes with five or more listed certifications start to read as "padded," and the strong credentials get lost. The signal-to-noise ratio drops sharply past four items.

The implication: if you have one strong, role-relevant certification, lead with it. If you have two or three, list them cleanly. If you have eight, pick the four strongest and drop the rest.

Where to put the section

For most roles, the certifications section goes after Experience and Education, near the end of the first page. The exception: roles where the certification is effectively a job requirement (medical, legal, regulated finance, licensed engineering, certain government roles), in which case the certification belongs in or near the summary, above Experience.

Format the lines tightly. The pattern that works:

Project Management Professional (PMP) — Project Management Institute. Issued 2021, current.

AWS Certified Solutions Architect — Professional. Amazon Web Services. Issued 2024.

Series 7 and 63. FINRA. Active.

Issuing body, year, current/expired status. No padding, no marketing copy.

When the certification is in progress

A certification you're actively pursuing is sometimes worth listing — but only when you've made meaningful progress and have a date. "Studying for the CFA Level 1 — exam scheduled August 2026" is real. "Pursuing CFA designation" without context is noise.

The same rule applies to expired certifications: if you're actively renewing one, you can list it as "renewing 2026." If it lapsed five years ago and you have no plan to renew, leave it off.

For the broader question of where credentials fit relative to your work history, see resume-summary-section. For the related question of how the ATS handles certification keywords, see ats-keywords-vs-recruiter-keywords.

What this isn't

A few clarifications:

• It's not a hierarchy of credentials. A PMP isn't "better than" an MBA or a portfolio. They're different things. The certifications section is just one part of the case the resume makes.
• It's not the place to list every training you've ever attended. Internal training, vendor webinars, and one-off workshops are not certifications. They belong on LinkedIn at most, not on the resume.
• It's not a substitute for relevant experience. A certification helps when paired with work that demonstrates the same skill. On its own, a credential is a weaker signal than a year of relevant work.

The short version: include role-relevant certifications from recognized issuing bodies, cap the section at about four items, format tightly with issuing body and date, and skip the LinkedIn Learning completions. The strong credentials work best when they aren't drowning in noise.