How to list certifications on a resume (and where to put them)

Most people list certifications in one of two ways: buried at the bottom where nobody sees them, or scattered across the page so the same credential appears three times. Both waste the credential. A certification is proof that an independent body checked your skill. Treat it like any other proof on your resume: put it where the reader is already looking for that kind of evidence, and write it so a stranger can verify it in seconds.

The short version: one line per certification — name, issuer, year — in a dedicated section, placed high when the posting requires it and lower when it is supporting evidence. The rest of this article is the placement rules, the honest handling of edge cases, and the mistakes that make a real credential look fake.

The one-line format

Every certification entry needs the same four pieces, in the same order, every time:

1. Certification name, written out in full the first time it appears. "AWS Certified Solutions Architect — Associate", not "AWS cert".
2. Issuing body. "Amazon Web Services", "CompTIA", "Project Management Institute". This is what makes the claim checkable.
3. Year earned (month too, if it is recent). Dates are how the reader judges whether the credential is current.
4. Status or expiry, only when it matters: "Expires Mar 2028", "In progress, expected Dec 2026".

Do not add a licence or registration number unless the posting asks for one or the number is public by nature (nursing licences, teaching credentials). A random string of digits in front of a recruiter who did not ask for it looks like filler, and it is one more piece of personal data on a document you send to strangers.

Where to put them: the placement rule

Placement is a relevance decision, not a formatting habit. Ask one question: does this posting require or strongly prefer this certification? If yes, it goes high. If no, it goes low. The same certification can sit in a different place on two different applications, and that is correct.

• Required or strongly preferred: near the top. Put a dedicated "Certifications" section directly under your summary, above work experience. The recruiter checking the must-have list should find it in the first screenful. If the certification is the single most important thing about your application — a newly qualified nurse applying for a nursing role — name it in the summary too: "Newly qualified RN (NMC-registered) with 400 hours of supervised clinical placement."
• Supporting evidence: lower down. If the certification backs up your experience but is not the reason you qualify, put the section after work experience, just above or below education. It is there for the reader who wants it and out of the way of the reader who does not.
• One or two certifications and a tight page: fold them into a combined "Skills & Certifications" section, or put them under education. This is the only case where merging is better than a dedicated section, because a one-line section with one line in it wastes space on a one-page resume.
• Recognised post-nominals only: next to your name. If the credential comes with letters people in the field use after a name — CPA, PMP, RN, CFA — you may put them in the header: "Maya Chen, CPA". Only for post-nominals the field actually recognises. Invented abbreviations ("John Smith, DMC") confuse the reader and cheapen the real ones.

What you should not do is list the same certification in three places — header, summary, and section — as if repetition makes it truer. One placement, chosen for this posting, plus a mention in the summary only when it is the headline credential. The reader who sees it twice assumes you are padding.

Which certifications to include

Include the ones that are relevant to this posting. That sounds obvious, but most certification sections fail in the other direction: a long list that proves the candidate collects credentials rather than uses them.

• Include it if the posting mentions it, if it is a recognised requirement in the field, or if it proves a skill your work history does not show yet — the classic case for new graduates.
• Leave it out if it belongs to a different field and says nothing about this role. A food-hygiene certificate on a software engineering application is not evidence; it is noise that makes the reader wonder whether you understand what the job needs.
• Leave it out if it expired years ago and you have not renewed it. An expired credential listed without a date reads as an attempt to pass it off as current. An expired credential listed with its date reads as a gap. Either way, it costs you more than it earns.
• Cut the list to the strongest three or four when you have many. A wall of certificates suggests you are compensating for missing experience. The strongest few, each tied to something the posting asks for, read as deliberate.

This is the same judgement as keyword matching: relevance beats volume. The certification section is not a trophy shelf. It is a short answer to the question "who has checked this person's skills?"

In progress, expired, and online courses — handled honestly

These are the three cases where people most often stretch the truth, and the three cases where honesty costs you nothing.

In progress. List it, labelled clearly: "In progress, expected Dec 2026". Never list an unfinished certification as if it were complete. The check is trivial — one question in the interview — and getting caught on it poisons everything else on the page. An honest "in progress" actually helps: it shows you are closing a gap the posting cares about, and it gives the interviewer something concrete to ask about.

Expired. Either renew it before you apply, or leave it off. The one exception is a credential that is still meaningful as history — a licence you held for ten years in a field you are returning to — and then you write "Held 2015–2023" so the dates do the honest work. If you have to explain away the expiry, the entry is doing more harm than good.

Online courses and certificates of completion. A certificate of completion is not a certification. "Completed: Machine Learning Specialization, Coursera, 2025" is a fair line under education or professional development. "Certified Machine Learning Engineer" for the same course is not. Recruiters know the difference, and the distinction is exactly what they are testing when they read this section. If the course came with a real assessed exam from the vendor, say so; if it did not, do not dress it up.

A credential you have to explain away is worse than no credential at all.

Certifications and the ATS

The ATS does not verify your certifications. It matches the text of the posting against the text of your resume. That has two practical consequences.

First, write the certification name the way the posting writes it. If the posting says "CompTIA Security+", write "CompTIA Security+", not "Security Plus" or "CompTIA Sec+". If it says "PMP", write "PMP" — but also write "Project Management Professional" somewhere on the page, because the parser may be matching either form and the human reader may only know one. The acronym plus the full name, first use, covers both. This is the same principle as matching keywords without stuffing: mirror the posting's language where it is true, and never claim a credential you do not hold.

Second, keep certifications in plain text in the body of the resume. Do not put them in a badge image, a header graphic, or a text box. Parsers routinely miss text inside images and floating boxes, which means your strongest credential can be invisible to the very filter you are trying to pass. A single-column layout helps here too — see why single-column resumes win.

One more trap: the certifications section is not a place to smuggle in keywords for skills you do not have. Listing "AWS Certified" when you once watched an AWS course is not tailoring, it is misrepresentation, and it will surface in the first technical question. The honest version of the same move is to list the course under education and let your bullet points show what you actually built.

The quick checklist

Before you send the resume, run through this list:

1. Every certification has a name, an issuer, and a year.
2. In-progress and expired items are labelled honestly or removed.
3. The section sits high if the posting requires the credential, lower if it is supporting evidence.
4. No certification appears twice. No certificate of completion is dressed up as a certification.
5. Names match the posting's wording, with the full name alongside the acronym on first use.
6. Everything is plain text in the body, not inside an image or a text box.

If the answer to all six is yes, the section is doing its job: a short, checkable list that lets the reader trust the rest of the page. Run the file through the ATS checker and confirm the certifications you care about are actually extracted. If they are not, the placement or the formatting is hiding them, and now you know exactly what to fix.

The bottom line

Certifications are not a list to maximise. They are proof, and proof works best when it is short, placed where the reader looks for it, and written so it can be checked. One line each, relevant ones only, honest about status, named the way the posting names them. Do that, and the section stops being filler and starts being the reason your resume survives the first screen.