Resume Skills: What to List, Where It Goes, and How Many

What the skills section is for

The skills section does two jobs, and persuasion is not one of them. The first is retrieval: it is the densest patch of searchable nouns on your resume, so it is what a keyword filter finds when somebody searches a database for a tool, a system, or a certification. The second is confirmation: a reader who has just finished your bullets uses it to check in about three seconds that the specific thing they need is present.

Nothing in that description says the section proves anything. Proof lives in the experience bullets, where a skill appears with a result attached to it. The skills block is an index to the document, and an index listing chapters the book does not contain is worse than no index at all.

That is the entire design principle. List what a reader would plausibly look up, group it so it can be scanned rather than read, and let the bullets carry the evidence for the handful of skills that decide the job.

Hard skills and soft skills are different claims

A hard skill is a named, checkable thing: Python, NetSuite, telemetry monitoring, GAAP, Salesforce, conversational Spanish, a current license. Somebody can test it or you hold a document for it, and either way it is true or it is not. These belong in the skills section without apology, because they are exactly what a reader searches for.

A soft skill is a claim about behavior, and a list is the worst available place to put one. Written as a bare word - communication, leadership, teamwork - it carries no information at all, because no candidate in history has listed the opposite. Written into a bullet with a scope attached it becomes checkable: mentoring two junior engineers, running the weekly architecture review, handling sixty conversations a day across phone, email, and chat.

The working rule is that hard skills go in the section and soft skills go in the bullets. A short strengths group at the end is defensible when the work history is genuinely thin and behavior is a real part of the evidence, which is why the entry-level example below carries one. It is the exception, not the pattern to copy.

Where the section goes on the page

The default position is below experience, next to education, near the bottom. Your work history is the argument and the skills list is the appendix to it, so moving the appendix to the top pushes the argument down where fewer people reach it.

Three situations invert that. If you are changing careers, the skills are the bridge between what you did and what you are applying for, so they belong high, immediately under the summary. If the role is technical and the stack is the first filter anyone applies, a compact stack block near the top saves a scroll. If you have almost no work history, the skills and education sections are what you have, so they lead.

Wherever it lands, keep it inside the main column of a single-column layout and keep it as ordinary text. Skills placed in a decorative sidebar or drawn as a graphic are among the entries most likely to arrive missing at the other end, and our guide to applicant tracking systems explains why that happens.

How to group them

Two to four groups, each on its own line, each with a label a stranger would understand at a glance. Ungrouped, a skills section is a run-on list the eye slides off. Over-grouped, it becomes an outline that takes longer to read than the bullets it is supposed to summarize.

How many skills are enough

Between eight and fifteen entries across two to four groups is the range that reads well and still covers what anyone is likely to search for. Twelve is a good target for most resumes in most fields.

Past about twenty, the section starts working against you in two ways at once. It stops being scannable, so the entries that matter get lost among the ones that do not, and it begins to look indiscriminate: a candidate listing thirty tools is telling the reader they cannot rank their own abilities. Listing every piece of software you have ever opened is the most common version of this mistake.

The floor matters too. Three entries under a heading looks like a section somebody abandoned halfway. If three is genuinely all you have, fold them into another section or drop the heading and put the strongest one in your summary instead.

Why rating bars say nothing

Templates love the five-dot row, the star rating, the percentage bar beside each skill. They are self-assessed numbers on a scale nobody ever defined, which makes them uninterpretable: your four out of five in Excel and another candidate's three out of five were produced by two different people guessing, and neither is comparable to the other or to what the job actually requires.

They cost you twice over. A bar drawn as a graphic is not text, so it can arrive as blank space in whatever the employer's system extracted from your file, taking the skill name with it when the name is part of the image. And any bar short of full invites the reader to notice a gap, which is a strange thing to volunteer, since nobody has ever been hired for rating themselves three out of five at something.

When proficiency genuinely varies and genuinely matters, say so in words inside the entry: Excel (advanced), Spanish (conversational), Python (basics). One parenthetical carries more information than a row of dots and survives being copied into a plain text field, which the dots do not.

Choosing skills from the posting

A generic skills section is a section written for nobody in particular. The posting is your specification, and it is usually more explicit about skills than about any other part of the job, because skills are the part the hiring manager could write down without thinking.

Declared skills and demonstrated skills

Every skill on your resume sits in one of two states. Declared means the word appears in the skills section. Demonstrated means it appears inside a bullet with a result attached, so a reader can see what happened when you used it and how much of it you handled.

The two are not interchangeable, and the distance between them is where a resume starts reading as thin. Anyone can type SQL under a heading. "Built and maintain the company metrics layer in dbt and Looker, used daily by 40 employees across product, sales, and finance" is the same claim in its demonstrated form, and it is the one an interviewer will open with.

Use the section for coverage and the bullets for depth. The three or four skills that decide the job you are applying for should appear in both places: once as a searchable term, once inside the work that proves it. Anything appearing in neither place has to justify why it is on the page.

What to do with rusty skills

Almost everyone has a few: the language you used daily four years ago, the platform your last employer migrated off, the certification you let lapse. The two wrong answers are listing them flatly as though they were current, and deleting everything that is not fresh this month.

The lists by role below

Underneath this guide are the skills sections from all twelve resumes in our example library, one list per role, each linked to the resume it belongs to. They are there to be read against your own field rather than copied across, because the transferable part is the shape and not the vocabulary.

Look at the ratio first. Nearly every list is one group of methods and one group of named tools, and the methods group is the part specific to the person while the tools group is the part specific to the industry. Look at the length second: none of them runs much past a dozen entries, including the technical ones, which have by far the largest legitimate vocabulary to choose from.

Then look at the entry-level list, the only one carrying a strengths group. That is what a defensible soft-skill list looks like in practice - three entries, placed last, on a resume where the work history is short enough that behavior is genuinely part of the evidence rather than filler.