Resume basics
How many skills should you list on a resume?
List eight to fifteen skills, grouped under two or three labels, and choose them because the job posting asks for them. A technical job with a real stack can go to about 20. List skills that can be named and checked: tools, languages, methods, certifications. Put soft skills in your experience bullets, where you can show them instead of claiming them. A longer list gets scanned, not read, and tells the recruiter you couldn’t decide what mattered for this job.
Last updated: September 21, 2026
At a glance
- Most jobs: 8 to 15 skills.
- Technical jobs: up to about 20, in labelled groups (Languages / Cloud and data / Methods).
- Where they come from: the job posting, not everything you’ve ever used.
- What goes in: tools, languages, methods, certifications, spoken languages.
- What stays out: soft skills, star ratings, Word and email, anything you couldn’t be quizzed on.
Not sure which skills the job actually wants? Paste the posting into the free keyword scanner and it lists them for you. No login.
Why more skills doesn’t mean a better resume
Your skills section has two readers and one job. The first reader is the applicant tracking system, which stores your resume so a recruiter’s search for a term finds it. The second is the recruiter, who glances at the section for a few seconds to confirm you belong on the shortlist. The job is to make both of them say “yes, this person has what the posting asks for”. Neither reader gets anything from a longer list. The software doesn’t rank you higher for listing 40 things, and a person scanning 40 items stops after the first line and thinks “padding”.
That’s why the posting sets the number, not your memory. Read the job description, mark every skill it names or implies, keep the ones you genuinely have, and order them with the posting’s priorities first. For most jobs that gives you 8 to 15 items. For a software, data or infrastructure job it can honestly give you 15 to 20, because languages, frameworks, cloud platforms, data tools and methods are all separate, checkable things, and grouping them under labels keeps the section readable. Past 20, the extra items are almost always things the posting never asked for.
Most people list more than this. Simplify counted the skills sections on 75,308 real resumes and found the typical resume listed 15, the average was 19.4, and one resume in ten listed 44 or more. That long tail is the list-everything habit, and it’s the habit to break: the recruiter reading a 44-item section isn’t impressed by the range. They’re hunting for the three items that matter and wondering why they had to.
How many skills to list at each stage of your career
| Your experience | Skills | Where and how |
|---|---|---|
| 0–3 years | 8 to 12 | Above your experience section, since your titles don’t say much yet. Tools and methods from coursework and projects count if you could answer questions about them. No proficiency bars. |
| 3–7 years | 10 to 15 | Two or three labelled groups. Above experience if you’re in a technical field or changing careers; below it when your job titles already make the case. |
| 7–15 years | 10 to 15 (up to 20 technical) | Drop skills that were current ten years ago and aren’t in the posting. Add the ones you now manage or decide on, not only the ones you operate. |
| 15+ years | 8 to 12 | Domain and leadership strengths (P&L ownership, regulatory areas, markets) plus the systems you still need to be found for. Your experience section carries the rest. |
Which skills go in the list, and which go in your bullets?
| In the skills section | In your experience bullets (or left out) |
|---|---|
| Software, languages, platforms and tools (Python, Salesforce, AutoCAD, Excel modelling) | Communication, leadership, teamwork, problem-solving: show them through what you did |
| Methods and frameworks (Agile, GAAP, Six Sigma, A/B testing) | “Attention to detail”, “fast learner”, “hard-working”: never as list items |
| Certifications and licences (PMP, CPA, AWS Solutions Architect, RN) | A skill you used once, years ago, that the posting doesn’t mention |
| Spoken languages with level (Spanish, professional working) | Basic office software (Word, email) unless the posting asks for it |
The skills examples guide has finished sections by job.
When the 8-to-15 rule doesn’t apply
- Software, data and infrastructure jobs can honestly run to 15 to 20 items, because the stack is the qualification. Group them (Languages / Frameworks / Cloud and data / Practices) so the reader can find the row they care about.
- Changing careers? Let the section run a little longer and put it above your experience. It’s the one place your resume can speak the new field’s language before the reader reaches your old job titles.
- US federal and some public-sector applications use their own structured formats and often want detailed skill statements. Follow the application system.
- Academic CVs usually have no skills section at all. Methods and instruments appear in the research and publications record.
- Trades and licensed jobs: lead with your licences, tickets and equipment certifications. Those get checked before anything else is read.
What a good skills section looks like
Data analyst, 4 years: 13 skills in three groups
Analysis & languages: SQL, Python (pandas), R, Excel (Power Query, pivot models)
Visualisation & BI: Tableau, Power BI, Looker
Data & methods: Snowflake, dbt, A/B testing, cohort analysis, stakeholder reporting
Operations manager, 12 years: 9 skills in two groups
Operations: P&L ownership, demand planning, vendor negotiation, Lean / Six Sigma (Green Belt), ISO 9001 audits
Systems: SAP MM, NetSuite, Excel forecasting, Power BI
The version to avoid: 31 items, one line, no groups
Communication, Teamwork, Leadership, Problem Solving, Time Management, Microsoft Word, Excel, PowerPoint, Outlook, Detail-Oriented, Fast Learner, Customer Service, Multitasking, Organisation, SQL, Python, Tableau, Critical Thinking, Adaptability, Reporting, Analysis, Data Entry, Research, Presentation, Collaboration, Planning, Scheduling, Email, Typing, Creativity, Work Ethic
Three of those (SQL, Python, Tableau) are the whole case for an analyst job, and they’re buried at positions 15 to 17 between “Organisation” and “Critical Thinking”.
Mistakes that weaken a skills section
- Listing everything you’ve ever used. The 44-item section exists to avoid a decision. Make the decision. The posting tells you which skills matter.
- Soft skills as list items. “Leadership” in a list is a claim. A bullet that says “led four engineers through a six-month migration” is proof. Move them.
- Proficiency bars, stars and percentages. The software can’t read them, a recruiter discounts anything under full marks, and “Python 70%” means nothing anyone can check.
- Your words instead of the posting’s. If the job says “customer relationship management” and your list says “client handling”, a search for the posting’s term misses you.
- Putting the section in a sidebar or a table. Two-column layouts and tables are the layouts most likely to break applicant tracking systems, and the skills section is exactly the text you most need the software to read. Keep it in the main column.
- Repeating the list in every bullet. Name each skill once in the list and show it once or twice in the bullets, where it did something. The section-by-section guide covers what goes where.
How many skills do real resumes list?
The other side of the count: across 1,981 resumes people compared against a job description on this site, the typical resume was missing 5 of the skills the posting asked for. The problem is rarely too few skills on the page. It’s the wrong ones for the job in front of you.
This is whoever used the tools in that window, not every resume in the world. Data generated 2026-09-22. Free to cite with attribution.
Sources
- Simplify, “How Many Skills Should You List on a Resume? We Counted 75,000 Resumes”: skills sections on 75,308 resumes, typical 15, average 19.4, one in ten listing 44 or more.
- The 8-to-15 range is the working consensus across recruiter and career-services guidance (Zippia 5 to 10, Kickresume, Teal, RateMy.CV 6 to 12); the technical ceiling of about 20 comes from the same sources.
More questions about resume skills
Is 20 skills too many for a resume?
For most jobs, yes. Past about 15, nobody reads the list; they scan it for one or two terms, and a long list tells them you couldn't work out which skills mattered for this job. A technical job with a real stack (languages, frameworks, cloud, data tools) can justify 15 to 20, grouped under labels. Past 20, cut to what the posting asks for.
Should you put soft skills on a resume?
Not in the skills section. 'Communication', 'teamwork' and 'leadership' are claims, and recruiters skip a list of claims. Show them in your experience bullets instead. 'Presented monthly results to a 12-person leadership team' is communication. 'Led a team of four through a system migration' is leadership. Keep the skills section for things that can be named and checked: tools, languages, methods, certifications, spoken languages.
How do you list skills on a resume?
Under a heading called 'Skills' (or 'Technical skills'), in two or three groups with a label each, for example 'Languages', 'Data and cloud', 'Methods'. Separate the items with commas on one or two lines per group. Put the most relevant to the posting first, not alphabetical. Skip proficiency bars and star ratings: applicant tracking systems can't read them, and they invite the reader to discount anything under five stars.
Should skills go before or after experience?
Before experience (right after your summary) if you're in a technical field, changing careers, or your job titles don't say what you can do. After experience for most other people with three or more years in the same field, where your titles and bullets already make the case. Either way, keep the section on page one.
Do my skills need to match the job description word for word?
Use the posting's wording for anything you genuinely have. Applicant tracking systems and recruiters both search for the posting's terms, and 'stakeholder management' won't match a search for 'client relationship management'. Matching the words is fair. Adding a skill you don't have is not, and it falls apart at the first technical question.
Which of the posting’s skills is your resume missing?
The right list comes from the job description. Paste a posting into the free keyword scanner and it pulls out the skills and terms the job asks for, so you can check your section against them. No login, no limit. Have your resume and the posting together? The comparison shows exactly which required skills you’re missing, and the builder lays the finished section out in a format applicant tracking systems read cleanly.