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

Cut your skills list in half. That is the best advice on which skills to put on a resume, and it takes five minutes. Start with the interview test: read each skill and ask whether you could talk about it for sixty seconds. "Python" survives, because you can describe the script you wrote and the data it cleaned. "Communication" does not, because everyone communicates and no one has a story about it.

A skills section built from concrete abilities (Python, Tableau, AWS, Zendesk) beats a wall of soft adjectives. Delete the vague words first, then build from what remains.

The interview test

Picture an interviewer stopping you mid-conversation and saying, "Tell me about a time you used that." Every skill on your resume should survive that sentence.

A word like "SQL" holds up. You can name the database, the query, the report it produced. "Problem Solving" does not hold up. It describes every job ever posted. The word carries no information, so it earns no space on your page.

Run through your list once. Cut every word that fails. You will end up with fewer skills and a stronger section.

Hard skills vs. soft skills

Naming a tool is useful. Naming a personality trait is not, because anyone can type one and nobody can verify it on a page.

Your skills section holds the concrete things: software, programming languages, certifications, lab techniques, machinery, platforms. These are words a reader can evaluate at a glance. If you either know it or you do not, it belongs in the list.

Soft skills go into your bullet points as evidence, not claims. Do not write "leadership" in a list. Write a line under the job where you led something.

Leadership

Trained 4 new hires and wrote the onboarding guide the team still uses

The bullet on the right is leadership. It cannot be typed by someone who did not do the work. The word on the left can be typed by anyone.

Which skills to put on a resume from the job posting

The posting is a list of what they want, written by the person doing the hiring. If it says Tableau and you know Tableau, that word should appear on your resume in the same form. If it says "Google Analytics 4," do not shorten it to "GA." Match their phrasing exactly.

Your resume is a reply to their posting, and replies work better when they use the same words. Read the posting with your skills list beside it. Highlight every match, then reorder your section so those matches sit at the top.

The limit is obvious, and people cross it anyway. Do not add a skill you do not have because it appeared in the posting. You will be asked about it. Add only the true ones.

Group your skills

A block of forty comma-separated words is unreadable. Three short labelled groups is not. Give each group a heading that tells the reader what kind of skill it contains.

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

Keep each group to one line if you can. Three groups of four skills reads faster than one group of twelve. Lead with the group that fits the posting best.

Delete the star ratings and the progress bars. "Python ★★★☆☆" tells a reader nothing except that you graded yourself. It invites the question of why you did not give yourself five stars. Those symbols also vanish when a file is read as plain text, leaving blanks where your skills should be.

Customer service resume: five skills that pass the test

Customer service roles lean on tools and workflows, not personality words. A line naming the ticketing system you used, such as Zendesk, Freshdesk, or Salesforce Service Cloud, tells a reader you can sit down and start working.

• A CRM or ticketing platform you have used (Zendesk, HubSpot, Freshdesk).
• Live chat or phone system software (Intercom, Five9, RingCentral).
• Data entry speed or a point-of-sale system you can name.
• A second language you can hold a conversation in.
• Scheduling or inventory software specific to your workplace.

Each one is concrete and verifiable. "Empathy" is not wrong, but it belongs in a bullet about a time you solved a difficult case, not in a skills list.

Where the section goes and how long it should be

If you are early in your career or changing fields, put skills near the top of the page. They are the strongest thing you have. You want the reader to see them before your short job history.

If you have ten years of experience, put skills at the bottom. Your work history is the argument. The skills list is the footnote that confirms it.

Either way, keep the section to three or four lines. It should support your resume, not dominate it. A new graduate with no long work history can list four or five honest skills and still have a strong section.

Typing speed, a foreign language, first-aid certification, a specific POS system you used in a part-time job: all of these count. The bar is not impressiveness. The bar is whether you can talk about it for thirty seconds without running dry.

If you are cutting to fit a single page, how long a resume should be is the other half of that decision.

• 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 honest list beats a long fragile one.

A short skills section that survives questioning is worth more than a long one that falls apart in the first interview. Every word you keep should be one you could talk about for a full minute. If you cannot, delete it and move on.