List certifications in their own section below education, formatted as name, issuer, and year: AWS Solutions Architect Associate, Amazon, 2025. Put a genuinely role-critical cert in your summary and after your name too. Date everything current, label in-progress honestly with an expected date, and drop expired certs unless the role explicitly asks about them.
A dedicated Certifications section beats scattering them through the resume, because both recruiters and parsers look for the heading. Standard order: certification name spelled out, issuing body, year earned, expiry if the cert has one. Use the official name — Certified ScrumMaster, not scrum certified — because recruiter searches and ATS matching run on exact strings, then add the acronym in parentheses so both forms are searchable.
Hierarchy follows relevance. A cert the posting requires belongs everywhere it can honestly live: the dedicated section, a mention in the summary, and for license-driven fields like nursing, accounting, or project management, appended after your name at the top. A cert that is merely nice sits one line in the section and nowhere else.
In-progress is listable if you label it exactly: PMP, expected March 2027, or currently enrolled. What you cannot do is list the bare cert name and let the reader assume completion — that is discoverable in verification, and certification bodies operate public registries that employers actually check. The honest label costs you little; the discovered inflation costs you the offer.
Expired certs are usually dead weight — an expired first-aid card or a 2014 vendor cert on a retired product says nothing current. Exceptions: certs that prove foundational knowledge that does not decay, listed with the year and no pretense of currency, and lapsed licenses in fields where reinstatement is quick and the employer mainly needs to know you held one. When in doubt, cut.
Weight follows scarcity and requirement. Certs that gate the job — CPA, PE, PMP, RN licensure, security clearances — are non-negotiable content. Cloud and vendor certs carry real search volume in recruiting databases: recruiters filter on AWS, Azure, and Salesforce certifications daily. Short online course completions carry the least weight, and a long list of them can read as credential collecting rather than capability.
Curate to roughly the five most relevant. If you hold twelve micro-certificates, group or summarize: 12 Coursera data-science course certificates including deep learning specialization, one line. The section should answer the recruiter's checklist, not archive your learning history — your skills section and bullets prove application, which is what the certificates only promise.
Yes, if labeled honestly: expected date or in progress next to the name. Never list the bare cert as if earned — issuing bodies run public verification registries and employers check them, especially for gating credentials.
Usually no. Include one only when it proves durable foundational knowledge or a license that is quick to reinstate, and show the year so you are not implying currency. An expired cert presented as active is an integrity problem.
Promote them: a Certifications section can sit where education would, directly below your summary or skills. For many technical and trade roles, current certifications carry more screening weight than a degree line anyway.
Run your resume through the free scorer to check your certifications section parses cleanly and matches what the posting asks for.
