List hard skills and named tools you can evidence — the specific software, languages, methods, and credentials the posting asks for. Eight to fifteen of them, in plain text. Soft skills belong inside your bullets as demonstrated behavior, never in a list, because nobody searches for "team player" and nobody believes it.
The skills section is the most-copied part of a resume and the least considered. Most candidates paste the same fifteen words they used five years ago, half of which are personality traits. Meanwhile the terms a recruiter is actually searching for sit in the job posting, unread.
Below: what separates a skill that works from one that wastes space, a ten-minute method for picking yours, ready lists for eight job functions, before-and-after rewrites that turn soft skills into evidence, placement rules, the skills to delete today, and what to do when you are early career or changing fields.
Key Takeaways
- The test that separates a real skill from filler
- A ten-minute method for choosing yours from any posting
- Starter lists for eight common job functions
- How to convert soft skills into provable bullets
- Six skills to delete from your resume today
What makes a skill worth listing
Start Here
Two tests. Would a recruiter type this word into a search box? And could you survive a follow-up question about it? A skill needs both to earn its line.
Hard skills are specific, teachable, and verifiable: SQL, financial modeling, Kubernetes, Epic, contract negotiation, media buying, GAAP. They pass the search test because they are what recruiters filter on, and they pass the interview test because you either did the work or you did not.
Soft skills — communication, leadership, adaptability — are real qualities that fail both tests as list items. Nobody searches for them, and everyone claims them, so their presence carries no information. That does not mean they do not matter to employers; it means a list is the wrong instrument for conveying them.
Transferable skills sit in between: project management, data analysis, stakeholder management, budgeting. These are worth listing when the posting names them, and they become much stronger when paired with a bullet showing scale. "Stakeholder management" is a claim; "aligned 4 departments and 2 vendors through a 9-month ERP migration" is the same claim with proof attached.
The practical consequence: your skills section should be almost entirely hard skills and tools, and your experience bullets should be where every other kind of capability shows up.
Choose your skills in ten minutes
Do This Next
Generic lists are a memory aid. The postings you want are the answer key, and the first third of each one is where the real requirements live.
- Open three postings for the same role. One posting is a sample of one; three shows you what the market consistently asks for.
- Highlight every named tool, method, and credential. Nouns only. Skip the adjectives entirely on this pass.
- Mark the terms that appear in all three. Those are genuine requirements rather than one hiring manager's wish list.
- Split into can-prove and cannot-prove. Only the first column goes on your resume; the second becomes your learning plan.
- Copy the posting's exact spelling. If it says "A/B testing" and you wrote "split testing," add their form — matching is literal.
The can-prove split is the step people skip and the one that matters most. Listing skills you cannot defend produces screening calls that go badly and burns a relationship with a recruiter who might have had a better-fitting role next month.
Skills by job function: starter lists
Pro Tip
Use these to jog your memory about what you have actually done — not as a list to copy. Anything here you cannot evidence should stay off the page.
- Administrative and office: calendar management, Excel (pivot tables, Power Query), expense reconciliation, travel coordination, vendor invoicing, Concur, SharePoint, minute-taking, document control
- Customer support: Zendesk, Intercom, Salesforce Service Cloud, escalation management, SLA reporting, macro authoring, knowledge base maintenance, CSAT analysis, tier-2 triage
- Sales: Salesforce, HubSpot, pipeline forecasting, MEDDIC, outbound prospecting, contract negotiation, territory planning, renewals, quota attainment, Outreach
- Marketing: SEO, SEM, Google Ads, Meta Ads, Google Analytics 4, marketing automation, lifecycle email, attribution modeling, conversion rate optimization, content strategy
- Finance and accounting: GAAP, IFRS, financial modeling, month-end close, variance analysis, FP&A, NetSuite, SOX compliance, cash flow forecasting, audit support
- Software and data: Python, SQL, Go, TypeScript, React, Kubernetes, Terraform, CI/CD, dbt, Snowflake, Airflow, system design, incident response
- Healthcare: patient assessment, Epic, Cerner, HIPAA, medication administration, care coordination, clinical documentation, triage, infection control, IV therapy
- Operations and supply chain: demand planning, inventory management, S&OP, Lean, Six Sigma, ERP (SAP, NetSuite), vendor management, logistics, process documentation
Two cautions. Some of these are entry tickets rather than differentiators — every analyst lists SQL, so listing it gets you into the pile rather than out of it, and the bullet showing scale is what separates you. And tool names age: a stack from six years ago dates you more than it qualifies you.
Soft skills: show them instead of listing them
Key Takeaway
Every rewrite below deletes an adjective and adds a number. That trade is most of the difference between a resume that reads generic and one that reads specific.
"Excellent communication skills"
Before: Excellent written and verbal communication skills with the ability to present to diverse audiences.
After: Presented monthly performance reviews to a 40-person leadership group; wrote the onboarding documentation now used by every new hire in a 60-person department.
"Strong leadership"
Before: Strong leadership abilities with experience motivating teams to achieve their goals.
After: Led a 9-person support team through a platform migration; cut voluntary attrition from 27% to 6% by restructuring the on-call rota and running weekly one-to-ones.
"Problem solver, works well under pressure"
Before: Natural problem solver who thrives under pressure and adapts quickly to changing priorities.
After: Diagnosed and fixed a billing defect affecting 3,400 accounts during a holiday freeze, restoring correct invoicing in under 6 hours and writing the runbook that prevented a repeat.
Notice that none of the "after" versions names the quality. They do not need to — a reader draws the conclusion themselves, which is considerably more persuasive than being told.
Where the skills section goes, and how it should look
Watch Out
The most common way skills disappear is a decorative sidebar. It looks organized on your screen and extracts as fragments or as nothing at all.
| Choice | Do this | Not this |
|---|---|---|
| Position | Below Experience | In a side column |
| Layout | Full-width, comma separated | Icon grid or table |
| Count | 8–15, posting-weighted | 30 covering everything |
| Levels | Group by category if useful | Star ratings or bars |
| Naming | Full term plus acronym | Acronym alone |
Placement matters because of how systems read the page. Workday builds your candidate profile from the flat text of your file, so a skills sidebar can arrive interleaved into your work history. Greenhouse handles clean single-column PDFs well and extracts nothing usable from icon-based skill ratings; Lever and iCIMS behave the same. Verify with a free ATS resume check — if your skills line is missing from the extracted text, none of the rest of this matters.
On count and structure specifically, see how many skills to list and whether you need a skills section at all .
Check that your skills survived the upload. Sidebars, icon grids, and rating bars are the three ways a skills section vanishes during parsing. See yours in under a minute.
Run a free ATS resume check →Six skills to delete today
Common Mistake
Each of these either matches nothing, signals a thin skill set, or actively dates you. Deleting them makes the remaining skills more visible.
- "Microsoft Office." Assumed. If Excel is genuinely a job requirement, name the specific capability — pivot tables, Power Query, VBA — and drop the rest.
- "Hard worker" and "team player." No search matches them and no reader is persuaded. They are the clearest signal that a resume was not tailored.
- "Internet research" or "email." Listing baseline computer literacy suggests there was nothing better to include.
- Retired or legacy tools. Software nobody has run in a decade dates you without qualifying you, unless the posting specifically mentions a legacy system.
- Skills irrelevant to the target role. Photoshop on an accounting resume raises a question rather than answering one.
- Language claims you cannot back. "Conversational Spanish" will be tested by someone, sometimes mid-interview. State the level accurately or omit it.
Edge cases: early career, career change, senior roles
Reality Check
The standard advice assumes a mid-career professional staying in their field. Three common situations need the section weighted differently.
Little or no work experience
Move skills above experience and be specific about where each one came from. Coursework, a capstone project, a society you ran, a part-time job where you rebuilt a process — all legitimate sources. Name the tool rather than the aspiration: "Python, pandas, SQL, Tableau" beats "data analysis and a passion for insights."
Career changers
Lead with the transferable skills the target field names, and be disciplined about the can-prove test. A match-rate tool will report a dozen missing terms; adding them all produces a resume that collapses under one follow-up question. A lower match with a coherent story converts better than a high one you cannot defend.
Senior and executive roles
Screening runs on scope rather than tools. Budget owned, org size, revenue responsibility, and market exposure matter more than software names, and a VP resume dense with tool listings reads junior. Keep a short skills line if the role names specific systems, and let the numbers carry the rest.
Non-technical roles with no obvious tools
Every role has methods even when it has no software. Case management, conflict mediation, curriculum design, grant writing, inventory cycle-counting, safety auditing — these are hard skills with names, and naming them precisely is what separates a specific resume from a vague one.
Your skills need to match in three places
Quick Win
Recruiters compare your resume against your LinkedIn, and the application form often stores skills separately from your file. Mismatches between the three read as carelessness.
Your resume is the version you control fully, and the one this page is mostly about. Get it right first, because the other two are usually derived from it.
Your LinkedIn skills section is what recruiters search when they are sourcing rather than reviewing applicants, and it works on exact terms in the same way. If your resume says "Snowflake" and your profile does not, you are missing from half the searches that should find you. Mirror the same eight to fifteen terms and reorder so the three most relevant sit at the top, since those are the ones displayed by default.
The application form itself frequently asks for skills in structured fields, separate from your uploaded file. Many portals pre-fill these from your resume and then use the fields rather than the document. Read what got auto-filled before you submit — this is where a parsing error becomes visible and, usefully, correctable. A skill mangled during extraction can be fixed in the form even when the underlying file was imperfect.
Keeping all three aligned takes about ten minutes once and saves you from the specific failure where a genuinely qualified candidate never appears in the search that was looking for exactly them.
Bottom line
Final Word
Hard skills and tools in the list, eight to fifteen, taken from the posting and provable. Every other capability goes inside a bullet with a number attached.
The skills section is small and disproportionately revealing. A list of precise, current, role-relevant tools tells a reader you understood the job. A list containing "Microsoft Office, team player, detail-oriented" tells them the same resume went to forty other companies — which is usually true, and is exactly the impression you want to avoid.
Tonight: open the posting you most want, highlight every named tool and method in its first third, and check each one against your resume. Add the ones you can genuinely prove, delete anything on your current list that the role does not ask for, and move one soft skill into a bullet with a number in it.
See which of your skills actually reach a recruiter
Upload your resume and read the extracted text section by section — including whether your skills line survived. Free, no signup, no scan limit.
Run the Free ATS Resume CheckAlso useful: free resume builder · resume keywords guide
Frequently asked questions
The ones named in the job posting that you can genuinely evidence. Beyond that, hard skills and named tools carry the most weight because recruiters search for them literally — SQL, Salesforce, financial modeling, Epic, Terraform. Generic qualities like "team player" match nothing and persuade nobody.
Demonstrate them rather than declaring them. A skills line reading "communication, leadership, problem-solving" is invisible to a search and unconvincing to a reader. A bullet reading "presented quarterly results to a 40-person leadership group" shows the same qualities and cannot be copied by someone who did not do it.
Eight to fifteen in the skills section, weighted toward what the posting names. Fewer looks thin; thirty looks indiscriminate and buries the ones that matter. If a skill would not survive a follow-up question in an interview, it is costing you space rather than earning it.
Only where it is genuinely part of the job specification, such as administrative or finance roles that require advanced Excel. Listing basic Word and PowerPoint alongside them signals a thin skill set. "Excel — pivot tables, Power Query, VBA" is worth a line; "Microsoft Office" is not.
Tools you have actually used in coursework, projects, or part-time work, plus anything from volunteering. Name the specific software, language, or method rather than the general area. "Python, pandas, SQL, Tableau — used to build a 3-year sales forecast for a class capstone" beats a generic list of aspirations.
No, and they actively hurt. They are graphics, so applicant tracking systems extract nothing from them — your skills become invisible. They are also self-assessed and meaningless to a reader. Plain comma-separated text does the job for both audiences.
After experience for most candidates, since your history is the stronger evidence. Put skills higher only when the role is defined by a specific tool stack, such as many engineering and analytics positions, or when you are early career and have more skills than history.
Read the first third of the posting, where the genuine requirements sit — the bottom is often boilerplate. Then compare three postings for the same role and look for terms that appear in all three. Repetition across postings is a far stronger signal than the length of any single requirements list.
Done for you
Turn this advice into an interview-ready resume
Professional writers rebuild your resume for ATS + recruiters — unlimited revisions, interview guarantee.