The Resume Skills Section: What to Include (and What to Cut)

The skills section is the most keyword-dense part of your resume, which makes it powerful for getting past Applicant Tracking Systems — and easy to get wrong. Done well, it's a fast match-signal for both software and recruiters. Done badly, it's a wall of fluff that wastes prime space.

Here's how to build one that works.

What the skills section is actually for

Two readers scan it:

1. The ATS, which checks whether your resume contains the skills named in the job description.
2. The recruiter, who glances at it to confirm you have the core tools before reading further.

Both want the same thing: a quick, scannable confirmation that you match. So your skills section should be specific, relevant, and honest — not a comprehensive autobiography of everything you've touched.

Hard skills vs. soft skills

Hard skills are concrete and testable: Python, Salesforce, financial modeling, SEO, Spanish, AWS. These belong in your skills section because they're exactly what an ATS searches for.

Soft skills — communication, leadership, teamwork — are real and valuable, but listing them as words proves nothing. "Communication" on its own is invisible. Instead, demonstrate soft skills in your experience bullets ("Presented quarterly results to a 200-person org") and reserve the skills section mostly for hard, searchable skills.

How to choose which skills to list

Start with the job description. Highlight every concrete skill, tool, and technology it names. The ones you genuinely have are your priority list — and they should appear in your skills section using the exact wording the posting uses.

This matters because ATS matching is often literal. If the job says "Power BI" and you wrote "data visualization tools," you may not register as a match. Mirror their language where it's true.

How to organize it

For most roles, a simple grouped list is best:

Technical: Python, SQL, dbt, Airflow, AWS Analytics: A/B testing, cohort analysis, Looker, Tableau Other: Spanish (fluent), Agile/Scrum

Grouping helps recruiters find what they care about fast. Keep it to the skills that matter for the target role — 10 to 15 well-chosen skills beats 40 generic ones.

Examples by field

• Software engineer: Java, Go, React, PostgreSQL, Docker, Kubernetes, CI/CD, REST APIs
• Marketer: SEO, Google Analytics 4, HubSpot, paid social, email automation, A/B testing
• Data analyst: SQL, Python, Excel (advanced), Tableau, statistical analysis, ETL
• Project manager: Agile, Jira, roadmapping, stakeholder management, risk planning
• Designer: Figma, design systems, user research, prototyping, accessibility (WCAG)

What to cut

• Obvious basics. "Microsoft Word" and "email" signal inexperience, not competence.
• Skill bars and star ratings. "Python ●●●●○" means nothing objective and often breaks ATS parsing.
• Skills you can't back up. If you list it, you can be asked about it in the interview.
• Irrelevant skills. Your unrelated certifications dilute the signal for this role.

The honesty line

List skills you'd be comfortable being tested on. "Familiar with" is fine for tools you've used lightly — just don't imply mastery you don't have. Getting an interview on an inflated skill only sets up an awkward conversation later.

Tailor it to every job (without redoing it each time)

Because the ideal skills section mirrors each job description, the "perfect" list changes from posting to posting. Rewriting it by hand for every application is tedious, which is why most people don't. Landed reads the job description and adjusts your resume — including which skills and keywords to surface — to match each role in under a minute, so your skills section is always aimed at the job in front of you.

Quick checklist

• Mostly hard, searchable skills; soft skills shown in bullets instead.
• Pulled from and worded like the target job description.
• Grouped and scannable, 10–15 skills.
• No basics, no rating bars, nothing you can't defend.

Get this section tight and relevant, and you give both the ATS and the recruiter an instant reason to keep reading.