A certification on a resume is one line: the name, the body that issued it, the year. Where that line goes depends on whether the certification is the job or a detail. A nursing licence is the job and goes under the name. A cloud certificate on an engineer's resume is a detail and goes in a section near the bottom. An online badge in "leadership" goes nowhere, because the reader has learned to skip them. The test is whether a hiring manager in the field would notice the name.
Key points
- One line each: name, issuing body, year. An ID number only when the field checks it.
- A licence that the role requires goes in the title line or under the name. Everything else goes in a Certifications section.
- Write "in progress" with the expected date. Write expired ones only when the field respects the history.
- Three to five. A list of twelve is a list of badges.
- Ask one person in the field which ones they would notice. List those.
Which ones count
| Kind | Example | Does the reader notice? |
|---|---|---|
| A licence the role requires by law | RN, CPA, PE, a commercial driving licence | Yes. Without it the application stops. |
| A credential the field treats as the standard | PMP in project management, CISSP in security, a cloud provider's professional level | Yes |
| A vendor certificate for a tool the posting names | Salesforce administrator, HubSpot, an analytics platform | Yes, when the posting names the tool |
| A completed course with a project | A UX certificate with a shipped project behind it | The project is noticed. The certificate confirms it. |
| An online badge in a soft skill | Leadership, communication, "AI for everyone" | No |
A certification is worth listing when a person who hires for the role would recognise the name without reading the line twice.
Where it goes
In the title line or under the name
When the credential is the job. "Registered Nurse, BSN" under the name. "Chartered Accountant" in the title line. The reader looks for it first and finds it first.
In a Certifications section
For everything else, a section after education, or after skills if the resume has no education section worth the space. One line per entry, newest first.
Certifications AWS Certified Solutions Architect, Professional, Amazon Web Services, 2025 Certified Kubernetes Administrator, Cloud Native Computing Foundation, 2024
In the skills list
Not as a line, but the skill it certifies goes in the list in the posting's words. The certification line is the evidence for the skill.
The line, written
Name as the issuing body writes it. The body. The year earned. An expiry only if the field tracks it, which licences and security credentials do.
Project Management Professional (PMP), Project Management Institute, 2023
Include the acronym in brackets once, so a search for either finds it. The guide on keywords has the rule.
In progress and expired
An in-progress certification goes on with the expected date, labelled: "AWS Certified Solutions Architect, Professional, expected March 2027." It says you are doing the thing. Do not list one you have not started.
An expired certification is a judgement call. In a field where the history matters, "CISSP, 2016 to 2022" tells the reader you held it for six years. In a field where only current ones count, an expired one reads as a lapse. Ask someone in the field.
A certification that no longer exists, because the vendor retired it, goes on with its years, as a fact.
What to leave off
- Soft skill badges from online platforms. Every resume has them and no reader has ever asked about one.
- Certificates of attendance for a conference or a webinar.
- A course with no project, in a field where the project is the proof. Put the project on instead.
- A certification in a tool the role does not use, unless it shows a domain the posting names.
Which ones the posting asks for
Read the posting the way the guide on reading a posting shows. A certification in the must-haves is a knockout question on the form and a line that goes near the top. One in the nice-to-haves is a line in the certifications section. One the posting does not mention is a line only if the field expects it. A certification that is in the must-haves and not on your resume is the reason the application stops at the skim, and Tailor on this site flags the gap before you send.
Questions
Do certifications replace a degree?
In some roles, yes, and the guide on jobs without a degree names them: the trades, operations, support, parts of technology. In roles that require the degree by law, no.
Do I include the credential ID?
Only when the field verifies it, which security and cloud credentials sometimes do. A line of digits on a resume for a design role is noise.
What about a bootcamp?
List it under education, with the year, and put the project it produced in the experience or projects section. The project is what the reader opens.
How many is too many?
Five. Past that, the reader assumes you collect them. Keep the ones the posting names and the ones the field treats as standard.
Does the ATS read certifications?
As text, yes, and some systems parse a Certifications section into its own field. Use the heading "Certifications" and one line per entry, so the parser can split it.