PlainResume

Certifications on a Resume: Gates, Signals, and the Udemy Problem

A practical guide from the team behind PlainResume, the free resume builder.

A certification answers a question your bullets can't: will a third party vouch that you know this? That's real value — but it varies enormously by certification, and the most common mistake is treating a weekend video-course certificate and a proctored professional license as the same kind of thing. Sort yours into three tiers first; the placement and formatting decisions follow from the tier.

The line itself: name, issuer, date

✗ "AWS certified"

✓ "AWS Solutions Architect — Associate · Amazon Web Services · 2025 (exp. 2028)"

Exact official name (screeners search for it — this is ATS keyword territory), issuing body, year earned, and the expiration if it has one. Add the credential ID only when an application form asks; skip badge images entirely — parsers read text, not pictures.

Tier 1 — gates: the job legally or contractually requires it

Licenses and required certifications aren't resume decoration; they're the first thing screened. A nursing license, a teaching certificate, a CDL, PMP on a government contract, a CPA for an accounting firm: these get their own section directly after the summary, with state and status where relevant. The reader's first question is "can I place this person at all?" — answer it in one second, and put the credential's abbreviation in your summary line too ("Jordan Reyes, CPA").

Tier 2 — signals: recognized, proctored, current

Industry certifications with real exams and real failure rates — AWS/Azure/GCP tracks, CPA, PE, CISSP, SHRM, PMP where the market cares — genuinely move screeners, especially when the posting names them. These live in a Certifications section near your skills, ordered by relevance to the posting, not by date. Two or three strong ones beat six mixed ones: like the skills list, the weakest item on the list sets the credibility of the whole section.

Tier 3 — the Udemy problem

Completion certificates from unproctored video courses verify that you watched, not that you learned — and every experienced reviewer knows it. A resume with twelve course certificates reads as a substitute for experience, which is the opposite of the intended signal. The honest hierarchy:

✗ "Certifications: Python Bootcamp (Udemy), SQL Masterclass (Udemy), Excel A–Z (Coursera), Intro to Data Science (Coursera), …"

✓ Skills: "SQL, Python (pandas)" — backed by a project bullet: "Built a rent-comparison tool in Python; 300 users in its first month."

The exceptions are narrow: the posting names the exact tool the course covers, or you're early-career and the completed course plus a real project is your honest evidence of initiative. Even then, the skill and the project carry the claim; the certificate is a footnote, never the headline.

Expired and in-progress, honestly

A section built for this. PlainResume has a dedicated, reorderable Certifications section — move it up top when your cert is a gate, keep it by skills when it's a signal — with a live page-count check. Free, no sign-up, no paywall on the PDF.

Build your resume free →

Frequently asked questions

Where do certifications go?

Required ones (licenses, posting-mandated certs): own section right after the summary. Recognized industry certs: a section near skills, ordered by relevance. Minor course certificates: bottom line or cut.

Are Udemy/Coursera certificates worth listing?

Usually not — they verify attendance, not skill. Exceptions: the posting names that exact tool, or you're early-career and pair the course with a real project.

How do I list expired or in-progress certs?

With dates, honestly: "expired 2024" or renew first; "exam scheduled May 2026" for in-progress. Never a vague "pursuing."