Skills to Put on a Resume: Cut the List in Half

Deciding which skills to put on a resume is mostly a deleting problem, not a listing one.

You are staring at a skills section with about thirty things in it. Excel. Communication. Teamwork. Problem solving. Microsoft Office. Time management.

None of those is doing anything for you. Here is how to work out which ones would.

A skill you cannot be questioned about is not a skill

This is the only test that matters. Read each word on your list and ask whether you would be comfortable if an interviewer stopped and said: tell me about a time you used that.

"SQL" survives that. You can describe a query you wrote. "Communication" does not. Nobody has a story about communicating, because everybody communicates. The word carries no information, so it earns no space.

Cut every word that fails the test. Most lists lose half their length in five minutes.

Hard skills belong in a list. Soft skills belong in your job history.

Naming a tool is useful. Naming a personality trait is not, because anyone can claim one and nobody can check it.

So the skills section holds the concrete things: software, languages, certifications, techniques, machinery. Anything a person either knows or does not know.

The soft ones go into your bullet points, as evidence rather than as claims. Do not write "leadership" in a list. Write "trained four new hires and wrote the onboarding guide the team still uses" under the job where you did it. That is leadership, and it cannot be typed by someone who did not do it.

Take the words from the job posting, but only the true ones

The posting is a list of what they are actually looking for, written by the person doing the looking. If it says Tableau and you know Tableau, the word should appear on your resume in the same form they wrote it.

That is not a trick, it is matching vocabulary. Software that scans applications looks for the terms in the posting, and so does the human who skims afterwards.

The limit is obvious and people cross it anyway. Do not add a skill you do not have because it was in the posting. You will be asked about it, and being caught is worse than not matching.

Which skills to put on a resume, grouped

A block of forty comma-separated words is unreadable. Three short labelled groups is not.

• Languages: Python, SQL, JavaScript
• Tools: Tableau, dbt, Git, Jira
• Certifications: AWS Solutions Architect (2025)

Delete the star ratings and the progress bars. "Python ★★★☆☆" tells a reader nothing except that you graded yourself, and it invites the question of why you did not give yourself five. It also disappears entirely when the file is read as text, so half your skills section becomes a row of blank symbols.

Where the section goes depends on how much work you have

If you are early in your career or changing fields, put skills near the top. They are the strongest thing you have and the reader should meet them before your short job history.

If you have ten years behind you, put them at the bottom. Your experience is the argument; the skills list is the footnote that confirms it.

The short version

• Delete anything you could not be interviewed about.
• Concrete skills in the list, personal qualities in your bullet points.
• Match the posting's exact wording, but only where it is true.
• Three labelled groups, no ratings, no bars.
• Top of the page early in your career, bottom of it later.

A short skills section that survives questioning is worth more than a long one that collapses in the first interview. If you are cutting to fit a page, how long a resume should be is the other half of that decision.