How many skills should a resume list?

Between eight and fifteen, grouped, and every one of them defensible in an interview. The number matters far less than the rule behind it: a skills section is a search index, not an inventory of everything you have touched.

Why the count has a ceiling at all

Two reasons, and neither is a formatting preference.

• A long list is unreadable, so it is not read. Thirty comma-separated items is a grey block. A recruiter scanning it takes nothing from it, which means the four that mattered got the same attention as the twenty-six that did not.
• Everything on the list is interviewable. If Kafka is on there because you read about it, someone will ask, and the answer you give costs you more than the keyword ever earned. This is the actual constraint.

The count by situation

• Fresher or first job: eight to twelve. You do not have fifteen defensible skills yet and padding to reach a number is visible.
• Two to eight years: ten to fifteen, grouped into three or four categories.
• Senior or specialist: often fewer, not more. At that level the tools are assumed and the evidence is in the job history. A principal engineer listing twenty technologies reads junior.
• Career changer: lean on the transferable ones and cut the rest hard. A list that spans two unrelated careers reads as neither.

Group them, and the count stops mattering

Three or four labelled lines beat one long line at any length, because the labels let a scanner find the row they care about.

Languages — Python, Go, SQL, JavaScript

Data — PostgreSQL, Redis, Kafka, dbt

Infrastructure — AWS, Docker, Terraform, GitHub Actions

Twelve items, three lines, and a reader finds the one they searched for in under a second. Do not use a two-column grid to save space here — two-column layouts and ATS parsing covers what that does to the extracted text order.

What to cut first

1. Anything a professional is assumed to have. MS Word, email, the internet. Listing these is the strongest available signal that the list was padded.
2. Rated bars and percentages. “Python — 85%” is a number you invented about yourself, and it extracts as noise. Drop the graphic.
3. Personality words. Hardworking, team player, detail-oriented. These belong in the bullets as evidence or nowhere — writing bullets that carry evidence is where that work happens.
4. Things you last used six years ago and would not want to again. They attract exactly the roles you are leaving.

Naming the section

“Skills” is fine and is what a keyword search expects. “Technical Skills”, “Core Competencies” and “Technologies” are all acceptable. Avoid inventions like “My Toolkit” or “What I Bring” — a parser maps a recognised heading into a field and does nothing with an unusual one, and the recruiter scanning for the section has to hunt for it.

Where the section actually sits

Below your experience, for anyone with experience. Above it only for freshers and career changers, where the skills are the pitch. The exception is a heavily technical role where the stack is a qualifying filter, in which case a compact three-line block near the top earns its space.

And the list is not where you win the keyword match. The bullets are — a skill named inside a sentence about what you did with it is both a keyword and evidence. Which resume keywords actually matter goes into which ones are worth the space.