Skills to Put on a Resume (And How to Choose the Right Ones)

The Skills Section Is Not a Brain Dump

The most common mistake with a skills section is treating it as a place to list everything you can do. Microsoft Word, teamwork, communication, time management, Excel, leadership, problem solving. The result is a generic block that says nothing, matches nothing, and gets skimmed past.

A good skills section does two specific jobs. It gives the Applicant Tracking System a dense set of relevant keywords to match against the job description, and it gives the recruiter a fast, credible snapshot of your toolkit. Everything in this post comes back to those two jobs: include skills that are searchable, relevant, and provable. Leave out the rest.

Hard Skills vs Soft Skills

Understanding the difference is the key to building a section that works.

Hard skills are specific, teachable, and measurable abilities. Tools, technologies, languages, certifications, methods. Python, financial modeling, Adobe Illustrator, Spanish fluency, SQL, Google Analytics, CPA certification. These are the skills the ATS searches for and the ones that prove you can do the technical parts of the job.

Soft skills are interpersonal and behavioral traits. Communication, leadership, adaptability, teamwork, problem solving. They matter enormously on the job, but they carry almost no weight in a skills list, because anyone can type "great communicator" and the ATS rarely searches for them.

The rule that follows: your skills section should be mostly hard skills. Soft skills are better proven than listed. Instead of writing "leadership" in a list, show it in a bullet point: "Led a 6-person team through a platform migration delivered two weeks ahead of schedule." The evidence is far more convincing than the label. We dig into this contrast in How to Make a Resume Stand Out.

How to Choose Which Skills to Include

You don't pick skills from a generic list. You pick them from the job description. Here is the process:

1. Read the job posting and highlight every skill it names. Tools, technologies, certifications, methodologies, and the specific competencies it emphasizes.
2. Cross off the ones you don't actually have. Only list skills you can defend in an interview. A skill on your resume is an invitation to be asked about it.
3. List the ones you do have, using the posting's exact wording. If the posting says "project management," write "project management," not "ran initiatives." The ATS matches on the term.
4. Add a few adjacent skills you have that the role would value, even if not named, to round out the picture.

This is keyword tailoring applied to the skills section specifically. For the bigger picture of finding and using the right terms, see What Are ATS Keywords and How to Find Them and How to Tailor Your Resume for ATS.

Format It So the ATS Can Read It

Keep the section simple and parseable:

• Use a plain comma-separated list or a simple bulleted list. No tables, no columns, no graphics.
• Skip skill bars and ratings. Those "Python: 4 out of 5 stars" graphics mean nothing to the ATS and look arbitrary to recruiters. The system can't read the rating, and a human has no way to judge what your "4 out of 5" means.
• Spell out acronyms once. Write "Search Engine Optimization (SEO)" so you match whichever form the posting uses.
• Group skills if the list is long. Categories like "Languages," "Tools," and "Certifications" help a recruiter scan, as long as the layout stays single-column.

The ATS-Friendly Resume Template shows exactly where the skills section sits and how to format it.

Skills Examples by Field

Use these as a starting point, then narrow to what each specific posting asks for.

Software and Tech: Python, JavaScript, SQL, React, AWS, Docker, Git, REST APIs, CI/CD, Agile, system design

Marketing: SEO, Google Analytics, HubSpot, content strategy, A/B testing, paid social, email marketing, marketing automation, Google Ads

Data and Analytics: SQL, Python, R, Tableau, Power BI, Excel, statistical modeling, ETL, data visualization, A/B testing

Finance and Accounting: Financial modeling, GAAP, QuickBooks, SAP, NetSuite, forecasting, variance analysis, Excel, CPA, accounts payable/receivable

Sales: Salesforce, HubSpot CRM, pipeline management, cold outreach, account management, negotiation, lead qualification, forecasting

Healthcare: Electronic Health Records (EHR), patient assessment, HIPAA compliance, medication administration, BLS/ACLS certification, care coordination

Design: Figma, Adobe Creative Suite, prototyping, user research, design systems, wireframing, responsive design, accessibility (WCAG)

Project Management: Agile, Scrum, Jira, Asana, stakeholder management, budgeting, risk management, PMP certification, roadmapping

Notice these are almost entirely hard skills. That is the point.

Skills to Leave Off

Some additions weaken the section:

• Vague soft-skill labels: "hard worker," "team player," "detail-oriented," "self-motivated." Prove these in your bullets instead.
• Obvious baseline skills: "email," "internet," "Microsoft Word" for a professional role. They signal that you ran out of real skills to list.
• Skills you can't back up. Listing a language you barely speak or a tool you used once is a liability the moment it comes up in an interview.
• Outdated or irrelevant tools that don't apply to the job you're targeting.

A Quick Test

Before you finalize the section, run each skill through three questions:

1. Is it relevant to this specific job? If not, cut it.
2. Is it a concrete, searchable skill, not a personality trait? If it's a trait, move the proof into a bullet point.
3. Can I talk about it confidently in an interview? If not, take it off.

Whatever survives all three is worth listing. A tight section of ten to fifteen genuinely relevant, provable hard skills beats a wall of thirty generic ones every time.