I get this question in two versions, usually from the same person about six weeks apart. The first version is genuinely about formatting. Where does the section go, does it come before education, how do I write the entry. The second version arrives later and it isn't a formatting question at all: I got certified and I still can't get interviews.
Both deserve an answer, in that order. So the first half of this is the mechanical answer, done properly, with the awkward cases included. The second half is the thing the first half doesn't fix.
We have more than 6,700 mentors listed on MentorCruise and every one was screened before going live, so I've spent several years reading the documents people use to describe themselves professionally, from both sides of that transaction.
The short version
- The format is four fields in one section: credential name as the issuer writes it, issuer, date, credential ID or verification link. Mirror it into LinkedIn's Licenses & certifications section, not Education.
- Put the section above your education if the credential is closer to the job than your degree is. That's most career changers and almost no new graduates.
- List an in-progress certification only with a status word and a booked exam date. List an expired one only if you label it expired. Issuers publish verification tools, so the claim is checkable.
- Formatting mistakes that actually cost you interviews are rare and easy to fix. If a hiring process has gone quiet after you got certified, the credential was almost certainly read and it didn't change the decision.
- The reason it didn't change the decision is usually question two: nobody in the market you're applying to has written the credential into a requirement. No layout fixes that.
How to list a certification on a resume
Where does the certifications section go? Above education if the credential is more relevant to the job than your degree, below your experience either way. Give it a plain heading, keep every credential in that one place, and write each entry the way the issuer writes it. A reader scanning for a named requirement should find it in one glance without hunting.
Where the section goes
A resume gets a scan pass before it gets a read pass, and the scan pass is checking whether you clear the stated requirements. So placement isn't an aesthetic question. It's a question about whether your certification is one of those requirements.
If the job posting names the credential, it belongs high: a short certifications block under your summary, or immediately under your most recent role. If it isn't named anywhere and you're including it as supporting evidence, it goes in its own section after experience.
Against education, the rule I'd use is that whichever one is closer to the job goes first. For someone moving into cloud infrastructure from a history degree, the Terraform credential beats the degree and should sit above it. For a computer science graduate applying to a company that screens on degree, it's the other way round. That's a judgment about your situation, and anyone telling you there's one correct order is guessing about your resume.
Two things I'd avoid. Don't scatter certifications through the document, one in the summary, one under a job, one at the bottom. And don't create a whole section for a single course completion certificate, because a section heading is a promise about what's underneath it. One weak item can live as a line under education without drawing attention to how thin it is.
One more distinction worth making. If you hold an actual license, a professional engineer registration, a nursing license, a CPA, that's a legal permission to practice and it isn't the same object as a vendor exam. Head the section "Licenses & Certifications" and put the license first. Merging a license into a list of vendor exams flatters the exams and undersells the license.
How to word a single entry
Four elements, in this order: credential name, issuer, date, credential ID or verification URL. Written out, an entry looks like this:
HashiCorp Certified: Terraform Associate HashiCorp, March 2026. Credential ID: (the one printed on your certificate)
Use the issuer's exact name for the credential. Not your paraphrase, not the shorthand you use with colleagues. Writing "Terraform certification" when the credential is "HashiCorp Certified: Terraform Associate" costs you the keyword match and reads, to anyone who holds the same credential, like you're describing something you half remember. Where the issuer appends a version or edition number to the exam name, carry the one you actually sat, because that's what the verification record says and it dates the credential for you.
Always name the issuer, even when it seems obvious. This is the one people skip and the one carrying the entire value of the line. A certification is worth what its issuer can enforce, so "Terraform Associate" with no issuer attached throws away the only part of the entry that tells a reader anything. HashiCorp publishes its own certifications against a product HashiCorp builds, and that fact is why the line is on your resume at all.
Date it. An undated credential reads as evasive, because the obvious reason to leave a date off is that the date is bad.
Expand the acronym once. Full name with the acronym in parentheses. The human reads the words, the keyword search finds the acronym, and it costs you four characters.
No adjectives. Not "prestigious", not "advanced" unless the issuer literally calls it that. If a credential needs an adjective to sound like it matters, the adjective is doing a job the issuer couldn't.
How to list a certification that's in progress
You can list one, and you should if you're actually going to sit it. Put it in the same section with an explicit status and a booked exam date: "In progress, exam scheduled for October". The status word is not optional. An in-progress credential listed without one reads as completed, and an interviewer who finds out otherwise has learned something about you that has nothing to do with the exam.
The honest test is whether you've paid for and scheduled the exam. If you have, it's a commitment with a date and it belongs on the page. If you haven't, "in progress" means you watched some videos, and I'd move it to a plain line about what you're currently studying. The risk is lopsided: listing a booked exam gains you very little, and listing a vague one and then getting asked about it costs you a lot, because at that point the interviewer isn't evaluating the certification any more. They're evaluating whether your resume is accurate.
What to do with an expired certification
List it if the work behind it is still relevant, and label it as expired, with the date range. An expired credential isn't a problem in itself. An expired credential presented as current is, because issuers publish public verification tools and anyone who cares enough to look can settle it in about ten seconds.
Red Hat is the clean example. It runs a public verification page where, in Red Hat's own words, "prospective employers, clients, managers, and others can verify someone's Red Hat certification status by entering the person's Red Hat certification ID." You give somebody the ID, they type it in, they see the status. That mechanism exists precisely so a claim on a resume can be checked against a database.
There's a second reason not to chance it. Where partner programs count certified staff, the employer has to check on a schedule, because the company's tier depends on that field being valid. In those environments an inaccurate certification claim isn't a small embellishment. It's something somebody's compliance process will surface.
So: if the credential explains a real period of your working history and the work still counts, keep it with the date range and let it be old. If it's a badge for a product nobody runs any more and it's only there to fill space, cut it. A resume isn't an archive.
How to add a certification to LinkedIn
Use the Licenses & certifications section, not Education. They're different objects and LinkedIn treats them differently. The form asks for the credential name, the issuing organization, the issue date, an expiration date or a "does not expire" option, a credential ID and a credential URL. Fill in every field your issuer gives you material for.
Pick the issuing organization from the dropdown rather than typing it, so its logo attaches. That's LinkedIn's own instruction and it's worth following, because a credential with the issuer's logo beside it reads as a credential, and one without reads as a text string somebody typed.
One mechanical note. LinkedIn's help documentation says the Add to Profile button certification providers use no longer autofills, and that members have to enter the information themselves. If you were waiting for the entry to appear after passing an exam, it isn't going to.
Does the credential ID matter? Exactly as much as the issuer's verification tool does, which varies enormously. For a Red Hat credential the ID is the input to a public lookup, so filling it in converts your claim into something a stranger can confirm. For a course completion certificate from a platform with no verification tool, the ID is a string nobody will ever type into anything. Fill it in when the issuer publishes a way to check it, and add the credential URL wherever the issuer gives you one.
And the question underneath that one, which is whether to put letters after your name. LinkedIn has no suffix field. Its help page says that "currently, LinkedIn profiles don't have a suffix field" and that showing credentials that way means adding them to the Last Name field, with LinkedIn instead pointing you at the certification section or an education entry. For licensed professions where the postnominal is the professional identity, everyone does the last-name thing and it reads normally. For a vendor exam it doesn't. A name field with a vendor acronym stapled to it is the clearest available signal that somebody is trying to make a credential carry more than it does.
The issuer sometimes tells you what you're allowed to say
Almost nobody checks this, and it's where the whole argument shows up inside the formatting question. Google publishes rules for how you may describe a Google Ads certification. Its own help page states that "you're allowed to mention your certification on your resume, business cards, LinkedIn profile, and other social media profiles", and also that "you may only refer to yourself as certified if you, personally, have passed the certification assessments". The same page names which certifications count toward the Google Partner badge and which don't.
Read that as a mechanism rather than as legal boilerplate. Google can define the language you're permitted to use about its credential, because Google controls the credential. It's the same enforcement power that makes the certification worth holding, pointed at how you present it.
Now the inverse. If you go looking for your issuer's rules on how you may describe its credential and there aren't any, that isn't a formatting problem. It's the answer to a different question, and it's the one the rest of this post is about.
Why fixing the formatting rarely fixes the silence
If you got certified and the applications still go nowhere, the format almost certainly isn't why. A certification in a labeled section, named the way the issuer names it, with a date, has been read. The problem isn't that a reader missed it. It's that a reader found it, understood it, and it didn't change what they were going to do.
That's an uncomfortable sentence, and I'd rather write it than let you spend another week moving a section around a page.
The formatting failures that genuinely cost you something are a short list, and you've probably fixed all of them by this point in the post. The credential isn't findable. It's named so loosely nobody can tell what you hold. The issuer is missing. The claim is inaccurate. Everything else in the formatting conversation is preference dressed up as rules.
Here's what's usually happening instead, in the order I'd check it.
Nobody in your market has written the credential into a requirement. This is the big one and it's checkable this afternoon. Open ten job postings you'd genuinely apply for, in the market you actually want, and count how many name the credential. If the count is zero, the credential isn't a gate anywhere in your pipeline, and no amount of prominence turns it into one. You didn't fail to present a key. You presented something that wasn't a key.
The credential is a requirement, and everyone in the pool has it. The opposite problem, and it feels identical from the outside. Where a partner program or a procurement process requires certified staff, everyone who needs the credential goes and gets it, and it ends up doing exactly one thing: stopping you being excluded. It can't distinguish you, because a signal everybody in the room holds carries no information. Moving from "excluded" to "in the pile" is a real change. It just isn't the change you were hoping for.
The document contains no evidence of work. This is the one that actually moves interviews, and the certification can hide it from you, because a credential sits in the same visual register as evidence. What it evidences is that you passed a test designed to be gradeable at scale, which is a different claim from "this person has done the job."
One honest caveat, because I don't want to hand you a diagnosis that's entirely your fault. Sometimes the market in your segment is just bad, and a good resume with a real credential and real work still gets silence for months. That happens. Run the three checks anyway: two of them are free, and the third is the only one you control.
What the certificate was ever going to do
A certification is worth exactly what its issuer can enforce. You've already bought yours, so run that test backwards. Three questions, fifteen minutes, and they'll tell you what the credential in your certifications section was ever capable of doing for you. Most of the time the answer explains the silence far better than any layout decision does.
Question one: who issued it, and do they control the thing being certified? Go and look at the issuer's own site right now. If HashiCorp issued it and HashiCorp builds the product, there's an organization behind the credential with the standing to make employers care. If a training company issued a certificate about a language it doesn't build, nobody lent that certificate any authority and the market prices it accordingly. Go has no official certification. Neither does Rust. That isn't a criticism of the products sold into those gaps, and it isn't your fault for buying one. It's an explanation.
Question two: what does it actually gate? Name the door: a partner tier, a procurement clause, a named requirement in a posting, a filter someone configured. The ten-posting count above answers this. If nothing comes back, the certificate gates nothing, and that's a legitimate thing to have bought. Buying a syllabus with a deadline attached is a reasonable purchase. The damage happens when somebody buys a syllabus believing they bought a key.
Question three: what does it not prove? Judgment under production conditions, and this one comes back the same however the first two went, including for the credentials issued by companies with total control over their own technology. An exam has to be gradeable at scale, which means its answers have to be right in every company on earth. Judgment is precisely the part that changes depending on which company you're in, so it's the part the format has to exclude.
Put the three together and you get the useful version. If your credential came from an issuer who controls nothing, in a market where nobody has written it into a requirement, it was never going to produce interviews and it was never going to matter where you put it on the page. That's harder to be told than "move the section up." It's also the only version that saves you time.
If you're not sure which kind of certification market yours came out of, our router post on what certification you should actually get sorts you into one of four. The specific inventories live on the landing pages: Terraform, Google Ads, CRM, Go, PyTorch, SRE, full stack and robotics.
What actually moves the decision
One piece of work somebody can look at, and a line on your resume that points at it. The certification line says you studied a syllabus. A work line says what happened when you applied it, to something real, with a result attached. Those are different claims, and only one of them survives an interviewer asking a follow-up question.
The practical version is a small edit rather than a rewrite. Leave the certificate where it is, formatted the way the first half of this post describes, then take the thing you built with what the exam covered and put it where results go, with what it did. The project line is what the interviewer will actually ask you about, and you want it to be something you can defend for ten minutes without notes.
Two things make that line land. Name the platform, not the field, because a resume that says "IoT" matches nothing a recruiter is searching for while one naming the protocol, the board and the cloud service matches a job description. And show one failure and the recovery: what broke, what you thought was wrong, what was actually wrong. That's the fastest way to demonstrate the judgment no exam reaches, and almost nobody does it, which is exactly why it works.
Then the part I'd spend money on, and I'll be direct that it's what we sell. Get the work read before an interviewer reads it. An unreviewed project and an unearned certificate are the same category of object: you finished something, and nobody competent has told you whether it's any good. Information isn't the scarce thing here. It's been free for a decade, and the study material for every credential worth holding is published by the issuer. What's scarce is somebody senior looking at your output and saying this part works, this part will fall over, and here's why.
A work review session puts one piece of your work in front of a vetted practitioner who does the job you're aiming at, for a fixed fee and a fixed length. If the resume itself is what you want a second opinion on, work with a resume mentor instead, and if the question is really about direction rather than documents, that's a career mentor. Every mentor is screened before they're listed, and you can read their track record and their reviews before you talk to anybody.
One case where the calculation is genuinely different: if your employer is paying, the money question mostly disappears and different rules apply. That's its own decision, and it's the subject of our companion post on what to do when your employer offers to pay for a certification.
The order to do this in
You have a formatting job and a strategy job, and they go in that order because the first is quick and it removes a variable. Here's the sequence with rough times, so you can stop deliberating and go and do it.
1. Fix the entry. Twenty minutes, once. One section, plain heading. Credential name exactly as the issuer writes it, issuer named, date, credential ID or verification link if the issuer publishes a lookup. Section above education if the credential is closer to the job than your degree. Mirror it into LinkedIn's Licenses & certifications with the issuing organization picked from the dropdown. That's the whole formatting job, and it's finished.
2. Count the gate. Thirty minutes. Ten postings, how many name your credential, write the number down. It's the most informative number in this process and nobody else can give it to you, because it's specific to your market and your level.
3. Run question one on the issuer. Five minutes. The issuer's own website, not a roundup article and not a training provider's landing page. Does the organization that builds the technology publish this exam, or does somebody else? That one check would catch most of the bad certification advice I read in a year.
4. Add one artifact. Build or ship one thing that uses what the exam covered, and put it where results go, with the platform named and one failure documented. This step takes real time. It's also the step that changes outcomes.
5. Get it read before an interviewer reads it, by somebody who has shipped the same kind of thing and will tell you the truth about it.
Steps one through three take an afternoon between them, and they'll tell you whether four and five are urgent. My honest guess, from the shape of the question when people bring it to me, is that step two comes back zero more often than anyone expects, and that finding out is worth considerably more than another week of moving a section around a page.
For the general resume mechanics rather than the certification-specific ones, our guide to resume best practices covers those, and how to build a portfolio that survives code review covers step four properly. If you're deciding whether to buy the next one, which Python certifications are worth it runs the same three questions on a single language.
Frequently asked questions
Where do certifications go on a resume?
In their own labeled section, below your experience, and above your education if the credential is more relevant to the job than your degree is. That's usually true for career changers and usually false for recent graduates in fields that screen on degree. Keep every certification in that one section rather than scattering them, so a reader scanning for a named requirement finds it in a single glance.
Should you put expired certifications on a resume?
Yes if the work behind it is still relevant, and only with the expiry labeled. Issuers publish verification tools, so an expired credential presented as current is checkable in seconds. Red Hat, for instance, runs a public page where employers and clients verify certification status from a certification ID. Keep an expired credential that explains a real period of your history. Cut one that's only filling space.
How do you add a certification to LinkedIn?
Use the Licenses & certifications section rather than Education, since LinkedIn treats them as different objects. The form takes the credential name, issuing organization, issue date, expiration or a "does not expire" option, a credential ID and a credential URL. Pick the issuing organization from the dropdown so its logo attaches, which is LinkedIn's own instruction, and fill in every field your issuer actually gives you material for.
Does the credential ID actually matter?
Only as much as the issuer's verification tool does. If the issuer publishes a public lookup, the ID turns your claim into something a stranger can confirm in one click, and it's worth adding everywhere. If the issuer publishes no way to check a credential, the ID is a string nobody will type into anything. That difference is a decent proxy for how seriously the issuer takes its own credential.
I got certified and I still can't get interviews. What should I fix?
Probably not the formatting. A credential in a labeled section with the issuer named has been read. Open ten postings you'd apply for and count how many name your credential: if it's zero, the certificate gates nothing in your market and no layout changes that. Then check whether your resume shows any work somebody can look at, because that's usually the actual gap.
Is a certification or a portfolio better?
They answer different questions, so the comparison only resolves once you know whether a gate exists. A certification clears a requirement where somebody has written one down, which you can check by counting job postings. Work somebody can inspect is what convinces a person you can do the job. Where no requirement exists, the work does both jobs and the certificate does neither.
