How Many Skills Should You List on a Resume? We Counted 75,000 Resumes

Ten to fifteen skills, grouped under two or three category labels. The median resume on Simplify lists exactly 15, so half of all job seekers land in that range. The other half is where it gets strange: the mean is 19.4, and 40% list more than 20 skills.

The advice on almost every career site is six to ten. That number is too low, and hardly anyone follows it anyway. The rest of this post covers the full distribution, why the gap exists, and what a tightened skills section looks like next to a bloated one.

What 75,000 real resumes actually list

Most answers to this question, including the one recruiters like me usually give, are a rule of thumb. More than two million people use Simplify, so we counted instead. Across a sample of 75,308 resumes edited on Simplify in the twelve months to July 2026:

• Median skills listed: 15
• Mean: 19.4
• 90th percentile: 44
• 40.0% list more than 20 skills
• 20.5% have no skills section at all (a share that holds even among finished resumes)

The edges matter more than the middle here. If everyone clustered between 12 and 18, the median would be the whole answer and we could stop. Instead there's a long right tail: one resume in ten carries 44 skills or more, which isn't a skills section anymore, it's an index.

Among the resumes that do have one, the most commonly listed entries are Python (62%), spreadsheet tools (41%), Git (40%), and Java (40%). Some of that reflects who uses Simplify, which skews toward students and early-career technical candidates. The rest reflects how the lists get built: people reach for the obvious keyword before anything specific.

Why the advice says 6 to 10 and the resumes say 20

Career sites converge on six to ten skills. Resumes on Simplify run far higher, but don't read our median of 15 as the real answer: our users skew toward students and early-career technical applicants, and a builder makes adding one more skill feel free. The telling number is the overstuffing rate: two resumes in five list more than 20 skills. The cause is keyword anxiety. Everyone applying online has read that applicant tracking systems scan resumes for keyword matches, and the rational response to a black box is to feed it more. If you can't tell which of the twelve tools in a job description the parser cares about, listing all twelve feels free.

Now the part these data posts usually skip. Our numbers describe what job seekers do. They do not describe what gets interviews. We can tell you the median is 15 with real confidence, because we counted. We can't tell you that 15 beats 8, because our outcome data is self-reported by users and wouldn't survive scrutiny. So don't read "the median is 15" as evidence that recruiters want 15. Read it as a snapshot of a lot of people making the same defensive bet.

What we'll argue without outcome data: a 44-item list is worse than a 12-item list. A recruiter gives the page seconds, and every skill you add divides that attention, so the eleven things you're genuinely good at carry the same weight as the tool you opened twice in 2023. Nobody is credible at 44 things, and an interviewer who picks one off the bottom of the list will find that out fast. The ATS argument doesn't hold either, since parsers read the whole document and the keywords in your experience bullets already count. (If that's the real worry, we have a guide to writing an ATS-optimized resume.)

Before and after: 25 items down to 12

Before (25 items in one undifferentiated block, roughly the 90th percentile):

Python, Java, JavaScript, HTML, CSS, React, Node.js, SQL, MySQL, PostgreSQL, MongoDB, Git, GitHub, Docker, AWS, Linux, VS Code, Jira, Agile, Scrum, Microsoft Word, Microsoft Excel, PowerPoint, Communication, Teamwork

After (12 items, grouped):

• Languages: Python, JavaScript, SQL
• Frameworks: React, Node.js
• Data: PostgreSQL, MongoDB
• Infrastructure: AWS, Docker, Linux, Git, CI/CD (GitHub Actions)

The cuts follow a few rules. Git and GitHub are one line, not two. Same for MySQL and PostgreSQL if you only really know one. HTML and CSS are assumed the second you list React. VS Code isn't a skill, it's a text editor. Microsoft Word isn't a skill either, and PowerPoint stopped being one around 2009. Agile and Scrum describe how a team works, so put them in an experience bullet ("shipped biweekly in a six-person Scrum team") where they cost nothing. Communication and Teamwork are claims a hiring manager discounts on sight.

The grouping earns its keep separately from the trimming. A flat list of twelve reads as twelve equal items. The same twelve under four labels tells a recruiter in about two seconds that you're a backend-leaning full-stack candidate who has touched deployment. That's a sentence about you, assembled out of a list. On which items are worth keeping, we maintain a running list of the most important skill keywords for a resume.

The 20% who skip the section entirely

One resume in five in our sample has no skills section. Some of those are people who started a resume and never finished it, and we can't cleanly separate abandoned drafts from deliberate choices, so treat 20.5% as a ceiling on the real skip rate.

Skipping is defensible in a narrow set of cases. A litigator fifteen years into practice doesn't need to tell anyone she can use Microsoft Word. A VP of sales gets evaluated on quota history, not tooling. Where the work is the credential and the tools are assumed, a skills section reads as filler.

For everyone else, dropping it throws away the cheapest real estate on the page. The skills section is the one place a resume says plainly what it can do, in the vocabulary a keyword search uses. Students feel this most: a thin experience section means the skills list is often the strongest evidence available. Default to including one, then keep it short.

Common questions

Should I list soft skills or hard skills?
Hard skills. Tools, languages, platforms, certifications, methods: things that are either true or false about you. Leadership and communication can't be verified in a list, and every applicant claims them, so they cost a line and buy nothing. Put the evidence in your experience bullets.

Should I include proficiency levels?
No. "Python: advanced" starts an argument you can't win, and the scales mean nothing anyway, since one person's "intermediate" is another's "expert." The exception is spoken languages, where "Spanish (conversational)" is a real distinction readers understand. If your proficiency is honestly low, cut the item rather than labeling it.

Where does the skills section go on the page?
Below experience for most people. Above it for new grads, career changers, and anyone whose recent job titles undersell them. The top of the page belongs to whatever is most convincing about you, usually the summary and the roles. Our guide to writing a resume summary covers what sits up there, and a companion post covers whether that summary should be in first person.

Should I tailor my skills to each application?
Yes, and it's the highest-return minute you can spend on a resume. Reordering so the posting's top three tools appear first takes seconds, and adding a skill you genuinely have but left off takes less. Tailoring is the working version of what the 44-item crowd attempts: they list everything once so they never have to think about it again, which is why their lists stop meaning anything.

Let something else keep count

Simplify's resume builder counts the skills on every version of your resume, groups them by category, and flags the ones a specific job posting asks for. It's free, and it beats counting by hand.