What Skills to Put on a Resume (and What to Leave Off)

The skills section is the most abused part of the modern resume. It's where candidates dump every tool they've opened, every soft skill they can name, and every technology they once read a tutorial about — producing a wall of words that tells the reader nothing and, worse, dilutes the few skills that actually matter.

Done properly, it does two specific jobs: it feeds the applicant tracking system the keywords it's scanning for, and it gives a human reader a fast read on whether you're technically qualified. Everything else is padding.

This guide covers how to decide what belongs, what to leave out, where each type of skill should live, and how to align the section with a specific job posting.

Hard Skills vs Soft Skills — and Why Only One Belongs in the List

Hard skills are teachable, specific, and verifiable. Python. Salesforce. Financial modelling. Conversational Spanish. Section 508 accessibility auditing. Someone could test you on them.

Soft skills are behavioural traits: communication, leadership, adaptability, problem-solving, teamwork. They matter enormously in the actual job, and they are close to worthless in a skills list — because every single applicant claims them and none of the claims are checkable.

The practical rule that resolves this:

List hard skills. Demonstrate soft skills. A skills section that says "leadership" is weaker than a bullet point that says you grew a team from three to eleven with no voluntary attrition.

That's not a stylistic preference — it's how the reader's attention works. An asserted trait is skipped; an evidenced one is remembered. The same principle drives most of what we cover in the guide on making a resume memorable rather than merely competent.

How to Choose Which Skills Make the Cut

Work through these four filters in order. Anything that survives all four earns a spot.

1. Is it in the job posting, or clearly implied by it? Open the posting and highlight every named tool, methodology, certification, and technical competency. That list is your starting inventory. Skills that appear in the posting and in your background are the highest-value entries you have.
2. Could you answer a follow-up question about it in an interview? Everything on your resume is fair game. If you'd be uncomfortable being asked "tell me about a time you used that," it doesn't belong.
3. Is it non-obvious for your role? "Microsoft Word" for an office job, "email" for anything, "internet research" — these are assumed. Listing them signals inexperience rather than competence.
4. Have you used it in the last three to five years? A tool you last touched in 2016 is a liability if it comes up. Either drop it or mark it honestly.

Most people find that these filters cut a 30-item list down to somewhere between 8 and 15 — which is the right range. A short list of relevant, defensible skills reads as focused. A long one reads as unfiltered.

What to List, by Role Type

The right skills vary substantially by field. These aren't prescriptive lists to copy — they're examples of the level of specificity to aim for.

Across every row, the pattern is the same: named tools and verifiable competencies beat categories. "CRM experience" is vague; "Salesforce (admin-level, 4 years)" is a fact a recruiter can act on.

Where Each Type of Skill Belongs

Not everything goes in the skills box. Placing each type where it does the most work matters as much as choosing it.

• Dedicated skills section — technical tools, platforms, languages, methodologies, certifications. Keep it near the top for technical roles, below experience for people-facing ones.
• Inside experience bullets — anything you want to prove rather than assert. Leadership, communication, negotiation, analytical judgement. These belong in the story of what you accomplished.
• Professional summary — your two or three signature competencies, the ones that define your professional identity. See the structure in the guide on writing your opening summary.
• A separate certifications section — formal credentials with issuing body and date. Don't bury a PMP or an AWS certification in a comma-separated list.

For the layout itself, group related skills under short sub-labels rather than running everything into one line. Something like:

• Languages: Python, SQL, JavaScript, Go
• Cloud & infrastructure: AWS (EC2, S3, Lambda), Docker, Terraform
• Data: PostgreSQL, dbt, Snowflake, Looker

Grouped lists scan in about a third of the time an undifferentiated block does, and they parse cleanly in applicant tracking systems as long as you avoid tables and columns to build them.

What to Cut Without Hesitation

These entries actively cost you credibility:

• Baseline computer literacy. Microsoft Word, email, web browsing, "computer skills." Assumed for every professional role.
• Unqualified soft-skill adjectives. Hard-working, detail-oriented, team player, self-motivated, passionate. Every applicant writes these.
• Skill rating bars and star graphics. They look designed and they're invisible to automated parsers — the system reads a graphic as nothing at all. More on that in the guide to getting past automated screening.
• Languages you can't hold a conversation in. "Basic French" from school is not a professional skill. Only list languages at working proficiency or above, and say which level.
• Obsolete technology. Unless the posting names it, tools that have been superseded date you without adding capability.
• Anything you couldn't demonstrate on the spot. The interview will find it.

Cutting these isn't just tidying. A shorter list makes the remaining entries more visible, and visibility is the entire function of the section. It's one of the quicker wins on the broader list of resume problems worth fixing first.

Matching Skills to the Job Posting

Applicant tracking systems match strings, not meanings. If a posting says "stakeholder management" and your resume says "working with senior leadership," a keyword-matching system may score that as a miss even though a human would read them as equivalent.

The workflow that closes that gap:

1. Paste the job posting into a document and highlight every named skill, tool, methodology, and certification.
2. Mark each one as: have it and it's on my resume / have it but it's missing / don't have it.
3. Add the second group using the posting's exact phrasing, as long as the claim is honest.
4. For the third group, decide whether the gap is small enough to apply anyway. Most postings list aspirations, not hard requirements — 70% coverage is generally enough to apply.
5. Re-check that the added terms also appear in context somewhere in your experience bullets. A skill that appears only in the list and never in the work history reads as thin to a human reviewer.

Done manually, that's fifteen to twenty minutes per application, which is why most people skip it and send the same document everywhere. Automating the comparison is the fastest fix: paste your resume alongside a posting and the AI returns the specific keyword gaps and a version that closes them. If you're starting from a document that's a mess structurally, the free resume builder gives you a clean skills layout to work from.

One caution worth stating plainly: don't add skills you don't have to improve a match score. Keyword stuffing — including invisible white text with hidden keywords — is detected by modern systems and ends the application immediately if a human catches it. The goal is to describe real capability in the employer's vocabulary, not to manufacture capability you lack.

If you want to see how your current skills section scores against a specific role before you send it, FixResume runs that comparison in about a minute. First optimisation is free, and volume options are on the pricing page.