8 min read
You paid for the PMP, passed the AWS exam, or renewed a state license. On paper you're qualified. On the resume those credentials sit in a Canva badge row or under Education where nobody searches.
That's not a pride problem. It's a placement problem. Recruiters filter on credential strings in Workday and Greenhouse before they read bullet three. If the parser never sees issuer and date in plain text, you're invisible on reqs you already cleared.
Before you tailor tonight, check your resume for free with the posting pasted in. Confirm every required credential shows as readable text, not just in a designed PDF layer.
Work through four grouped checklists below. You'll finish with a dedicated section, correct line format, expiry rules, and one bullet that proves use. That's the full job for one application night.
Quick Wins
- Highlight every certification named in the job description before you edit layout.
- Use a Certifications header in the body, not icons in a sidebar.
- Write credential, issuer, and year on one plain line per cert.
- Move expired unrelated certs off the tailored file for this req.
Certs, licenses, and courses: what belongs on the page
A certification is proof a recognized body tested you: PMP, CPA, RN license, AWS Solutions Architect, CompTIA Security+, SHRM-CP. Licenses required to practice belong in Certifications or a separate Licenses header when the posting treats them as gates.
Degrees stay under Education. Short LinkedIn Learning completions usually stay off unless the posting names that exact program or you need to prove a tool listed as required.
Think searchable proof, not a trophy case. Every line should answer whether a recruiter filtering on that credential would find you. If the text sits inside a graphic, rebuild before you apply.
For license-heavy fields, pair this page with craft a resume for healthcare roles . For section order context, see best resume section order for ATS .
How to put certifications on resume: four checklists
Open the posting you're applying to tonight. Keep it beside your resume file. Work through posting pull, section build, date rules, and proof bullet in order.
Checklist 1: pull credentials from the posting
Separate required from preferred before you touch layout. Required items must appear in plain text with full name and issuer. Preferred items go in when you hold them and they still support the role.
- Highlight required: Copy every credential string from the job description into a scratch note.
- Mirror spelling: If they write "Project Management Professional (PMP)," don't shorten to "PM cert."
- Flag licenses: RN, CPA, PE, and CDL often gate the req. Mark them as page-one priority.
- Skip noise: Drop internal company badges and one-hour MOOC completions not named in the posting.
Checklist 2: build the Certifications section
Default order for most candidates: Contact, Summary, Experience, Skills, Certifications, Education. When credentials gate the role, move Certifications or Licenses above Experience or directly below Summary so page one shows proof.
- Header label: Use Certifications or Licenses. Parsers map those words to database fields.
- Single column: No sidebar badge rows. No tables split across columns.
- One line per credential: Full name, issuing organization, year earned or valid-through date.
- Order by relevance: Posting-required certs first, then preferred, then older niche items.
Checklist 3: dates, expiry, and in-progress status
Active certs show year earned or "Valid through Month Year" when renewal cycles matter for the role. Show expiry only when the posting names current status or the license type requires it.
| Status | What to write | Where it goes |
|---|---|---|
| Active | Year earned or valid-through date | Top of Certifications list |
| In progress | "PMP, expected completion March 2026" | Below active, above expired |
| Recently lapsed | Note renewal in progress or omit until active | Below active certs only if posting still values it |
| Expired, unrelated | Remove from tailored file | Off the page for this application |
I've screened Workday pulls where PMP showed in Skills but not Certifications, and the req filtered everyone without the issuer line on a dedicated row.
Checklist 4: prove use in one Experience bullet
The Certifications section helps filters. Bullets prove you applied the credential. Repeat the top credential once in a dated bullet with an outcome tied to the posting.
- Pick one gate cert: The credential the posting lists as required or strongly preferred.
- Name it in the bullet: First eight words should connect cert to real work.
- Add one outcome: Timeline, scope, or metric from that role. Illustrative numbers inside the bullet are fine.
- Skills echo: You may repeat the acronym in Skills only when Certifications also shows issuer and date.
Copy-paste block: certification line formats
Copy-paste lines (adjust dates and issuers)
CERTIFICATIONS
Project Management Professional (PMP), Project Management Institute, 2024
AWS Certified Solutions Architect, Associate, Amazon Web Services, 2025
SHRM-CP, Society for Human Resource Management, 2023
LICENSES
Registered Nurse, State of California, License #123456, Active through 2027
CPA, Texas State Board of Public Accountancy, 2022
Before: PMP and AWS listed as colored badge icons in a right sidebar. Workday parsed an empty Certifications field.
After: Plain Certifications block in the body with full names, issuers, and years. Same credentials now appear in recruiter credential search.
Before: "BLS, ACLS, Epic" in Skills only. RN license number missing.
After: Licenses section with RN number and state. Certifications lists BLS and ACLS with dates. One bullet under the current unit names Epic and patient load.
Before: Ten certs listed alphabetically with a 2014 First Aid card above active PMP.
After: PMP first because the posting requires it. Expired unrelated First Aid removed from the tailored file.
Edge case: multiple certs from one issuer. List each exam on its own line. Don't merge into "Various AWS certs." Recruiters search exact exam names.
Edge case: bootcamp certificate on a career pivot. Place Certifications above Experience and lead bullets with projects from the program: "Full Stack Web Development Certificate, General Assembly, 2025."
Run the paste test from how to check if your resume is ATS-friendly after you rebuild. Certification lines should appear as readable text, not blank gaps where icons used to sit.
Layout traps that hide credentials
Badge graphics instead of text. Icons and colored shields often parse as blank space in Workday. Use words.
Certs only in Skills. A comma list without issuer and year is weak for regulated roles and easy to skip in recruiter search.
Burying licenses in Education. RN, CPA, and PE credentials are not degrees. Give them a labeled Certifications or Licenses section.
Listing every MOOC completion. Length without relevance signals padding. Keep posting-aligned credentials only.
Wrong or outdated status. Expired PMP with no note, or listing a cert you're studying for as earned, fails verification fast.
Two-column layouts. Certifications trapped in sidebars garble on import. Single column in the body wins.
This won't fix applying to roles you're not qualified for. It stops a credentialed file from dying in the parser before a human sees proof you already earned.
Match file to posting before upload
Placement rules are guesswork until you score the file against the live req. Run checks on the exact PDF or DOCX you'll submit, not a prettier version you keep for email.
Paste the posting into score your job match and confirm required credential keywords appear in readable text, not only inside a designed layer.
Then run the free ATS checker on the same export. Fix layout flags before you celebrate a match percentage. If certification lines vanish in the parse preview, move the block into the document body and remove tables.
When a posting asks for a cert you're completing, note expected completion in a cover letter, not as earned on the resume. The cover letter generator helps draft that line without overselling status on the credential list.
Upload-ready tonight
You don't need a new template. You need credentials where parsers and recruiters search: dedicated section, issuer on every line, active before expired, one bullet that proves use.
- Pull required certs from the posting and mirror exact spelling.
- Format plain lines: credential, issuer, year or valid-through date.
- Drop expired unrelated certs from the tailored file for this req.
- Tie the top credential to one dated Experience bullet.
Open your file now, move certs out of icon rows into plain lines, and run the free resume check on a req that lists credentials you already earned. That's how you stop losing filters on proof you've already paid for.
Read more
Frequently asked questions
Use a dedicated Certifications or Licenses section in the document body for most roles. Move it above Experience when the posting leads with a license or credential requirement. Never trap credentials in a sidebar, footer, or icon row parsers skip.
List active credentials first with year earned or valid-through date. Put recently lapsed certs below active ones only when you are renewing and the posting still values that credential. Drop expired unrelated certs that do not support the target role.
Include industry-recognized certs and rigorous bootcamp credentials when the posting names them or when they prove a must-have skill. Skip one-hour completion badges unless they map directly to a required tool in the job description.
Plain text lines with full credential name, issuing body, and year or expiration. Example: AWS Certified Solutions Architect, Associate, Amazon Web Services, 2025. Avoid icons, badge graphics, and tables that break parsing in Workday previews.