How to Add Certifications to a Resume

You finished the course, you have the badge, and now you are staring at your resume wondering where it goes. A "Certifications" section at the bottom? Up next to your name? Inside the job where you used it? Every guide gives you a different default, and most of them treat your CPR card and your PMP the same way, which is the actual problem.

They are not the same kind of thing. One is a requirement the job filters on. The other is supporting evidence. Sort your certifications into those two piles first, and the placement question mostly answers itself.

The takeaways

• Required licenses go up top, supporting certs go to the bottom. If a posting lists the credential as a must-have (a PMP, a CDL, an RN license), it belongs near your name or summary where a recruiter spots it in the first scan.
• Three to five relevant certifications is the ceiling. A wall of ten online-course badges reads as padding and quietly signals you are substituting credentials for experience.
• A certificate proves you finished a course, not that you can do the job. List the ones that map to what this employer asked for, and let your work bullets carry the rest.

Where should certifications go on a resume?

It depends on whether the job requires the credential. If the posting names a certification as a hard requirement, put it where it gets seen fast: beside your name as an abbreviation (Jane Doe, PMP), in your summary, or in a short block directly under your contact line. A recruiter screening for that exact credential should not have to dig.

Everything else is supporting evidence, and supporting evidence sits lower. A dedicated "Certifications" section below your work experience is the standard home for online courses, continuing education, and nice-to-have credentials. The exception is entry-level: when you have little work history, certifications are some of your strongest proof, so it is fair to move that section up, just under your summary. Indeed and Jobscan both land on the same logic, even if they phrase the default differently: importance to the role decides height on the page, not a fixed rule.

Which certifications are actually worth listing?

The ones relevant to the job in front of you, and not many more. A focused set of three to five credentials that match the posting does more than a stack of fifteen. Recruiters read a long certifications list the way they read a long skills list: with suspicion that you are padding. Worse, a pile of beginner online certificates can read as a substitute for real experience rather than an addition to it.

Run each credential through one question: would this make a hiring manager for this specific role more likely to call me? An AWS or CompTIA cert on a cloud-engineering application, yes. A weekend Udemy course on something unrelated, no, leave it off. Recognized issuers help here. A credential from AWS, Google, CompTIA, PMI, or a licensing board carries weight a recruiter recognizes instantly; an obscure provider they have never heard of carries almost none, so make the relevance obvious in the line itself.

How do you format a certification entry?

Give four things, spelled out, in a consistent order: the full certification name, the issuing organization, the date you earned it, and the expiration date if it has one. So: "AWS Certified Solutions Architect, Amazon Web Services, March 2025." Skip the bare acronym on its own. "CSM" means nothing to a recruiter scanning fast and nothing to the ATS parsing your file, while "Certified ScrumMaster (CSM)" gets read by both.

List them in reverse chronological order, newest first, unless relevance to the role argues for a different order, in which case lead with the credential the job actually asked for. Keep the font and size identical to the rest of the resume so the section does not look bolted on. One clean line per credential is enough; you do not need the certificate number or a logo, and a logo can break ATS parsing anyway.

Should you list a certification in progress or expired?

Yes to in progress, carefully. If you are partway through a credential, list it with the issuer and an expected date, marked clearly: "Google Data Analytics Certificate (In Progress, expected August 2026)." That shows initiative and is honest. Never write it in a way that implies you already hold it, because the moment an interviewer asks about a credential you have not earned, the whole resume gets a second, more skeptical read.

Expired is trickier. As a rule, drop expired certifications. The exception is when the underlying skill still matters and the lapse is recent: you can keep it and label it "Expired 2024" or "renewal in progress," so you are not quietly passing off a dead credential as live. If a required license has lapsed and the job needs it current, do not list it as if it counts, fix the license first.

Match the certifications to the posting

The same instinct that orders your work bullets orders your certifications: read the posting, find the credential it names or implies, and make that one easy to find. If the job calls for a specific license, it should not be buried at the bottom under three courses nobody asked about. Tailoring this section to each role is the same discipline behind the rest of a well-built resume: put the most relevant proof where the reader looks first, and let the supporting material sit underneath. A certification only helps when it answers a question the employer actually asked.

Where JobScalr fits

Re-sorting your certifications for every posting is slow, and that is the part worth handing off. JobScalr reads a specific job posting against your resume, gives you an honest match score from 0 to 100 with the reasoning behind it, and rewrites your resume and cover letter to fit the role without inventing skills, credentials, or results you do not have. It will not apply for you, and the final read stays with you. It takes the repetitive matching off your plate so your time goes to the jobs where you actually fit.