How to List Skills on a Resume So They Actually Count

Your skills section probably looks like this: Communication. Teamwork. Leadership. Microsoft Office. Problem-solving. Maybe a little progress bar next to each one, filled in to whatever level felt honest the day you wrote it.

It is the fastest part of a resume to write, which is the whole problem. A recruiter skims that block in a second and learns almost nothing, because the same five words sit at the top of half the resumes in the pile. The skills section can do real work, but only if you stop treating it as a place to describe your personality and start treating it as what it actually is: a searchable index of what you can do.

The takeaways

• A skill belongs in your skills section only if it is a concrete noun a recruiter or ATS could search for: a tool, a language, a method, a certification. "Hardworking" is not searchable.
• Most resume guides land on 8 to 12 skills, but relevance beats the count. Mirror the exact wording the job posting uses, and list nothing you could not defend in an interview.
• Soft skills like communication and leadership still matter; they just belong in your experience bullets as evidence, not in a list as adjectives.

Where do skills actually belong on a resume?

In two places, doing two different jobs. The dedicated skills section near the top is a fast, scannable keyword block for the recruiter and the applicant tracking system. Your experience bullets are where each skill shows up in action, with a result attached.

That split matters because the two formats prove different things. A line in your skills section says "I claim to know SQL." A bullet that reads "rebuilt the weekly reporting pipeline in SQL, cutting a four-hour manual job to ten minutes" proves it. The list gets you found and shortlisted; the bullets get you believed. If a skill is important enough to put in the section at the top, it should also appear somewhere below, doing something. A skill that lives only in the list, with no trace of it in your actual history, is the first thing an interviewer probes and the easiest to get caught on.

Which skills belong in the skills section?

The ones a recruiter could type into a search box. Concrete, checkable nouns: programming languages, software, frameworks, certifications, languages you speak, named methods like Scrum or double-entry bookkeeping. If you can picture someone searching a database for it, it belongs in the list.

Here is the test that clears out the clutter. Could a completely different person, in a completely different job, list the same skill with a straight face? "Microsoft Office," "team player," and "detail-oriented" all pass that test, which means they fail yours. Recruiters glance past those words because everyone has them and nobody can disprove them. "Salesforce," "financial modeling," and "Adobe InDesign" are specific enough that they either match the role or they don't. Lead with the hard, role-specific skills the posting names, and cut anything that survives the anyone-could-write-this test. The gap it leaves is usually where a real, nameable skill should go.

How many skills should you list?

Around 8 to 12 is the range most resume guides settle on, but the number matters far less than the match. A tight list of nine skills that mirror the job posting beats a wall of twenty that covers everything you have ever touched. Length is not the signal; relevance is.

The move that makes the section work is mirroring the posting. If the job asks for "data visualization" and you wrote "making charts," change yours to match the words they used, as long as it is true. ATS keyword matching is literal, and a human reading after it is scanning for the same terms. This is the same logic behind tailoring the whole resume to the job description: you are speaking the employer's vocabulary back to them. Just keep it honest. Mirroring their wording is fair game; claiming a skill you would fumble in the first interview question is not.

What about soft skills like communication and leadership?

They count, and they can decide the hire, but a listed adjective is the weakest possible version of them. "Leadership" in a skills block is a claim with no evidence. The same skill shown in a bullet, "led a team of five through a six-month migration with zero unplanned downtime," is something a recruiter can actually weigh.

So move them down the page. Let your experience section carry the soft skills by showing them in motion: a negotiation you closed, a conflict you defused, a process you taught three other people to run. The exception is a soft skill that is really a method with a name, like stakeholder management or Agile facilitation, which is concrete enough to survive in the list. Everything fuzzier, the communication and the teamwork, earns its place through bullets that show impact rather than a tidy row of words nobody believes on sight. A tool like Jobscalr or a careful read of the posting can help you line up the right terms, but the test stays the same: every skill you list should be one you could prove in the room. For more on what recruiters read first, the résumé section of the blog goes deeper.