Resume skills section: we tested 4 versions against an ATS

Short answer: the number of skills you list barely matters. What matters is whether the words in your skills section are the same words that appear in the job posting. We ran four versions of one resume — the only difference between them was the skills section — through our own ATS parser, and two versions that look nothing alike scored exactly the same.

That result is worth sitting with, because it also reveals what a skills section can't do for you.

Why the advice contradicts itself

Search for how many skills belong on a resume and you'll collect a different number from every page: 8 to 12, 10 to 15, up to 18 for technical roles. The hard-to-soft ratio splits the same way — some say 60/40, others insist hard skills should be 70 to 80 percent of the section.

Nobody is lying. These numbers come from recruiter preference and scanning behaviour, which genuinely vary by industry and by person. The problem is that they get presented as if they were machine requirements — as if listing 15 instead of 12 would push you past a filter. So we tested that claim directly.

What we tested

We wrote one marketing analyst job posting and one resume for a candidate with about four years of experience. We then produced four versions of that resume. The work history, education, and contact details were byte-for-byte identical in all four. Only the skills section changed:

1. Version A — 8 generic soft skills. Communication, teamwork, problem-solving, Microsoft Office, leadership, time management, attention to detail, adaptability. The list you write when you're filling a gap on the page.
2. Version B — 22 skills, kitchen sink. The generic eight, plus every tool and technique the posting mentioned, plus a few it didn't (Python, R, Power BI, Salesforce, Photoshop).
3. Version C — 10 skills, mirrored from the posting. Only terms the posting actually used, and every one of them also backed up by a line in the work history.
4. Version D — no skills section at all. The same ten capabilities, but only demonstrated inside the experience bullets.

We scored all four with the same parser that runs on this site, measuring keyword coverage against the posting. The job posting and resumes were written for the test rather than taken from a real application, so treat the numbers as a demonstration of how the mechanism behaves, not as an industry benchmark.

The results

• Version A (8 generic skills): 22% keyword coverage. The parser matched two terms out of nine. It missed SQL, Tableau, Excel, Google Analytics, and A/B testing — every hard requirement in the posting.
• Version B (22 skills, stuffed): 89% coverage. Eight of nine terms matched.
• Version C (10 mirrored skills, evidenced): 89% coverage. Also eight of nine. Identical to Version B.
• Version D (no skills section): 88% coverage. Seven of nine, and an overall score five points below B and C.

What each result actually tells you

Version A is the real failure mode, and it's the most common one. Eight skills is within every recommended range you'll read. It still scored 22 percent, because the words were generic. "Communication" and "problem-solving" appear in the candidate's list but not as requirements in the posting, so they match nothing. The count was fine. The vocabulary was the problem.

Version D shows a skills section is worth having, but not for the reason you'd guess. Dropping it entirely cost only one percentage point of coverage — the keywords were still there, just inside sentences. What it cost was five points of overall score, from structure, and it costs a recruiter the six seconds it takes to confirm you have the tools before reading anything else.

Version B is the trap. It scores well and reads badly. Listing Python, R, Power BI, Salesforce, and Photoshop on an application for a job that asked for none of them tells a hiring manager you paste the same resume everywhere. Worse, every unearned item is a question you can be asked in the interview.

How to write the skills section

1. Open the job posting and copy out the nouns: tools, platforms, methods, certifications. Those are your candidates, in the posting's own wording.
2. Delete any you can't defend for ten minutes in an interview. This is the whole quality filter.
3. Write what's left, in the posting's spelling. If it says "A/B testing," don't write "split testing." A parser matching strings will miss the synonym.
4. Spell out acronyms once — "Search Engine Optimization (SEO)" — so both the exact-match parser and the human skimming the page find it.
5. For each of your top three or four, check that a bullet in your work history shows you using it. If none does, the skill is a claim rather than evidence.
6. Stop. Whatever number you land on is the right number, as long as every item survived step 2.

What a strong entry looks like

The second version is only two items longer. The difference is that every term came off the posting, and each of the first four is demonstrated in a bullet further down the page.

Where to put the section

Above your work history if you're changing fields or early in your career, where the tools are more persuasive than the job titles. Below it if your recent titles already match the role. Either position parses correctly — what breaks parsing is putting skills in a sidebar, a text box, or a two-column layout, which is a formatting problem rather than a content one. We covered that failure in our ATS parsing walkthrough, and watched a two-column template lose every digit in our open-source template test.

One more thing to skip: proficiency bars, star ratings, and percentages. They carry no information a reader trusts — you assigned them to yourself — and a parser reads a five-star graphic as nothing at all.

FAQ

How many skills should I list on a resume?

As many as survive this filter: the term appears in the job posting, and you could discuss it for ten minutes in an interview. That usually lands between 8 and 14, but the range is a side effect, not a target. Our test found no scoring difference between 10 well-chosen skills and 22 stuffed ones.

Should I include soft skills in the skills section?

Include a soft skill only when the posting names it as a requirement, and use the posting's wording. Otherwise it occupies a line and matches nothing — that's exactly why Version A in our test scored 22 percent. Soft skills are more convincing shown in a bullet about what you did than asserted in a list.

Do I need a separate skills section at all?

Yes, though the margin is smaller than most advice implies. In our test, removing it cost one point of keyword coverage and five points of overall score. The stronger argument is human: it lets a recruiter confirm you have the required tools in a few seconds instead of hunting for them inside paragraphs.

Will listing more skills help me pass the ATS?

Only up to the point where the posting's terms are covered. Past that, extra entries add nothing to the match and start working against you with the person who reads next — every unearned item is a question waiting in the interview.

Should the skills section go above or below work experience?

Above if you're changing fields or early in your career, because your tools argue better than your job titles do. Below if your recent titles already match the role. Both parse fine; what breaks parsing is a sidebar or a two-column layout, not the section's position.

The takeaway

Stop counting. Open the posting, take its vocabulary, remove anything you can't defend, and make sure your top few show up again in your work history. The number you end up with is the right number — and the version of you that a human wants to interview is the one who could not have padded the list, whatever the parser says about it.