How to List Certifications on Your Resume With Examples

How should you list certifications on your resume? Use the exact credential title, issuing organization, earned date, and expiration date when applicable, and make the credential's current status clear.

A short Certifications section usually gives those details enough room. A credential that the job specifically requires may also deserve a brief mention near the top of your resume, such as in your headline; these resume headline examples show how that can look. Either way, the reader should be able to tell what you earned without interpreting a badge image or guessing whether you passed an exam.

The harder decisions come when your records include course certificates, an expired credential, or an exam you have scheduled but not passed. Here's how to choose the right wording and placement, with developer and product manager examples you can adapt. All sample credentials, dates, and work descriptions below are illustrative, not records of actual candidates.

Choose credentials that matter for the role

Start with the job description rather than your entire collection of credentials. Look for a named certification, a preferred qualification, or a responsibility that an earned credential directly supports. Then check what you actually hold.

A relevant certification is worth including when it helps answer a specific question about your qualifications. For example, a cloud development credential may support an application for a role building on that platform. The same credential may add little to an unrelated role where your recent work already supplies stronger evidence.

Use this order when deciding what earns space:

• Include a required credential if you hold it and its current status meets the stated requirement.
• Consider a preferred or directly relevant certification next.
• Keep supporting credentials only when they add useful information that is missing elsewhere.
• Remove unrelated or repetitive introductory certificates when they crowd out stronger qualifications.

There is no fixed number of certifications a resume needs. An experienced candidate may need one concise entry. An early-career candidate may have room for several relevant credentials, provided each is described accurately. Space matters too. If you're asking yourself, “Do resumes have to be one page?” trimming low-value certificates is an easy place to start.

For broader decisions about connecting qualifications to a posting, Jobsuit's guide to tailoring a resume to a job description can help. Keep the certification's official name intact while deciding how prominently to present it.

Distinguish certifications from certificates and training

Use the label the issuer gives you. A professional certification records that you met the issuer's certification requirements. A course-completion certificate records completion of that program. The requirements may include assessments, but the word certificate alone does not tell a reader what was assessed.

Training attendance, exam preparation, and an earned certification are different records. You can accurately describe each without promoting one into another. A digital badge is a way to represent a credential; check what the badge actually recognizes before calling it a certification. A professional license also has its own issuer and status, so preserve that label if you use a combined Licenses and Certifications section.

Choose a section name that fits its contents. Certifications works for earned certifications. Professional Development can accommodate completed training and course certificates. Avoid placing everything under Certifications simply because it sounds stronger.

Build a complete certification entry

Gather the credential record before you format your resume. Check the issuer's portal, certificate, or official verification page for the exact title and dates. This prevents small but consequential mistakes, such as using the training provider as the certification issuer or listing the exam date as the award date.

For an earned certification, include its title, issuer, and earned date. Add expiration information when applicable so its status is clear.

A simple entry can follow this pattern: Full credential title, Issuing organization. Earned Month Year. Expires Month Year, if applicable.

For example: AWS Certified Developer - Associate, Amazon Web Services. Earned April 2026. Expires April 2029.

Those dates are illustrative. Copy your own dates from the issuer's record rather than calculating an expiration date from a sample. Add a familiar abbreviation after the full name when it helps recognition, but avoid replacing an unfamiliar title with initials alone. Spelling out the full title also keeps an ATS friendly resume searchable for the exact credential name.

Use one date style throughout the section. Month and year are generally enough for a resume entry; if an application asks for an exact day, use the official record to complete that field. There is usually no reason to include exam scores, the number of attempts, or a description of every module.

Credential IDs are optional unless the application requests one or the issuer uses a public identifier for verification. A long ID that does not help the reader verify anything adds clutter. If the credential is unfamiliar, a brief, accurate explanation of its focus can help, but keep it separate from claims about your professional experience.

Decide where certifications go on your resume

Placement should reflect the credential's relevance and the strength of the rest of your resume. Give a required qualification enough visibility that the reader does not have to search for it. Keep supporting credentials compact when experience does more to explain your fit.

These are layout choices, not fixed rules. If you have substantial relevant experience, placing a supporting certification below it preserves the reading order of a reverse chronological resume format. If you are changing careers and an earned credential addresses a key requirement, moving the section higher may make your qualifications clearer.

You can mention one especially relevant certification in your summary and retain the complete record in the Certifications section. Keep the summary reference short. Repeating the title and dates in several places consumes space without adding evidence. If you're unsure what belongs there, our guide to what is a resume summary explains how to write one.

Avoid attaching every credential abbreviation to your name. Unless a designation is relevant and conventionally used that way in your field, the full entry is easier to understand. Likewise, a list of good resume skills can name a technology you can use, but it should not become a second incomplete credential list.

Make credential status explicit

An earned credential, a renewal in progress, and a scheduled exam need different wording. Check the status again when you submit an application, especially if you are reusing an older resume.

Active and nonexpiring credentials

Show an expiration date when the issuer assigns one. AWS Certified Developer - Associate, for example, is valid for three years. Use the dates on your own credential record to establish its validity.

Other credentials follow different rules. Scrum.org's Professional Scrum certifications are earned through assessment, separate from training attendance, and are lifetime certifications without renewal costs. Do not invent an expiration date for a credential that has none.

For a non-expiring certification, the earned date may be enough. You can add No expiration if that clarification is useful and supported by the issuer. A lifetime credential still does not establish how recently you used the subject matter, so leave current hands-on ability to your work and project descriptions.

Expired credentials and pending renewals

Usually, omit an expired certification when it adds little to your current application. If it explains relevant historical experience or the employer asks about previous credentials, you can include it with an unmistakable status label.

An illustrative entry might read: AWS Certified Developer - Associate, Amazon Web Services. Earned May 2022. Expired May 2025.

Do not remove the expiration date and present the credential as current. An expired certification also should not be described as satisfying a requirement for an active credential.

Renewal pending means the process is unfinished. If the credential is still active, retain its current expiration date until the official record changes. If it has expired, keep the Expired label even if you have completed some renewal steps. Mention renewal activity only when it is accurate and relevant; do not substitute an assumed future expiration date.

Training in progress and scheduled exams

If you are enrolled in a course, name the course and its provider under Professional Development or Training. An expected course completion date can be appropriate when it reflects your actual program schedule. Make clear that it refers to training completion, not an expected certification award.

For an exam you have actually booked, wording such as AWS Certified Developer - Associate exam scheduled for November 2026; certification not yet earned describes the situation without implying a result. Include that information only if it helps the application; otherwise, it may fit better in your cover letter, as our cover letter vs resume guide explains. A plan to book an exam someday usually does not need resume space.

Avoid a bare In progress after a certification title. It leaves open whether you are studying, enrolled in training, awaiting an assessment, or waiting for the issuer to award the credential. After passing an exam, check the issuer's awarded status before presenting yourself as certified.

Developer resume example with an earned certification

Suppose a developer is applying for a role involving applications on AWS and holds an active AWS Certified Developer - Associate credential. The certification entry can be brief:

AWS Certified Developer - Associate, Amazon Web Services. Earned April 2026. Expires April 2029.

That illustrative entry establishes the credential. It does not tell the reader whether the candidate has built an application, maintained a production service, or completed a personal lab. Those details belong in the relevant experience or project entry.

For a personal project, an illustrative description could read:

Personal project, serverless reading tracker. Built an API with AWS Lambda and Amazon DynamoDB, added automated tests, and documented deployment steps and error handling.

Use a description like that only when it matches work you actually completed. Label personal work as a project rather than placing it under an employer you did not work for. If you followed a tutorial, describe your contribution accurately instead of implying you designed the entire system independently.

An experienced developer could instead pair the credential with an actual work example involving a deployment, debugging task, or service improvement. Be specific about what you did and what you can substantiate. You do not need to invent a percentage improvement to make a technical contribution understandable.

Product manager resume example with a product owner credential

For a product manager applying to a role that values Scrum experience, an earned Professional Scrum Product Owner I credential may be relevant. The same assessment and status distinctions apply here: attending a class does not mean you hold the certification.

An illustrative entry could read:

Professional Scrum Product Owner I (PSPO I), Scrum.org. Earned June 2026.

No expiration date is needed for this lifetime certification. The entry also should not imply that the credential proves every skill involved in product management, such as customer discovery, commercial judgment, or making tradeoffs with stakeholders.

Use a separate work example to explain those abilities. An illustrative product experience bullet might read:

• Used customer interview notes and support feedback to revise backlog priorities, documented the tradeoffs, and reviewed the proposed sequence with engineering and design.

The value of that description comes from the candidate's actual decision and contribution. If the work happened in a course exercise, label it as a course project. If it happened at work, place it under the appropriate role and describe your own responsibility accurately.

An experienced product manager may give this credential a single line below work experience. Someone transitioning into product work might place it higher, alongside clearly labeled relevant projects. In either case, completing more introductory certificates should not displace stronger evidence of decisions you have made and work you have delivered.

Add public verification without exposing private information

A verification link is useful when it lets the reader confirm the credential directly. Use your own issuer-provided public credential page, not a generic certification information page presented as proof that you hold it.

Before adding a link, open it while signed out. Confirm that it shows the right credential and the information you intend to share. Check that it does not lead to your account dashboard or ask the reader to use your login.

Use descriptive link text, such as Verify credential, beside the text entry. Keep the title and status readable even if the link is not opened. A badge image alone makes those details harder to find and may become unreadable when the resume is copied, printed, or read by resume parsing software.

Never include passwords, access codes, private score reports, or screenshots containing account information. Review the public page for personal details before sharing it. If you do not want to make that record public, omit the optional link and follow the employer's requested verification process instead. Use only a working link to your own credential.

Check your certification section before applying

Read the section as if you have never seen the credentials before. Can you identify the issuer, understand the status, and connect each entry to the job?

Before submitting, confirm that:

• Every title and level matches the official record.
• Earned and expiration dates are accurate today.
• Training, scheduled exams, and expired credentials are labeled clearly.
• Optional verification links work without exposing private account information.
• Your work examples support the abilities you claim separately from the credential.

Keep a private master list of your credentials and verification details, then select the relevant entries for each application. Your resume should give the reader a clear account of what you have earned and what remains unfinished, without requiring them to infer either. For the rest of the document, our step-by-step guide on how to write a resume covers every section.