Skills section resume decisions come down to one test: could you be tested on it tomorrow without flinching? If not, it does not belong in the list. The section is a searchable index, not a personality statement.
Specs at a glance
- Count: 8 to 20 job-matched hard skills for most roles, up to 25 or 30 when a technical stack genuinely demands it, grouped by category rather than listed as loose tokens.
- Composition: tools, platforms, certifications, languages and domain competencies. Testable things.
- Wording: copied from the posting. Matching systems often index exact phrases rather than synonyms.
- Skills-based hiring reached 70% of employers in 2026, up from 65%, per the NACE Job Outlook 2026.
- Soft skills are contested: 41.4% of recruiters in a Novoresume HR survey said they like seeing them in a dedicated section, while most parsing guidance says keep them in your bullets.
- 10.7% of job seekers admit listing a skill they cannot actually perform, per Novoresume’s 2026 Resume Report. Hard skills are the worst category to inflate because they are the testable ones.
- Placement matters as much as content: Workday often stores skills in a separate searchable field, and Greenhouse weights recent roles, so priority tools belong in both places.
What is the skills section actually for?
Retrieval. A recruiter with 300 applications does not read skills sections, they search them, and your list either contains the term they typed or it does not.
That single fact settles most of the arguments. It explains why exact wording beats elegant wording, why “Microsoft Office” is weaker than “Excel (pivot tables, Power Query)”, and why adjectives like results-driven occupy space that returns nothing.
It also explains the second audience. Once a human opens the file, the same list has about four seconds to say what kind of professional this is. A section that does both jobs is specific, grouped, and short enough to absorb at a glance.
Teardown one: a skills section doing nothing
Here is a composite of what arrives most often, drawn from client documents rather than any one person’s resume.
Composite from client intake, not an individual document. The pattern appears in roughly half the resumes that arrive.
Notice that nothing in that list is false. The person may well be organised and hard working. The problem is that the claims are unfalsifiable, which makes them worthless as evidence and invisible as search terms.
Why does every guide give a different number?
Because the number is the wrong unit. Published advice ranges from 8 to 12, 10 to 15, 8 to 20, and 15 to 25 for technical stacks, and each range is presented with equal confidence.
The spread tells you the answer is conditional. A staff nurse and a platform engineer do not have comparable lists, and a single target number would be wrong for at least one of them.
The method that survives across role families: mine the posting’s requirements section, list the must-haves you genuinely hold, add the adjacent tools you use weekly, group them, and stop. If that produces nine entries, nine is correct. If it produces twenty-four grouped into four categories, that is correct too.
The stopping rule: stop when the posting’s must-haves are covered, not when the section looks full. Padding past that point lowers the average credibility of everything above it.
What skills can you put on your resume, by role family?
| Role family | Typical count | Grouping that works |
|---|---|---|
| Software and data | 15-25 | Languages / Cloud / Data / Practices |
| Healthcare and clinical | 10-16 | Clinical / Systems / Certifications |
| Finance and accounting | 10-18 | Systems / Reporting / Regulatory |
| Marketing | 10-16 | Channels / Platforms / Analytics |
| Operations and supply chain | 10-16 | Systems / Methodologies / Compliance |
| Executive | 8-12 | Domain / Governance, no tool lists |
| Early career | 8-12 | Ungrouped, tools and coursework-backed skills |
The executive row is the one people get wrong. At that level a long tool list reads as operational rather than strategic, and the section should carry domain and governance nouns instead: P&L ownership, turnaround, post-merger integration, regulatory exposure.
Should soft skills go in the skills section?
The orthodoxy says never, and the orthodoxy overstates it. Most parsing guidance argues that soft skills belong in your bullets, where an outcome can demonstrate them, and that argument is sound.
But 41.4% of recruiters in a Novoresume HR survey said they like seeing soft skills listed in a dedicated section, which means a blanket rule is wrong for something close to half the people reading.
The reconciliation is placement and volume. Two or three soft skills the posting explicitly names, at the end of the list, cost you nothing. Eight of them at the top, with no supporting evidence anywhere in the document, are what the orthodoxy is actually objecting to.
The deciding question is whether your experience section proves it. Communication as a bare word is noise. The same word is fine when a bullet below it says you built training materials used by 120 people.
Teardown two: the same person, rebuilt
The rebuild invented nothing. It named what the first version described generically.
One detail worth copying: the language entry carries a level. A bare “Spanish” tells a reader nothing about whether you can run a meeting in it, and recruiters read the unqualified version as weaker than it probably is.
The same applies to credentials. A certification with the year attached is verifiable and signals currency, while a floating acronym raises the question of whether it lapsed.
Where else do your skills need to appear?
In the bullets, and in the application form. Treating the skills section as the only home for your capabilities is the most common structural error I see.
Workday commonly stores skills in a distinct searchable field, separate from the experience text, and that field is populated from the application form rather than from your design decisions. If you skipped it during the application, you are missing from searches that hit that field.
Greenhouse weights recent roles heavily, which means your priority tools should appear in your current job’s bullets as well as in the list. A skill that appears only in a sidebar can read as historical.
And the phrasing should match the posting, since exact-phrase indexing is common and synonym handling is inconsistent. If they wrote “revenue cycle management” and you wrote “billing operations,” you may simply not come back in the result set. The guide to what an ATS actually does covers why this is a searchability problem rather than a rejection one.
What should you cut?
Anything you would not want tested. Novoresume’s 2026 report found 10.7% of job seekers admit to listing a skill they cannot perform, and hard skills are the worst possible category for that gamble because verification is routine: the Excel test, the take-home, the certification check.
Cut software everyone has. Listing email or web browsing as skills actively dates you, and basic office suites only earn space when the posting names a specific advanced function.
Cut duplicates across categories. The same competency phrased three ways looks like padding to a human and adds nothing to a search.
Cut anything you last touched six years ago unless it is a named requirement. Currency matters more than coverage, and a long tail of stale tools dilutes the ones you use now.
Once the list is honest, the proof belongs downstairs. Turning a listed skill into a defensible line is covered in the piece on writing bullet points that survive scrutiny, and how far to re-cut the list per application is in the tailoring framework.
Sources and limits
Skills-based hiring adoption comes from the NACE Job Outlook 2026. Self-reported skill inflation and the recruiter preference on soft skills come from Novoresume’s 2026 Resume Report and its HR survey. Count ranges and parser behaviour on Workday and Greenhouse are drawn from published practitioner guidance, which is consistent on the mechanism and inconsistent on the numbers, as the article states.
Two limits. Both teardowns are composites assembled from patterns across client documents rather than any individual’s resume, so they illustrate rather than evidence. And no controlled study exists comparing skills-section formats against interview outcomes, so the guidance here is drawn from screening practice and parser behaviour, not from a measured effect.
Questions about the resume skills section
How many skills should I list on my resume?
Between 8 and 20 for most roles, and up to 25 or 30 for genuinely deep technical stacks when grouped by category. Cover the posting’s must-haves you actually hold, then stop.
Should the skills section go at the top or the bottom?
Top for technical and certification-driven roles where the tools are the qualification. Below experience for senior and leadership roles, where scope matters more than tooling.
Do I need a different skills section for every application?
Not a rewrite, but a reorder. Moving the three skills a posting emphasises to the front takes under a minute and is the highest-return edit available.
Should I include proficiency ratings or star bars?
Avoid graphical bars, which parse badly and mean nothing consistent. Written levels work for languages, where standards exist, and rarely help elsewhere.
Where do certifications belong, in skills or their own section?
Their own section once you hold more than two, or inside skills with the year attached when the list is short. Dates matter because they signal currency.
Can I list a skill I am currently learning?
Only with the status visible, such as a certification in progress with an exam date. Listing it plainly invites a question you cannot answer well.
Does a skills section help with AI screening tools?
It helps with retrieval, since these systems index the terms you supply. It does nothing for credibility, which is decided by whether your experience supports the claims.
The honest version is usually stronger
Most people underclaim in this section, listing categories where they hold specifics. Pulling the real tools and credentials out of someone’s history is what a structured intake is for. Book a free consultation, or see the services and pricing. If applications are going quiet across the board, start with the funnel diagnostic.
About the author. Dustin Harvey is a Certified Master Resume Writer (CMRW, CARW, CPRW) with an MBA in HR Management and roughly a decade on the hiring side, where he ran the searches that skills sections either answer or miss. He writes career documents for professionals from early career through the C-suite at HotResumeJob. Background is in the about section, client outcomes in the reviews, common questions in the FAQ, and further writing on the blog.