How to List Skills on a Resume (ATS-Safe)

You've rewritten your bullet points. You've fixed your summary. And then you hit the skills section and freeze — because nobody agrees on what goes there. Fifteen keywords? Three categories? A row of little progress bars showing you're "90% Excel"?

Here's the honest version: your skills section isn't a personality test or a brag wall. It's a short, scannable answer to one question a recruiter and a parser are both asking — does this person have what this role needs? Get the terms right and it works for you. Get cute with it and it quietly works against you.

This is how to list skills on a resume so the right ones survive the software and read clearly to the human who opens your file next.

Why the skills section matters more than you think

When a role pulls a thousand applicants, nobody reads a thousand resumes. The applicant tracking system — Greenhouse, Workday, Ashby, Workable — organizes the pile, and recruiters run searches against it: does this candidate have skill X? A clean skills section is where that question gets answered fastest.

Two things to keep straight before we go further. First, the ATS does not reject your resume on skills — that's a myth worth killing (more on that below). Second, recruiters are usually not experts in the role they're hiring for. A recruiter staffing a finance or ops seat probably doesn't do that job themselves. So your skills section has to tell a story a smart non-expert can follow — matching the exact words from the posting, not the fancier ones you'd use among peers.

The three types of resume skills

Almost every skill falls into one of three buckets. Knowing which is which keeps your section honest and organized.

Hard skills — specific, teachable, usually provable. Think SQL, financial modeling, Salesforce, Google Analytics, Spanish fluency. These are the ones a parser matches most reliably and a recruiter searches for by name.
Soft skills — how you work with people and problems: stakeholder management, written communication, prioritization. Real, but hard to verify from a list, so they land better proven in a bullet point than declared in a tag.
Tools and platforms — the software and systems of your craft: HubSpot, Jira, Figma, Tableau, NetSuite.

The hard-skills-vs-soft-skills question on most resumes isn't "which should I list" — it's "where." Hard skills and tools earn a dedicated skills section. Soft skills earn their keep inside your experience, where you can show them rather than claim them.

What type of skill is this? A quick test

Stuck on whether something belongs in your skills list? Ask: could a recruiter search for this exact word, and could I prove it in an interview? "Negotiation" — vague, hard to search, better shown. "Contract negotiation with enterprise vendors" — specific, provable, and now it's really an experience bullet, not a tag. If a word only means something wrapped in context, it belongs in your bullets, not your skills box.

How to pick the skills that actually matter

Here's where most people go wrong: they list the skills they have, or the ones they're proud of, instead of the ones this role is asking for. Your skills section should change per job — because the job description already tells you what to put in it.

Start by reading the posting the way a recruiter wrote it. We walk through the full method in how to read a job description for resume keywords, but the short version: pull the must-have skills, tools, and certifications it names, separate them from the nice-to-haves, and use the posting's exact phrasing. If it says "Google Analytics 4," don't write "web analytics." Mirror the term.

This is the part DashApply's gap analysis is built for. Paste a job link or description, and it shows the skills and keywords the role wants that your resume is missing, plus a live match score. You're not guessing which terms matter — you're seeing them, then deciding which ones are genuinely true for you. (It never adds a skill you don't have. That's your call to make, every time.) If you'd rather find the terms by hand first, the job description keyword finder approach covers that pass too.

How to structure your skills section

Keep it near the top third if you're early-career or pivoting and the skills are your pitch — lower if your experience does the heavy lifting. Group related skills under short labels so a skimmer gets the shape in two seconds:

Technical: SQL · Python · Tableau · Google Analytics 4
Marketing: SEO · HubSpot · A/B testing · email automation
Languages: English (native) · Spanish (professional)

Plain text. Comma or dot separators. No tables, no columns, no graphics. The parser reads this cleanly; so does the human.

Which layout fits you?

Dedicated skills block — best for technical and tools-heavy roles where a recruiter searches by exact term. Clear, searchable, fast.
Skills woven into experience — best for senior and leadership roles, where how you used a skill matters more than that you own it. We get into this in tailoring a resume for senior roles.
A short block plus proof in bullets — the one most people should use: a tight skills section for searchable hard skills, soft skills demonstrated below.

One layout to avoid entirely: skill bars and star ratings. "React ★★★★☆" means nothing — you set the rating, so it carries zero signal, and the graphic can scramble in a parser. Say the skill plainly and let your bullets prove the level.

The skills employers want in 2026

The specific technical skills for your resume depend on your field, but the categories hiring keeps rewarding right now:

Data fluency — reading and acting on numbers, whatever the tool (Excel, SQL, GA4, Tableau).
AI-adjacent competence — using AI tools in your actual workflow. Recruiters increasingly read this as a signal of how you'll work, not a gimmick.
Clear written communication — the quiet durable one, especially for remote roles. If you're applying remote, tailoring your resume for a remote job covers the async and self-management signals worth surfacing.

But "top skills of 2026" lists are a trap if you copy them blindly. The best skills to put on your resume are the overlap between what you can prove and what the posting names. Everything else is padding.

Resume skills examples that work

Marketing analyst

Analytics: SQL · Google Analytics 4 · Looker · Excel (advanced)
Marketing: paid search · SEO · marketing attribution · A/B testing
Tools: HubSpot · Salesforce · Asana

Operations manager

Operations: process design · vendor management · capacity planning
Systems: NetSuite · Jira · Tableau · Excel

Notice what's missing: no "team player," no "detail-oriented," no "hard worker." Those aren't skills a recruiter searches for — they're claims you prove in your resume achievements, with scope and numbers behind them.

Best practices for your skills list

Mirror the posting's exact terms. "Customer success," not "client happiness."
List skills you can defend in an interview. If you can't speak to it for two minutes, it doesn't go on.
Keep it tight — roughly 8–15 skills, grouped. More than that and nothing stands out.
Match your resume to your LinkedIn. Recruiters cross-check, and a skills section that contradicts your profile reads as noise.

Mistakes that make a skills section forgettable

The usual suspects, and why they cost you:

Listing every skill you've ever touched. A 30-item wishlist buries the five that matter. We go deep on picking the right ones in the resume skills section that passes ATS.
Soft skills with nothing behind them. "Leadership" in a tag box convinces no one; a bullet about leading a 6-person launch does.
Fancy formatting that breaks parsing. Icons, bars, and multi-column skill grids look polished and read as garbage to the software. If you love a two-column look, read whether two-column resumes are actually ATS-friendly before you commit.
The same generic skills on every application. If your skills section never changes per role, it's not tailored — and a flat, one-size-fits-all resume is a common reason people aren't getting interviews.

A quick skills-section makeover

Before:

Skills: Hard worker, Team player, Microsoft Office, Communication,
Leadership, Fast learner, Problem solving, Detail-oriented

After (for a marketing-analyst posting):

Analytics: Google Analytics 4 · SQL · Excel (advanced) · Looker
Marketing: SEO · paid search · A/B testing · HubSpot

Same person, same career. The second version answers the recruiter's search; the first answers nobody's. The soft skills didn't disappear — they moved into the experience bullets, where "communication" became "wrote the weekly exec dashboard read by 40 stakeholders."

Regional notes: US, Canada, UK, Australia

There's no single global-correct resume. For the US and Canada, skip personal details, photos, and age — bias risk, and norms expect them gone. The UK and Australia are broadly similar for most office roles, with "CV" the common word for the same highlights document. Wherever you are, the skills-section principle holds: match the language of the local posting and the sector. When in doubt, mirror what the job description itself uses.

Advanced: make your skills work twice

Once the basics are solid, two levers raise the ceiling:

Put searchable hard skills in two places — the skills block and naturally inside the relevant bullet. A recruiter's search hits either, and the bullet gives it context. (Repeat honestly, don't keyword-stuff.)
Pair each skill with evidence where it counts. "Tableau" in your list, "built the self-serve Tableau dashboard that cut reporting time 60%" in your experience. The bullet proves the tag. If you're short on numbers, quantifying a resume without metrics shows how to use scope and frequency instead.

Your skills-section action plan

Read the target job description and pull the exact skills, tools, and certs it names.
Keep the hard skills and tools you can genuinely prove; cut the rest.
Group them under 2–3 short labels in plain text — no bars, no tables.
Move soft skills into your experience bullets, backed by scope or numbers.
Check your skills match your LinkedIn, then tailor again for the next role.

When you've got the terms down, the whole page still has to match the job. See how to tailor your resume to a job description for the full pass — and if the manual version wears you out, DashApply's role-specific tailoring runs it against your real experience, shows you the gaps, and lets you review and edit every line before you download. It's free during early launch, no card required.

FAQ

How many skills should I put on a resume? Roughly 8–15, grouped under short labels. The goal is the skills this role asks for, not everything you've ever done — a long wishlist buries the few that matter and reads as padding to a recruiter.

What's the difference between hard skills and soft skills on a resume? Hard skills are specific and provable (SQL, financial modeling, Salesforce); soft skills are how you work (communication, prioritization). List hard skills in a dedicated section where a recruiter can search them. Prove soft skills inside your experience bullets instead of declaring them in a tag box.

Do ATS systems reject resumes based on the skills section? No. An ATS organizes applicants and lets recruiters search by skill — it doesn't produce an "ATS score" or auto-reject your resume on skills. The one real auto-reject is knockout questions on the application form (visa and work authorization), not your skills list. "ATS score checkers" are selling a number no ATS actually produces.

Should I use skill bars or ratings to show proficiency? No. You set the rating yourself, so it carries no signal, and the graphic can scramble in a parser. Name the skill plainly and let a bullet point prove the level — "built the quarterly Tableau dashboard" beats "Tableau ★★★★☆."

What technical skills should I put on my resume in 2026? Only the ones that overlap with the specific job posting and that you can defend in an interview. Data fluency and AI-adjacent competence are broadly rewarded, but copying a generic "top skills" list without matching the role just adds noise. Pull the terms from the posting itself.