How to List Certifications on Your Resume for ATS

You earned the certification. You paid for the course, passed the exam, and added the credential to your LinkedIn. Then you copy-pasted it onto your resume — and the ATS still filtered you out.

This happens more often than you think. Certifications are some of the highest-signal keywords in a job application, but they're also one of the most commonly mis-formatted sections. ATS systems need to parse your certification entries in a specific way to match them against job requirements — and small formatting errors can make them invisible.

This guide covers exactly how to list certifications on your resume so ATS reads them, where to put them, what to include, and what to skip. We'll look at real formatting examples across industries, handle edge cases like in-progress and expired certs, and show you what a properly structured certifications section looks like from the ATS's perspective.

Why Certifications Matter More Than Ever for ATS

Modern job postings are increasingly specific about credentials. A posting for a cloud architect role might say "AWS Certified Solutions Architect required." A healthcare role might specify "BLS certification required." A finance role might require "CPA or CFA preferred."

When recruiters configure ATS filters, certifications often become hard requirements — meaning resumes without the matching keyword are automatically disqualified before a human sees them. According to LinkedIn hiring data, job postings requiring specific certifications have grown significantly, particularly in technology, healthcare, finance, and project management.

The challenge: ATS systems don't read your resume the way a human does. They extract text, run it against a pattern-matching engine, and score the match. If your certification is buried in a dense paragraph, uses an uncommon abbreviation, or is formatted inside a table or graphic, the system may fail to extract it entirely.

Where to Put Certifications on Your Resume

Placement depends on how central certifications are to the role you're targeting. There are three main options:

Option 1: Dedicated Certifications Section (Recommended for Most)

Create a standalone section labeled "Certifications" or "Licenses & Certifications". This is the clearest signal to ATS systems and recruiter eyeballs alike. Place it:

• After Skills and before Education — if certifications are highly relevant to the role (e.g., AWS certs for a cloud engineer)
• After Education — if certifications supplement your degree (e.g., PMP after an MBA)
• Near the top of the resume — if a certification is required and you're competing against credentialed candidates (e.g., licensed nurse listing RN immediately)

Option 2: Within the Education Section

If you have only one or two short-course certifications and they're closely tied to your degree, you can include them as sub-entries under your Education section. This works for:

• Google Analytics certification listed under a Marketing degree
• Coursera/edX professional certificates adjacent to a formal degree

The downside: ATS systems that segment sections by header may not scan certifications listed under "Education" when searching for a "Certifications" field. When in doubt, use a separate section.

Option 3: Within the Skills Section

Some people list certifications as skills (e.g., "PMP Certified" in a skills list). This works as a secondary mention but should never replace a dedicated section. Including the full certification name in your Skills section can help with keyword matching for systems that scan the entire document as plain text.

How to Format Each Certification Entry

Each certification entry should follow a consistent structure. ATS systems look for specific fields when parsing credentials:

Here's what a properly formatted certifications section looks like:

The Four Fields That Matter to ATS

1. Full certification name — Use the official name exactly as issued. "AWS Solutions Architect" and "AWS Certified Solutions Architect – Associate" are different strings; recruiters may filter for the official one.
2. Acronym (if commonly used) — Include the abbreviation in parentheses after the full name: e.g., "Project Management Professional (PMP)." Many ATS systems search by abbreviation.
3. Issuing organization — This provides context and disambiguation. "Scrum Master Certified" alone is ambiguous; "Certified ScrumMaster (CSM) — Scrum Alliance" is not.
4. Date — ATS systems check whether certifications are current. Include the issue date at minimum; include expiration for time-limited certs.

Full Name + Acronym: The Most Important Rule

This is the single most impactful formatting tip for certifications and ATS. Always write both the full certification name and the acronym.

Why: ATS systems search for whatever the recruiter entered in the filter. One recruiter might filter for "PMP," another for "Project Management Professional," and another for "PMI." If you write only the acronym, you miss searches for the full name. If you write only the full name, you miss acronym searches.

The correct format:

Notice how the licensed nurse example also includes the license number and issuing state board — critical for healthcare ATS systems that verify credentials.

Industry-Specific Certification Examples

Technology

Project Management

Finance & Accounting

Healthcare

Marketing & Digital

Handling In-Progress Certifications

If you're actively pursuing a certification, you can list it — but be transparent about the status. Misrepresenting an in-progress cert as completed is a red flag if discovered during background checks.

Use one of these formats:

In-progress certifications still contain the keyword, so they'll match ATS filters — the recruiter can then assess whether "expected" is close enough. For roles that list a certification as preferred (rather than required), this approach often works well.

Handling Expired Certifications

Expired certifications create a dilemma. The keyword value is there, but showing an expired credential can raise concerns. Here's the guidance:

• Recently expired (within 1-2 years): Include it, noting the expiration date. Many hiring managers will still count it, especially if renewal is common.
• Long expired (3+ years): Omit it unless it's the only evidence of a required skill. An expired CISSP from 2015 does more harm than good.
• Expired but fundamental (e.g., old CPA license): Include it with "License Inactive" rather than omitting. The credential history still has value.

Never alter or omit the expiration date to make a cert appear current. ATS systems don't check expiration dates automatically, but human reviewers and background screening services do.

Certifications vs. Licenses: What's the Difference?

Many people conflate certifications and licenses, but they're distinct — and ATS systems sometimes have separate fields for each.

• Certifications are issued by professional organizations and demonstrate competency (e.g., PMP, CPA, AWS cert). They may or may not be legally required.
• Licenses are issued by government bodies and are legally required to practice a profession (e.g., RN, PE, real estate license).

If you have both, consider using the section header "Licenses & Certifications" and list licenses first. For healthcare and legal roles especially, licenses are required fields — put them prominently.

Certifications That Don't Belong on Your Resume

Not every credential you've earned needs to be on your resume. Skip these:

• Completion certificates for short online courses (e.g., a 2-hour Udemy course). These carry no weight and take up space. List them only if you have no other credentials and the topic is directly relevant.
• Outdated technology certifications (e.g., MCSE for Windows Server 2003). These signal age rather than skill.
• Certifications unrelated to the role. A software engineer applying for a backend role doesn't need their Food Handler's License on their resume.
• Internal training certificates from previous employers. Unless the company is widely known and the training is industry-recognized, these add noise.

Common Mistakes That Make ATS Miss Your Certifications

1. Listing Only the Acronym

Writing "PMP" without "Project Management Professional" means you'll miss ATS searches for the full name. Always include both.

2. Using Non-Standard Section Headers

Headers like "Credentials," "Professional Development," or "Training" may not be recognized as certification fields by all ATS systems. Stick to "Certifications" or "Licenses & Certifications."

3. Embedding Certifications in a Table or Text Box

If your resume uses tables for layout, text inside cells may not parse correctly in older ATS platforms like Taleo. Keep certifications in standard body text.

4. Listing Certifications in the Header or Footer

Some applicants add "PMP | CPA | AWS Certified" in their contact header. ATS systems often skip headers and footers during parsing. These credentials won't count toward keyword matching.

5. Leaving Out the Issuing Organization

"Scrum Master Certified" from unknown source vs. "Certified ScrumMaster (CSM) — Scrum Alliance" are not the same thing. Always attribute the issuing body.

6. Not Mirroring the Job Description Language

If the job posting says "AWS Certified Developer – Associate" and you write "Amazon AWS Developer Certification," the ATS may not match them. Use the exact wording from the job description where possible.

Should You List Certifications in Your Resume Summary?

Yes — for highly relevant credentials. If a certification is required for the role or is a major differentiator, mention it in your resume summary as well. This creates a second keyword hit and immediately signals to both ATS and the recruiter that you're qualified.

Example:

The certification appears in the summary, in the certifications section, and ideally in the relevant work experience bullets — giving it three separate matches across the resume.

Quick Reference: Certification Formatting Checklist

• Use a dedicated "Certifications" or "Licenses & Certifications" section header
• Write the full certification name and the acronym in parentheses
• Include the issuing organization for every entry
• Add the issue date and expiration date (or "No Expiration")
• For licenses, include license number and issuing state/body
• Mark in-progress certifications with "In Progress — Expected: [Month Year]"
• Avoid tables, text boxes, and headers/footers
• Mirror the exact wording from the job description where relevant
• Mention key certifications in your resume summary for extra keyword density