Resume skills section: what to include (and what to cut)

Recruiters spend about five seconds on your skills section. They're not reading it. They're scanning for two or three specific words from the job posting, and if those words aren't there, the rest of your resume may never get a real look.

That's the whole game. And yet most skills sections read like someone emptied a junk drawer: "Communication, Microsoft Office, Teamwork, Problem Solving, Leadership." That list tells a recruiter nothing, except that you've seen other resumes.

Here's how to build a skills section that actually earns its space.

What the skills section is for

Two audiences read it, and neither one cares about adjectives.

The first is the applicant tracking system. ATS software screens resumes by matching words and phrases against the job posting. It doesn't infer. If the posting says "Salesforce" and your resume says "CRM software," many systems score that as a miss. Your skills section is the easiest place to get those exact matches in, because it's a plain list with no narrative to work around.

The second audience is a human recruiter doing a fast pass over a stack of resumes. They already know what they're looking for. A staffing manager hiring a payroll specialist scans for "ADP" or "Workday." A marketing lead scans for "Google Ads" and "HubSpot." Your skills section either confirms the match in seconds or it doesn't.

So the section has one job: put the exact skills this employer wants where both readers will find them instantly. Everything else is noise.

Hard skills only (with one exception)

Hard skills are things you can be tested on. Software, languages, certifications, methods, equipment. Excel pivot tables. Python. QuickBooks. OSHA 30. Adobe Premiere. A recruiter can verify these in an interview, so they trust them on paper.

Soft skills are claims. "Detail-oriented" and "team player" cost you credibility because anyone can type them, and everyone does. I've never met a recruiter who shortlisted someone for listing "communication skills."

That doesn't mean soft skills don't matter. It means they belong in your experience bullets, with proof attached. "Trained 4 new hires on the ticketing system" says more about communication than the word ever will. "Led a team of 6 through a warehouse relocation" beats "Leadership" every time.

The exception: if the job posting explicitly names a soft skill as a requirement ("must have strong client-facing communication skills"), include it. The ATS may be looking for that phrase. Just back it up somewhere in your bullets so it doesn't hang there unsupported.

Match the posting, word for word

Open the job description and pull out every concrete skill it mentions. Tools, platforms, methods, certifications. Then check your list against theirs.

Three rules for the matching:

Use their exact phrasing. If they write "search engine optimization," don't write only "SEO." If they say "customer relationship management," a bare "Salesforce" might not register. When in doubt, include both forms: "search engine optimization (SEO)." That covers ATS systems that match on either version.

Mirror their priorities. If the posting mentions Tableau five times and Power BI once, Tableau goes first in your list. Position matters. Some systems weight keywords that appear earlier and higher on the page.

Don't claim what you don't have. It's tempting to paste in every keyword from the posting. Resist it. You'll get asked about each one in the interview, and "I've read about it" is a bad moment to have in front of a hiring manager. If you have partial experience, say so honestly: "Python (basic scripting)" is fine and reads as self-aware.

Group skills into categories

A flat list of 15 skills is hard to scan. Grouped, the same 15 skills read in seconds. Here's what that looks like for a data analyst:

Languages and querying: SQL (PostgreSQL, BigQuery), Python (pandas, NumPy)

Visualization: Tableau, Power BI, Looker

Statistics: A/B testing, regression analysis, forecasting

Tools: dbt, Excel, Git, Jira

And for an office administrator:

Software: Microsoft 365 (Excel, Outlook, Teams), QuickBooks, DocuSign

Operations: calendar management, travel booking, expense reporting, vendor coordination

Records: data entry (10,000+ records migrated), CRM upkeep, filing compliance

Notice the parenthetical details. "SQL (PostgreSQL, BigQuery)" is worth more than "SQL" alone because it answers the follow-up question before it's asked. Same with "Excel (pivot tables, VLOOKUP, macros)" versus just "Excel." Specificity is what separates people who use a tool from people who once opened it.

Three to five categories is plenty. Use category names a recruiter would recognize, not creative ones. "Technical skills" works. "My toolbox" doesn't parse well in an ATS and looks off to a human.

What to cut

Some things actively hurt you:

Microsoft Word, email, internet research. Baseline skills signal that you're padding. The exception is when a posting for an entry-level role specifically lists them as requirements.

Skill bars, star ratings, and percentages. "Excel: 80%" means nothing (80% of what?) and the graphics often turn to garbage in ATS parsing. Words only.

Technology that dates you, unless the employer asks for it. Lotus Notes and Flash tell a story you don't want told. If a legacy system is genuinely relevant to the job (plenty of companies still run on old software), keep it. Otherwise let it go.

Anything you'd fail a basic question about. Every line in this section is an invitation for an interview question. Only list what you can talk about for two minutes without sweating.

Where the section goes

It depends on how much experience carries your case.

If you're early career, switching fields, or in a heavily tool-driven role (development, data, design, accounting), put skills near the top, right after your summary. Your tools are your strongest argument, so make them impossible to miss.

If you're mid-career or senior in the same field, skills can sit lower, after your experience. By then your work history does the persuading and the skills section is confirmation.

Either way, keep it out of headers, footers, sidebars, and text boxes. Some ATS parsers skip those page regions entirely, which means your carefully chosen keywords never get read. One clean column, standard section header ("Skills"), plain text.

The part nobody wants to hear: it changes per application

Here's the uncomfortable truth. A skills section built once and sent everywhere is optimized for nobody. The posting for one analyst job leads with Tableau and stakeholder reporting. The next one leads with Python and experimentation. Same job title, different keywords, and the resume that wins each one looks different.

Reordering and rephrasing your skills for every single application is genuinely tedious. It's the kind of task people skip after the tenth application, which is exactly when it starts costing interviews. If you'd rather not do it by hand, JobTailor does this automatically: paste a job description, and it reorders and rephrases your skills and bullets to match what that specific posting asks for, using only what's actually in your background.

Examples: weak versus fixed

A few before-and-after lines, because this is easier shown than explained.

Weak: "Social media." Fixed: "Meta Ads Manager, TikTok Ads, Hootsuite scheduling, monthly performance reporting."

Weak: "Data analysis." Fixed: "SQL, Excel (pivot tables, Power Query), Google Analytics 4."

Weak: "Customer service." Fixed: "Zendesk (40+ tickets/day), refund and escalation handling, 96% CSAT."

Weak: "Project management." Fixed: "Asana, sprint planning, budget tracking up to $250K, cross-team scheduling."

The pattern in every fix: name the tool, add the proof, drop the abstraction. When a number fits naturally, use it. Numbers in a skills section are rare enough that they stop the scan.

A quick note on certifications and languages

Certifications can live inside the skills section if you only have one or two ("Google Analytics certified," "PMP"). Three or more deserve their own section, because certifications are often exactly what a recruiter is filtering for and they shouldn't be buried mid-list.

Spoken languages get their own line, with an honest level: "Spanish (professional working proficiency)" rather than just "Spanish." Recruiters have been burned by "fluent" too many times to take the bare word at face value.

Checklist before you send

Run your skills section through this:

Every skill in the posting that you actually have appears here, in the employer's exact wording. Acronyms are spelled out once with the short form in parentheses. The most important skills for this job come first. No soft skill stands alone without proof in your bullets. No skill bars, no ratings, no graphics. Nothing listed that you couldn't discuss in an interview. The section sits in the main body of the page, in plain text.

If you want to see what this looks like done for your own resume, you can try JobTailor free. Upload your resume, paste a posting you care about, and compare the tailored skills section against your current one. The difference is usually obvious within a minute, and then you can decide if the manual version was ever worth the effort.

Either way, stop treating the skills section as a formality. For a lot of applications, it's the only part of your resume that gets read at all.