The Resume Skills Section: Hard Skills vs. Soft Skills (and What to List)

The skills section is the most misused part of the average resume. It's either an afterthought ("Microsoft Office, communication, teamwork") or a keyword dump forty entries long. Both waste one of the highest-value blocks on the page, because the skills section is one of the first places both recruiters and applicant tracking systems look.

Here's how to build one that earns its space.

Hard Skills vs. Soft Skills

Hard skills are specific and teachable, and someone can verify them in an interview or a work sample: Excel, Python, phlebotomy, QuickBooks, Spanish, forklift operation, Google Ads, AutoCAD.

Soft skills are how you work: communication, leadership, adaptability, time management, problem-solving.

Both matter to employers. But they don't belong in the same place on your resume, and this is the distinction most people miss:

The skills section is for hard skills. Soft skills belong in your bullet points, demonstrated rather than declared.

Why? Two reasons. First, hard skills are what ATS software and recruiters search for: "SQL" is a search term, "team player" is not. Second, a listed soft skill is an unverifiable claim. Every resume says "strong communicator," including the ones written by people who aren't, so the words have stopped carrying information.

Show Soft Skills, Don't List Them

The fix is to move soft skills into evidence. Compare:

• ❌ Skills: "Leadership, communication"
• ✅ Bullet: "Led a 6-person support team and ran weekly syncs with engineering to close the top recurring complaint."

That bullet proves leadership and cross-team communication without naming either, and it shows initiative on top. One exception to the rule: if the job posting explicitly lists a soft skill as a requirement ("strong written communication"), you can echo the phrase once, in your summary or a bullet, so the keyword match exists. Then prove it somewhere real.

What Actually Goes in the Skills Section

Aim for 8 to 15 hard skills, chosen for the job you're applying to, not everything you've ever touched. A useful way to think about candidates:

• Tools and software: Excel, Salesforce, Figma, SAP, Epic, POS systems
• Technical abilities: data analysis, copywriting, budgeting, wound care, contract negotiation
• Certifications and licenses: CPA, PMP, CDL Class A, RN license (these can also live in a separate Certifications section if you have several)
• Languages, with an honest level: "Spanish (conversational)," "French (fluent)"

Order them by relevance to the posting, not alphabetically. The first three or four are the ones a skimming recruiter will actually read.

Formatting That Parses

Keep it simple: a plain list or comma-separated line under a header literally called "Skills." Skip the skill bars, star ratings, and percentage graphics: they're meaningless ("80% of Excel"?) and ATS parsers can't read them. Every ResuPals template renders the skills section as plain, parseable text for exactly this reason.

Tailor It Per Application

Your skills section should shift slightly with every application. Not a rewrite, just a re-sort and a swap. Pull the posting's required skills to the front (the ones that are honestly yours), and swap out the least relevant entries for ones the posting mentions.

Say you're a marketer applying to a role that emphasizes email and analytics. Your generic list might lead with "Canva, Instagram, Hootsuite." For this application it should lead with "Mailchimp, Google Analytics, A/B testing." Same skill set, different spotlight. This is the same twenty-minute tailoring pass we describe in the keywords guide, and the skills section is the fastest part of it.

Three Mistakes That Undermine the Section

1. Listing skills your bullets contradict. If "project management" is in your skills list, some bullet should show you managing a project. Skills with no supporting evidence anywhere on the page read as padding.
2. Including default-level skills. "Email," "Microsoft Word," and "internet research" are assumed for most office jobs and signal a padded list. Exception: if the posting names it, list it.
3. The forty-skill wall. A giant list forces the reader to guess what you're actually good at, and it looks like keyword stuffing because it usually is. Cutting to the relevant dozen makes every remaining entry more credible.

A Quick Worked Example

A posting for an operations coordinator asks for: inventory management, Excel (pivot tables, VLOOKUP), vendor communication, and ERP experience (NetSuite preferred).

A tailored skills section: Inventory management · NetSuite · Excel (pivot tables, VLOOKUP) · Vendor negotiation · Purchase orders · Shipping & logistics · Slack/Asana

Seven entries, four exact matches, nothing the candidate can't back up in an interview. The vendor communication requirement shows up as a bullet instead: "Managed relationships with 12 vendors, renegotiating two contracts to cut supply costs 8%."

That's the whole system: hard skills in the list, soft skills in the evidence, re-sorted per application. If you want the formatting handled for you, the free ResuPals builder includes a dedicated skills section in every template, and Pro's job tailoring can do the re-sort against a posting automatically.