A certification belongs on your CV when it proves something your job history and skills section don't already prove — a required license, a specific tool, a credential the job posting names directly. It doesn't belong there just because you finished it. A list of unrelated badges next to real experience doesn't add weight; it dilutes the parts of your CV that were actually doing the work.
That's the judgment call this article is about. Not how to format a certifications section — you can find that anywhere — but how to decide, certification by certification, whether it's making your case or quietly undermining it.
The Real Test: What a Certification Has to Prove
Before you add anything to a certifications section, ask what it's supposed to do for the reader. A certification earns its place when it does one of these:
- It's required or expected for the role. A nursing license, a bar admission, a Series 7, a PMP for a program manager post — these aren't optional extras, they're prerequisites. Leaving them off looks like an omission, not modesty.
- It closes a specific gap in your experience. If you're moving into cloud infrastructure but your last two jobs were on-prem, an AWS or Azure certification is doing real persuasive work: it's evidence you've kept pace with where the field went.
- It matches a keyword the job posting uses. Many mid-size companies still run CVs through an applicant tracking system before a person reads them. If a posting says "Scrum Certified" or "Six Sigma Green Belt" by name, a matching credential on your CV is worth more there than it would be to a human reader alone — see how to find ATS keywords for any job posting if you're not sure how to spot which terms matter for a given role.
- It's from a body the industry actually respects. A CFA, a CPA, a PMI credential, a recognized language certificate (like a C1 CEFR or DELE) carries weight because the issuer's standards are known. A certificate from a platform nobody in the field references doesn't carry the same signal, even if the content was genuinely useful to you.
If a certification doesn't do at least one of those things, it's not disqualifying to include — but it's not pulling weight either, and it's competing for space with things that are.
When a Certification Reads as Padding
The opposite failure is just as common, and it's the one most candidates don't see in their own CV. A certifications section becomes a liability when it signals that you're padding rather than proving.
The tells are consistent: a long list where half the entries are one-day webinars; certifications with no clear connection to the role you're applying for; multiple "Introduction to..." courses stacked as if each one were a separate achievement; or a certification presented with more prominence than five years of relevant experience sitting two lines below it. A hiring manager reading fast reads a bloated list as compensating for something, even when that's not the intent.
The fix isn't to hide everything — it's to be selective the way you'd be selective with bullet points under a job title. If you wouldn't mention it out loud in an interview as something that shaped how you work, it probably shouldn't take up a line here.
Where to Put Certifications on Your Resume
Placement is a signal in itself — it tells the reader how much weight to assign before they've even read the credential.
Put certifications near the top, close to your skills or summary, when the credential is required for the role or is one of the first things a recruiter will screen for. A compliance officer's certifications, a pilot's licenses, a nurse's registration — these function almost like eligibility, so they need to be seen immediately.
For most other candidates, certifications sit lower: after experience and education, in their own labeled section near the end of the CV. At that point they're doing what they should do — reinforcing a case that's already been made by your work history, not trying to substitute for it.
One placement to avoid: scattering certifications inside individual job entries. It fragments the credential and makes it look incidental. Give it one clear home.
Certifications Section Resume Example
A section that reads as evidence rather than decoration is short, specific, and dated:
Certifications
- Project Management Professional (PMP), Project Management Institute — 2024
- AWS Certified Solutions Architect – Associate — 2025
- Google Data Analytics Professional Certificate — 2023
Each line has an issuer and a date, no descriptions, no bullet explanations underneath. If a certification needs three lines to justify its presence, it's usually a sign it doesn't belong in this section — it belongs, briefly, in the experience or projects section where the skill was actually applied.
Listing Online Courses on a CV
Online courses sit in a gray zone, and treating them exactly like formal certifications is where a lot of CVs go wrong. A completed, verifiable course from a recognized platform — a Coursera Professional Certificate, a well-known vendor course, a university-affiliated program — can go in the same certifications section, especially for candidates early in their career. If you're building a CV with little formal work history yet, well-chosen courses are one of the more credible ways to show direction; see how to write a CV with no experience for how that fits into the rest of the document.
What doesn't belong: a running tally of every course you've started, generic "certificate of completion" badges with no real assessment behind them, or courses with no bearing on the job. If you have several short, related ones — three data visualization courses, say — group them into a single line ("Completed multiple data visualization courses, including [specific one]") rather than listing each as its own achievement. One consolidated line reads as intentional; five scattered ones read as an attempt to fill space.
Expired Certifications on a CV
Whether an expired certification stays depends on what kind it is. Time-bound technical and compliance certifications — cloud platforms, security credentials, project management certifications with renewal cycles — lose most of their evidentiary value once lapsed, because the whole point of the expiry date is that the field moved and your knowledge might not have moved with it. If you're mid-renewal, say so plainly: "PMP (renewal in progress)." If it's simply lapsed and you have no plan to renew, it's usually better cut than left dangling with an old date that invites the question you don't want asked.
Certifications that don't really "expire" in practice — a language proficiency certificate, a foundational credential tied to a degree, a license you'd only need to reactivate rather than re-earn — can stay as long as the date is honest. The test is the same one from the top of this article: does keeping it prove something current, or does it prove something that used to be true?
Making the Final Cut
Once you've gone through your list, you should be able to say in one sentence why each remaining certification is there — what it proves, and for which kind of role. If you can't, that's the one to cut, not the one to keep "just in case."
This is also one of the easier things to misjudge about your own CV, because every certification felt like effort when you earned it. A free CV review from Kaeros looks at exactly this kind of judgment call — what's proving your case and what's quietly working against it — and tells you plainly which is which before you send anything out. For a broader pass on how the rest of the CV holds up against automated screening, the ATS CV guide covers the format side this article deliberately left out.