Certifications on a Resume: Where to Put Them and What to Include

Certifications belong on a resume when they are relevant to the target job, required by the employer, or strong evidence of a skill. Put important certifications near the top if they are a hiring requirement. Put supporting certifications in a dedicated Certifications section.

Do not list every course you have ever taken. A certification should help the recruiter understand fit.

Where to put certifications

Certification format

Use a simple format:

Certification Name - Issuing Organization - Date or Expiration

Examples:

• Project Management Professional (PMP) - PMI - Active
• AWS Certified Solutions Architect - Amazon Web Services - 2026
• Google Analytics Certification - Google - 2025

If a credential has an ID or verification link and the employer may care, include it only if it stays readable.

What to include

Include:

1. Official certification name.
2. Issuing organization.
3. Date earned or expiration date.
4. Active status when relevant.
5. Credential ID only when useful.

Avoid vague labels like certified in marketing if the credential has an official name.

Expired certifications

If a certification is expired, remove it unless it still explains important background and you label it honestly. Never imply that an expired credential is active.

Certifications and ATS keywords

Many job descriptions use certifications as hard filters. If a posting asks for CPA, PMP, SHRM-CP, RN, AWS, CompTIA, or similar credentials, use the exact official name if you have it.

Include both acronym and full name when space allows:

• Certified Information Systems Security Professional (CISSP)

FAQ

Should certifications go before education?

Yes, if they are more relevant than your education for the target job. Otherwise, place them after Education.

Should online courses go on a resume?

Only if they are relevant and credible. Projects or proof of skill are usually stronger than a long course list.

How many certifications should I list?

List the certifications that help the target role. Three relevant credentials are better than twelve random ones.

In-progress and expired certifications

List an in-progress certification only when it is relevant and there is a realistic completion timeline. Be specific and honest.

Examples:

• AWS Certified Solutions Architect - Amazon Web Services - In progress, expected August 2026
• Google Analytics Certification - Google - Active, expires 2027
• PMP coursework completed - Exam scheduled September 2026

Remove expired certifications unless they still explain relevant background and you label them clearly. Do not present an expired credential as active.

Certifications by resume section

Certification names can act as ATS keywords, but only when they are accurate. Use the official credential name and issuing organization so recruiters and systems can understand it.

Certifications should prove role fit

A certification belongs on a resume when it helps the employer evaluate you for the target role. Do not list every certificate you have ever completed. List the ones that are current, relevant, required, or strong supporting proof.

Certification examples

Strong:

• AWS Certified Solutions Architect - Associate, Amazon Web Services, active through 2027.

Weak:

• Online business certificate, completed.

Better:

• Google Data Analytics Certificate, completed 2026; coursework included SQL, spreadsheets, dashboards, and case-study analysis.

In-progress certifications

List in-progress certifications only when there is a real timeline:

• PMP certification coursework completed; exam scheduled September 2026.
• AWS Solutions Architect preparation in progress; exam planned August 2026.

Do not list vague "studying for" credentials if they do not support the application.

Certification keywords

Certification names can act as keywords, but accuracy matters. Use the official credential name and issuing organization. If a job requires a credential, make it easy to find.

Certifications by role and seniority

Certifications help most when they remove doubt. They can prove baseline knowledge, satisfy a requirement, or support a career change. They are weaker when they look like a pile of unrelated online courses.

Certification formatting examples

Weak:

• AWS certificate

Better:

• AWS Certified Cloud Practitioner, Amazon Web Services, issued 2026.

Weak:

• Studying for PMP

Better:

• PMP exam scheduled October 2026; completed 35 hours of project management education.

Weak:

• Various Coursera certificates

Better:

• Google Data Analytics Certificate, completed 2026; coursework included SQL, spreadsheets, data cleaning, and dashboard case studies.

Certification final check

For each credential, ask whether it helps the target role. If yes, keep it and format it clearly. If no, remove it. A shorter certification section with relevant proof beats a long list that makes the reader wonder what role you are targeting.

Certification placement examples

Weak:

• Certifications listed after hobbies even though the job requires one of them.

Better:

• Required certification appears in the summary and in a clear Certifications section.

Weak:

• Ten unrelated certificates listed with no dates or issuers.

Better:

• Three relevant credentials with official names, issuing organizations, and active or completed dates.

Certification section template

Use this format:

Keep the names exact. Recruiters and ATS systems often search for the official credential name, not a paraphrase.

Mini case study: certification plus project proof

A certification is stronger when it connects to a project or work example.

Weak:

• Google Data Analytics Certificate.

Better:

• Google Data Analytics Certificate, completed 2026.
• Project: cleaned sample customer dataset, built pivot-table dashboard, and summarized churn-risk patterns for final case study.

Weak:

• AWS Certified Cloud Practitioner.

Better:

• AWS Certified Cloud Practitioner, issued 2026.
• Project: documented basic cloud architecture for portfolio app, including storage, compute, and access-control notes.

The certificate tells the reader you studied the topic. The project shows what you can do with it.

Certification cleanup rule

If a credential is unrelated to the target role, remove it unless it explains a pivot or required qualification. A resume for data analyst roles does not need a long list of generic leadership certificates unless they support the job.

Certifications in the top third

Put a certification in the top third only when it helps screeners immediately.

Certification plus bullet example

Weak:

• Completed Scrum course.

Better:

• Certified ScrumMaster, Scrum Alliance, active through 2027.
• Project: maintained sprint task board for class product prototype, tracked blockers, and summarized demo feedback.

Weak:

• Data certificate.

Better:

• Google Data Analytics Certificate, completed 2026; built SQL and spreadsheet case-study projects with dashboard summaries.

Final certification rule

A certification should reduce doubt. If it creates confusion about your target role, remove it or move it lower.

Final certification example

Treat a certification as evidence, not decoration.

Weak:

• Certifications: online leadership course, business course, data course.

Better:

• Google Data Analytics Certificate, completed 2026; built SQL and spreadsheet case-study projects with dashboard summaries.

The better version gives the credential a role. It supports the target instead of filling space.

Last-mile certification review

Read the certification section as if you were a recruiter searching for one requirement. Is the required credential obvious?

Weak:

• Training: cloud, business, leadership, analytics.

Better:

• AWS Certified Cloud Practitioner, Amazon Web Services, issued 2026.

Use official names, issuers, and dates. Vague certificate labels waste one of the easiest keyword opportunities on the resume.

Sources

• seodata.dev certification in resume keyword data
• O*NET, U.S. Department of Labor
• Bureau of Labor Statistics Occupational Outlook Handbook