Which Resume Certifications Actually Impress Recruiters

Photo by Micaela Bassa on Pexels

Three months of study, a $400 exam fee, one new line on the resume — and then silence. Meanwhile a coworker with a single unfamiliar credential listed under "Certifications" is fielding recruiter messages weekly. That gap isn't random. Recruiters don't score certifications on how hard they were to earn. They score them on one question: does this match something the job posting actually asked for?

That's the whole rule, and once you apply it, the "worth it vs. skip it" decision gets a lot less mysterious.

The Real Test: Does the Job Posting Ask for It?

Ajusta, an ATS-scoring research group, ran 22 resumes against 48 real job descriptions and found the effect is binary, not gradual. When a posting listed a certification as required, having it added a measurable scoring boost — the certification name became a keyword match that's hard to compensate for any other way. When a posting listed it as merely preferred, the boost was smaller. When the posting didn't mention certifications at all, having one added almost nothing — the certification wasn't a keyword the scanner was even looking for, and the resume space it took up could have gone to something else.

That single finding explains most of the confusion around certifications. A CISSP means everything on a senior security-engineer posting that says "CISSP required" and close to nothing on a marketing-coordinator posting that never mentions certifications at all. The credential didn't change. What the employer was scanning for did.

So before you spend money or resume space on a certification, pull up 10-15 postings for the role you actually want and count how often the certification shows up as required or preferred. If it's most of them, it's worth having. If it's none of them, that study time is probably better spent on a portfolio piece or a stronger set of resume bullets.

Worth It: Certifications That Move the Needle

These consistently show up as required or preferred in job postings for their field, from real recruiting and salary-survey data:

• PMP (Project Management Professional) — shows up as a required or preferred qualifier across a large share of project-management postings; PMI's own salary survey reports certified project managers earning meaningfully more than uncertified peers in the same roles.
• AWS Certified Solutions Architect (and the parallel Azure/Google Cloud associate certs) — cloud-infrastructure postings frequently name a specific cloud provider certification by title, and the lift is largest early-career, when you don't yet have years of production experience to point to instead.
• CPA (Certified Public Accountant) — functionally required for public accounting; the CPA-vs-non-CPA line reshapes the whole resume in that field.
• CISSP — the senior-security-engineer standard; frequently listed as a hard requirement, not a nice-to-have, on postings above the mid-level.
• SHRM-CP / SHRM-SCP — carries real weight specifically in HR hiring, where it functions similarly to how PMP functions in project management.
• Any state-issued license your job legally requires — RN, Bar admission, CDL, real estate license. These aren't optional extras; they're gatekeeping credentials, and they belong at the top of your resume, sometimes right next to your name.

The common thread: a widely recognized issuing body (a government board, PMI, AWS, ISC², SHRM — not an unfamiliar online platform), and a field where postings name the credential by title often enough that you could find it by searching job listings yourself.

Skip It: Certifications That Just Take Up Space

• Short online course completions with no industry recognition. A four-hour "Digital Marketing Masterclass" from a platform no hiring manager has heard of doesn't read as a credential — it reads as a course you clicked through. If it's not from a recognized issuer, it belongs under "Professional Development," not "Certifications," or it belongs off the resume entirely.
• Anything old and unrelated to your target role. A 2016 Six Sigma Yellow Belt on a software-engineer resume doesn't help — it dilutes the section and confuses anyone scanning it for relevant keywords.
• A long list of unrelated micro-credentials. Ten badges from ten different platforms reads as collecting, not expertise. One strong, relevant, recognized certification consistently beats a wall of minor ones.
• A certification in a field where postings almost never mention certifications at all. Ajusta's job-description analysis found certifications listed as required in just 5% of marketing/sales postings and 8% of general-business postings, versus 72% of healthcare postings and 45% of finance postings. If you're in one of the fields on the low end, that resume space is better used on quantified results instead.
• An expired certification listed as if it's current. This isn't just a weak signal — it's a credibility risk if it gets caught at the reference-check or verification stage.

What to Do With an Expired or In-Progress Certification

Don't drop these into a gray zone. Handle each case explicitly:

Expired and no longer relevant to your target role: drop it entirely. It's not helping, and an unexplained expiration date raises more questions than the credential answers.

Expired but you're actively renewing: list it with a clear note — "PMP, Project Management Institute. Issued 2021. Renewal in progress" — so it reads as maintained, not lapsed.

Still in progress: list it only with a realistic completion date, not a vague "in progress." "AWS Certified Solutions Architect — Associate. Expected completion: October 2026, exam scheduled" signals real momentum. A bare "in progress" with no date reads as aspirational filler, and recruiters have learned to discount it. See our full guide to listing in-progress certifications for the exact phrasing to use for every stage, including passed-but-not-yet-issued.

I worked with a career-switcher last year who listed "Google Data Analytics Certificate — In Progress" for eight months straight with no date attached. Once she added "Expected completion: March 2026, 4 of 6 courses done," the same line started getting asked about in interviews instead of getting skipped over. The credential hadn't changed — the specificity had.

How Many Certifications Is Too Many?

Three to seven relevant ones is the range that shows up consistently across resume-formatting guidance. Fewer than that can look thin if your field expects certifications; more than that starts to look like padding, and it dilutes the keyword density of the section — the ATS and the recruiter both weight the first item or two in a list more heavily than the rest anyway.

If you genuinely hold ten or more legitimate, relevant certifications — this happens in IT more than anywhere else — group them into two or three labeled clusters ("Cloud & Infrastructure," "Security") instead of one long undifferentiated list. And always pair the certification with at least one resume bullet that shows you actually applying the skill. A certification says you can. A bullet with a real result says you have. Recruiters weigh the second one more than the first, no matter how many exams you've passed.

Building your certifications section in Simple CV is a matter of adding one entry per credential and reordering them by relevance to the job you're applying for — no reformatting the whole resume every time you tailor it for a new posting.