What belongs in the skills section, and what is quietly hurting you

The skills block is the most padded part of most resumes. Here is how to decide what earns a place, why grouping beats listing, and what proficiency bars actually communicate.

Updated 2026-08-05 · 5 min read

The skills section is where resumes go soft. It is easy to write, it fills space quickly, and nothing in it has to be defended by an accompanying result — which is exactly why readers discount it and why it is the first place an experienced interviewer looks for something to probe.

It is still worth having. It is where a recruiter's search terms live, and it is the only part of the document where a tool or a language can appear without an awkward sentence built around it. The problem is not the section; it is that most people treat it as an inventory rather than an argument.

The test for inclusion

Every entry should pass both of these:

Would a reasonable candidate for this job possibly not have it? If the answer is no, it is not a skill, it is an assumption. Microsoft Word, email, internet research, and "computer literate" all fail. Including them does not add a match; it costs you credibility, because a reader now knows you were willing to pad.

Could you be interviewed on it right now? Everything in this section is fair game. A framework you used for two weeks in 2023 is a liability sitting next to skills you actually have, because the interviewer cannot tell which is which and will sometimes pick the wrong one.

Most skills sections lose a third of their entries to the first test and another few to the second. What remains is short, and short is the point — six well-chosen terms carry more weight than twenty-five, because the reader can tell that a judgement was made.

Group them, and label the groups

An undifferentiated run of forty comma-separated terms is unreadable, and it flattens everything to the same importance. Three or four labelled groups solve both problems at once:

Analysis SQL, Python (pandas, statsmodels), experiment design, cohort and churn analysis Tooling dbt, Snowflake, Tableau, Looker, Git Working with people Requirements interviews, written readouts, metric definition

The labels do real work. They impose a structure that shows how you think about your own capability, they let a reader skip to the group they care about, and they make it possible to reorder for a specific posting by moving one line rather than rewriting the section.

Choose labels that mean something for your field rather than generic ones. "Technical / Soft / Other" is a taxonomy that tells the reader nothing. "Clinical / Systems / Unit leadership" tells a nurse manager three things before they read a single term.

Where the line sits between skills and evidence

A useful division: the skills section holds nouns, and the experience section holds verbs.

Tools, systems, languages, certifications and named methods are nouns. They belong in the list, because writing a sentence around each one would be tedious and because a search will be run on them.

Capabilities are verbs, and they belong in the bullets where they can be proven. "Stakeholder management" as a list item is a claim. "Ran the requirements workshops for a change two of the three affected teams had already rejected once" is the same claim with evidence attached, and it cannot be copied by the next applicant.

This is why "leadership", "problem-solving", "communication" and "teamwork" almost always fail in the skills block. Not because they do not matter — they are usually the deciding factors — but because a list is the one place where they cannot be believed.

Proficiency bars, star ratings and percentages

Do not.

There are three separate problems. The scale is uncalibrated, so nobody can tell what your 90% means relative to someone else's 90% or to the job's requirement. The graphic carries no text, so a parser extracts the skill name with no indication of level and your careful distinction disappears. And the format invites the reader to look for the shortest bar, which turns a section that was arguing for you into one that is arguing against you.

If levels genuinely matter in your field, say it in words and attach a duration. "Epic for 3 years, including the 2024 upgrade" is unambiguous, survives parsing, and is far more informative than four filled circles out of five.

How long the section should be

Three to five lines, or three to four labelled groups. If yours is longer, it is either doing the experience section's job or it is padded.

Two situations justify going longer. Deeply technical roles where the stack is genuinely the filter — an infrastructure engineer may reasonably list more tools than a marketing manager. And roles where multiple licences or certifications apply, though those usually deserve their own section rather than being folded in with software.

Two situations justify going much shorter, or dropping the section entirely. When everything you would list already appears naturally in your bullets, the section is duplication. And when you are early enough in your career that an honest list would be three items — in which case three items is the right answer, and padding it to twelve is the most transparent thing you can do on a resume.

Language, licences and the things that are not really skills

A few categories get filed under Skills by default and are usually better placed elsewhere:

Languages. Worth including, and worth being precise about. "Conversational Spanish" and "Spanish, fluent including written patient education" are different claims and only one of them will survive an interviewer switching languages mid-conversation. Fluency claims are tested more often than people expect.

Certifications and licences. These deserve their own section, especially in healthcare, accounting, education, engineering and skilled trades, where they function as a gate rather than a bonus. Burying an active RN licence inside a comma-separated list is a real cost.

Software you administered versus software you used. Worth distinguishing where it is true. "BambooHR (administrator and migration lead)" is a materially different claim from "BambooHR", and the parenthetical costs four words.

A pass to run right now

Open your resume and go through the skills section entry by entry:

Delete anything a competent candidate for this job would certainly also have.
Delete anything you would not want to be asked about.
Move any capability that could be demonstrated into a bullet, and delete the list entry.
Group whatever survives under three or four labels that would make sense to someone in your field.
Put the group most relevant to the posting first.

Most people finish this with a section half the length they started with, and every remaining line pulling its weight. That is the version that helps you, both in the search and in the read.

Try it on your own resume

Open the free builder Run the ATS checker

Keep reading