Notifications
Clear all

Where exactly do certifications go on a resume — and which ones are even worth listing?

10 Posts
9 Users
0 Reactions
129 Views
FutureTechie
(@futuretechie)
Trusted Member
Joined: 5 months ago
Posts: 53
Topic starter  

genuinely confused about certifications on resume — specifically where they go and which ones recruiters actually care about.
i have:

AWS Cloud Practitioner (in progress)
Google Data Analytics Certificate (Coursera)
An old CompTIA A+ from 3 years ago
A random Udemy course certificate for Python

do all of these belong on my resume? do i put them in their own section or mix them with skills? and does where to put certifications on resume actually matter for ATS?
someone please help 😭



   
Quote
TechTrekker
(@techtrekker)
Trusted Member
Joined: 5 months ago
Posts: 64
 

on the ATS question — yes, where to put certifications on resume matters for parsing.
ATS systems look for standard section headers. if you call your section "Credentials & Learning" instead of "Certifications", some parsers won't categorise it correctly.
stick to: Certifications, Licenses & Certifications, or Professional Certifications — all reliably parsed.
also: always include the issuing body and year. "AWS Cloud Practitioner — Amazon Web Services, 2024" beats just "AWS Cloud Practitioner" for both ATS and human readers. if it's in progress, write "(Expected May 2026)" — don't hide it, most recruiters respect the hustle.



   
ReplyQuote
Diane J. Hurt
(@diane-j-hurt)
Eminent Member
Joined: 5 months ago
Posts: 47
 

from the hiring side — here's which certifications on resume actually move the needle vs. which are noise:
High signal:

AWS / Azure / GCP (any tier)
PMP, CAPM
CFA, CPA, ACCA
Google Analytics, Google Ads
Salesforce certifications
CompTIA Security+ (for cybersecurity roles)
SHRM (HR roles)

Low signal / use with caution:

Generic Coursera/Udemy certificates for mainstream topics
Certificates with no recognisable issuer
Expired certifications (especially in fast-moving fields)
Certifications completely unrelated to your target role

the question i ask as a hiring manager: "Would I recognise this cert and trust what it represents?" if yes — list it. if no — skip or fold it into a skills mention instead.



   
ReplyQuote
8Rookie
(@8rookie)
Eminent Member
Joined: 5 months ago
Posts: 40
 

okay what about certifications that are in progress? do you list them on your resume before you've finished? feels weird to claim something you don't have yet 🤔



   
ReplyQuote
EngineerInTraining
(@engineerintraining)
Trusted Member
Joined: 5 months ago
Posts: 44
 

@8Rookie yes, list in-progress certs — but format matters:
✔ AWS Solutions Architect — Associate | In Progress (Expected June 2025)
✔ Google Project Management Certificate | Coursera — Currently Enrolled
this is completely standard and actually signals to recruiters that you're actively upskilling. i got asked about my in-progress AWS cert in two separate interviews — both times it was a positive conversation starter, not a red flag.
what you should NOT do: list it without the "in progress" note. if someone asks and you haven't passed yet, that's awkward.



   
ReplyQuote
Mandien
(@mandien)
Trusted Member
Joined: 5 months ago
Posts: 47
 

here's the format i use for my resume certifications section — clean, ATS-friendly, easy to scan:
CERTIFICATIONS
──────────────────────────────────
AWS Cloud Practitioner — Amazon Web Services (2024)
Google Data Analytics Certificate — Coursera (2023)
PMP — Project Management Institute (2022, renewal 2026)
CompTIA Security+ — CompTIA (In Progress, Expected Aug 2026)
one line per cert. issuer in there. year in brackets. in-progress flagged clearly.
i used craftresumes.co when i was building my first proper resume and they specifically restructured my certs section this way — before that i had them randomly mixed into my skills list which apparently confuses ATS parsers.



   
ReplyQuote
Shilpi
(@shilpi)
Trusted Member
Joined: 5 months ago
Posts: 48
 

as a hiring manager i want to add: the position of your certifications section on the page matters depending on your career stage.
Entry-level / student: Certifications should be near the top — after summary and skills, before or alongside experience. They're doing heavy lifting to compensate for thin experience.
Mid-level: After your experience section. Your work history is the main story, certs are supporting evidence.
Senior / executive: At the bottom or folded into a brief "Professional Development" line. Nobody hiring a VP wants to read a list of Coursera badges.
this is the part that confuses most people about where to put certifications on resume — there's no single right answer, it shifts with seniority.



   
ReplyQuote
Counconect
(@counconect)
Trusted Member
Joined: 5 months ago
Posts: 45
 

one thing i got wrong for ages: listing certifications that had expired without flagging them.
had my PRINCE2 certification from 2019 on my resume in 2024. recruiter asked me about it in a screening call, i admitted it had lapsed — awkward silence. lesson learned.
options when a cert expires:

Remove it entirely if it's no longer relevant
Add "(Expired 2022)" if the knowledge still signals something
Add "(Renewal in Progress)" if you're actually renewing it

also: some certs don't expire (Google Analytics, most Coursera certs). some do with a fixed window (AWS recertifies every 3 years, PMP every 3 years). know which category yours falls into before you put it on your resume.



   
ReplyQuote
UXDesigner415
(@uxdesigner415)
Trusted Member
Joined: 5 months ago
Posts: 53
 

for design / creative roles — slightly different rules for certifications on resume.
nobody in UX/UI hiring cares much about generic business certs. what they DO care about:

Nielsen Norman Group UX Certification — very high signal
Google UX Design Certificate — decent for entry level
Interaction Design Foundation memberships/certs — recognised in the community
Adobe / Figma specific skill badges — useful but not game-changers

for creative roles, your portfolio link is doing 90% of the work. the certifications on resume section is secondary — keep it short and only include things a UX hiring manager would nod at. resumewritinglab.com helped me figure out which of mine were worth keeping vs. cutting — had 6 listed before, trimmed to 3, actually looked more confident.



   
ReplyQuote
FutureTechie
(@futuretechie)
Trusted Member
Joined: 5 months ago
Posts: 53
Topic starter  

okay wrapping this up with my final decisions based on everyone's advice:
Keeping on my resume:

AWS Cloud Practitioner (In Progress, Expected April 2025) — own dedicated Certifications section
Google Data Analytics Certificate — same section

Moving to Skills mention only:

CompTIA A+ — just noting "CompTIA A+" in my technical skills list since it's older and not directly relevant to my target roles

Removing entirely:

Udemy Python certificate — redundant since i'm listing Python as a skill with project evidence anyway

placing the Certifications section right after my Skills section, before Experience, since i'm entry-level and need these to do some work for me.
thanks everyone — this was way more nuanced than i expected. how to list certifications on resume sounds simple but there's actually a lot of strategy in it 🙏



   
ReplyQuote
Share: