6 min read
Wrong placement hides credentials from boolean searches and from recruiters who skim headers first. You don't need fifteen lines. You need the right section label and one parseable line per license.
If you're juggling school certificates and professional licenses, don't dump them in one Education block. Split by issuer tonight so parsers and humans aren't guessing.
Before you upload to Workday or Greenhouse, check your resume for free and confirm cert strings show up in extracted text. If PMP or CPA vanishes, fix layout before you tweak keywords.
This won't turn a weak fit into an offer. It stops a qualified file from failing a filter you already satisfy. That's the whole point of placement: make what's true easy to find.
Quick wins
- Heading: Certifications or Licenses and Certifications, plain text.
- One credential per line: name, issuer, year (or honest in-progress note).
- Single column through the cert block. No badge graphics or sidebar boxes.
What recruiters search for first
Corporate recruiters often run boolean searches on strings like PMP, CPA, RN, or AWS inside Workday. If your credential sits only inside a dense paragraph or a mixed Achievements list, it may never surface in that search even though a human reading the PDF would spot it.
Placement is findability. A labeled Certifications block earns a pause on skim. A cert buried under Education after three degree lines does not, especially when the req cares about your license, not your night-school program.
Parsers map uploaded files into fields when they recognize section labels. Certs listed only in Experience may copy into job history text but not populate a field a recruiter can filter on. A dedicated heading with plain lines gives the extractor a clean boundary.
For line formatting after placement is set, see what makes an ATS resume professional . You'll still want boring structure before you polish design.
Where do you put certifications on a resume tonight
- Mark JD requirements. Copy exact cert spelling from Requirements (PMP vs Project Management Professional).
- Sort by issuer. School certificates stay under Education. Industry exams and licenses go to Certifications.
- Count role-relevant certs. Two or more → dedicated section below Skills. One gatekeeper → headline echo plus one structured line.
- Write one line each with issuer and year. Repeat the cert once in a recent Experience bullet as proof, not as the only location.
- Parse-check the export. Re-export single-column DOCX or simple PDF if extracted text drops your block.
Copy-paste Certifications block:
CERTIFICATIONS
Project Management Professional (PMP), PMI, 2024
AWS Certified Solutions Architect – Associate, Amazon Web Services, 2024
Registered Nurse (RN), State of Texas, 2022
Before: Education lists BS Accounting plus PMP coursework in activities. CPA noted in a club line. Recruiter search on CPA returns nothing structured.
After: Certifications holds CPA and PMP with issuers and years. Education holds the degree only. Same facts, searchable layout.
Before: Skills reads Python, SQL, AWS, certified, Agile, Scrum. No issuer or date anywhere.
After: Skills holds tools only. Certifications lists AWS Certified Solutions Architect – Associate with issuer and year on its own line.
I've screened stacks of these in Workday and Greenhouse, and the file that wins is boring: one column, one cert per line, exact spelling from the posting when it's honest.
Placement traps that hide credentials
- Achievements soup: mixing certs with employee-of-the-month awards under one cute heading.
- Education-only CPA or RN: professional licenses treated like campus certificates.
- Skills-only listing: comma list with no issuer, year, or section label.
- Two-column badges: Canva sidebars and icon rows that parsers drop on import.
- Headline stacks: CPA | PMP | CSM | SAFe when the JD named one requirement.
Workday and Greenhouse application forms sometimes ask license questions separately. Answer knockouts with the same spelling as your resume. The file and the form answer different fields. Mismatch there can look like you don't hold the cert even when it's on page two.
Early-career candidates with thin Experience can keep Certifications above job history so PMP or Security+ leads the story. Senior hires with long work lists can move the block below Experience but still above Education. Either way, keep one cert per line inside a labeled section.
In-progress certs belong only when advanced and honest, like PMP (exam scheduled May 2026). Expired BLS on a clinical req is a hard gap. Fix renewal before you apply, don't bury expiry in a paragraph.
If dates on LinkedIn and your resume disagree, fix that noise before recruiters doubt the cert itself. How to fix mismatched dates on resume and LinkedIn walks through alignment without inventing timelines.
Verify placement before you apply
Run the same file you'd upload. You want cert strings visible in preview, not merged into Skills or Education by mistake.
Score your job match after extraction looks clean. If the posting wants a letter that names your license, generate a cover letter that repeats the cert once in plain text, not a badge image.
Right section, right spelling
Professional certifications on a resume belong in a labeled Certifications block below Skills when you have more than one gatekeeper credential. School certificates stay in Education. Echo one required cert in the headline when the JD repeats it, and keep the structured list as the source of truth.
Run the free ATS check on your export. Parse first, polish second.
Read more
Frequently asked questions
Put professional licenses and industry exams in a Certifications section below Skills and above Experience when you hold two or more the role cares about. Put university certificates under Education. Echo one required cert in the headline or summary when the posting lists it as non-negotiable.
Only when the credential is issued by a school and tied to a degree or formal program. CPA, PMP, RN, and AWS belong in Certifications with issuer and year, not under a university block where boolean searches may miss them.
You can name one cert next to a tool when space is tight, but do not replace a structured Certifications block with a comma list in Skills. Skills fields often lack issuer and date, which recruiters use to judge currency.
They read it when the heading is plain text like Certifications or Licenses and Certifications and each credential sits on its own line in a single column. Two-column templates, badge icons, and sidebar boxes often drop the whole block on upload.