How many skills should you list on a resume?

Eight to fifteen, grouped into two to four labelled lines. Past about twenty the list stops being a claim and starts being an inventory, and the ones that matter are buried among the ones that do not.

Where should the skills section go on a resume?

Below your experience for anyone with a work history, because the experience is the evidence and the skills list is the index to it. Above it for a first resume or a career change, where the skills are the strongest thing on the page.

Should I put soft skills on my resume?

Not in the skills list, where 'communication' and 'teamwork' are unfalsifiable and every applicant claims them. Put them in your bullets as things you did — led a review across three teams — where they come with evidence attached.

Do skill rating bars work on a resume?

No. A five-dot proficiency meter extracts as nothing at all, so a parser sees the skill name with no qualifier and a human sees a number you assigned yourself. Both readings are worse than the plain list.

What counts as a skill on a resume?

A noun that names something checkable — a language, a tool, a platform, a method, a certification, a spoken language. If an interviewer could not ask you a question that tests it, it is not a skill, it is an adjective.

How to list skills on a resume

Nouns that name checkable things, grouped, two to four lines. Why rating bars extract as nothing, why soft skills belong in your bullets, and what a side column does to the order.

Last reviewed 19 Sept 2026

The short answer

Group them, comma-separate them, keep it to two to four lines — ten to twenty skills for a technical role, fewer for most others. Nouns you can be tested on, never adjectives about yourself, never rating bars. Then make sure the important ones also appear in a bullet, because that is where a skill is proven.

The skills section is the most over-thought and least load-bearing part of a resume. It exists so a reader scanning for one term can find it in two seconds, and so a keyword search retrieves you. That is the whole job.

It is not where you prove you have the skill. That happens in the bullets, attached to work you did.

What goes in it

Nouns that name checkable things. Languages, tools, platforms, systems, frameworks, methods, certifications, spoken languages.

Not adjectives about yourself. “Team player”, “detail-oriented”, “hard-working”, “excellent communication skills” — every candidate writes these, nobody writes the opposite, so they carry no information at all. A screener’s eye passes straight over them and they cost you the space.

Soft skills are demonstrated, not listed. “Communication” in a list means nothing. “Ran the weekly release review for four engineering teams” is communication, and it is in the employment section where it belongs.

The format

Grouped, comma-separated, two to four short lines total. Not a three-column grid, not one skill per bullet, and not rating bars.

Skills · a technical role

Languages: Python, Go, SQL, JavaScript

Data: Postgres, dbt, Airflow, BigQuery

Infrastructure: AWS, Terraform, Docker, GitHub Actions

Three labelled groups, eleven skills, three lines. A reader looking for one term finds it in a glance.

Skills · a non-technical role (marketing)

Channels: SEO, paid search, email lifecycle, LinkedIn Ads

Tools: GA4, HubSpot, Looker Studio, Figma

Languages: English (fluent), Hindi (native)

The category labels are doing real work — they let a reader jump to the group they care about instead of parsing forty comma-separated words. Use categories your industry recognises, not invented ones.

Never use rating bars or star ratings

Three separate problems. The scale is meaningless — nobody knows what four out of five bars means, and the person reading it certainly does not share your calibration. It invites you to advertise your own weaknesses, since anything under full is read as “not really”. And it is a graphic, so it extracts as nothing: the skill name survives and the rating vanishes, meaning the only thing the parser sees is a skill list you could have written in plain text.

What a parser receives from a rating-bar skills block

SKILLS

Python

SQL

Figma

(the bars: nothing — they are shapes, not text)

The design showed five bars, four bars, two bars and three. The text layer keeps the names and drops every rating, so what survived is a plain list with worse layout.

✕ Rating bars

Python ●●●●● · SQL ●●●●○ · Go ●●○○○ · Rust ●○○○○

✓ Proficiency in words

Advanced: Python, SQL. Working knowledge: Go, Rust.

If proficiency genuinely varies and matters, say it in words. It survives extraction and nobody has to guess your calibration.

How many

Ten to twenty for a technical role. Fewer for most non-technical ones.

A list of fifty devalues the whole section, because a reader knows nobody is good at fifty things and stops trusting any individual entry. It also makes the genuinely relevant items harder to find, which is the exact opposite of the section’s purpose.

Cut anything that is assumed. Microsoft Word, email, “the internet”, and in most technical roles Git. Listing an assumed skill reads as having run out of real ones.

Matching the job posting, honestly

Reorder rather than invent. If the posting leads with Kubernetes and you have used Kubernetes, it should not be the fourteenth item — move it forward. That is tailoring and it is legitimate.

The same goes for AI tools, which are now the most padded line in the section — see how to put AI skills on a resume for the version a recruiter believes.

Adding a skill you do not have to pass a filter is a bad trade even ignoring the honesty question: it works exactly as far as the screen, and then you are in a technical interview about it. The people who get caught by this are not caught by the ATS.

A term in the skills list and nowhere else is a weak claim. The strong version is the term appearing in a bullet, attached to something you built with it. A reader distinguishes these instantly. See resume keywords that matter and tailoring to a job description.

Where to put it

Experienced candidates: after employment. Your work is the argument; skills are the index to it.

Freshers and career changers: near the top, above employment. When the work history is thin or points elsewhere, the skills are the most relevant thing on the page. See your first resume with no work experience.

The side-column question

A skills list in a narrow left or right column is a common design and it has one cost worth knowing about. A PDF’s text comes out page by page, and a side column extracts after however much of the main flow fitted onto that page — so the parser can receive your skills after your job history rather than beside it.

For a skills list this is usually survivable: the terms are all still there, and a keyword search finds them wherever they sit. It matters more for anything whose position carries meaning, which is why in our own two-column templates education deliberately stays in the main column — in the rail it would extract after skills and break the Summary → Experience → Education → Skills order that most parsers are calibrated against.

Full treatment in are two-column resumes ATS-safe.

Six things to cut today

Delete on sight

Rating bars, stars, percentage rings, dials.
Soft-skill adjectives with nothing behind them.
Anything assumed for the role.
Skills you last touched eight years ago and could not discuss now.
Duplicates in different clothing — JS, JavaScript, ES6 is one entry.
The word “etc”. It tells a keyword search nothing and tells a human you stopped thinking.

Where this site fits

Skills are a plain field here and the templates render them as text, not as graphics — there are no rating bars to switch on, which is a deliberate omission rather than a missing feature.

Our free checker shows you the text a parser pulls out of your PDF, in full and in order, so you can see for yourself where your skills section landed relative to everything else. That is a more useful answer than any general rule about columns, because it is an answer about your document.

Common questions

How many skills should you list on a resume?: Eight to fifteen, grouped into two to four labelled lines. Past about twenty the list stops being a claim and starts being an inventory, and the ones that matter are buried among the ones that do not.
Where should the skills section go on a resume?: Below your experience for anyone with a work history, because the experience is the evidence and the skills list is the index to it. Above it for a first resume or a career change, where the skills are the strongest thing on the page.
Should I put soft skills on my resume?: Not in the skills list, where 'communication' and 'teamwork' are unfalsifiable and every applicant claims them. Put them in your bullets as things you did — led a review across three teams — where they come with evidence attached.
Do skill rating bars work on a resume?: No. A five-dot proficiency meter extracts as nothing at all, so a parser sees the skill name with no qualifier and a human sees a number you assigned yourself. Both readings are worse than the plain list.
What counts as a skill on a resume?: A noun that names something checkable — a language, a tool, a platform, a method, a certification, a spoken language. If an interviewer could not ask you a question that tests it, it is not a skill, it is an adjective.