Deciding which skills to put on a resume is a selection problem, not a collection problem. Almost everyone's raw list is too long — a decade of work generates fifty things you can plausibly do — and the instinct to include all of them is exactly what makes skills sections invisible. A recruiter scanning a 30-item list assumes you padded it. A recruiter scanning a tight, job-matched list of ten assumes each one is real. This guide gives you the master list to pick from, and more importantly, the filter to pick with.
How recruiters actually read a skills section
Two audiences look at your skills section, and they use it differently.
Recruiters use it as a verification panel. They arrive with a mental checklist from the job description — three to six must-haves — and scan your list to tick them off. They spend seconds, not minutes. A skill they are not looking for earns you nothing; a missing skill they are looking for costs you the tick.
The applicant tracking system uses it as searchable text. When a recruiter searches their candidate database for "Salesforce" or "phlebotomy," the skills section is one of the places that term needs to exist on your resume. That is the extent of the machine's involvement — it indexes, humans decide. Our guide to finding the right resume keywords covers how to identify which terms a specific posting is really asking for.
Both audiences reward the same thing: a short list where every item maps to the job. Neither rewards volume.
The 120-skill master list, organized by category
Use this as a menu, not a template. The point is to jog your memory, then select ruthlessly.
Data and analysis
Excel (advanced formulas, pivot tables), SQL, Python, R, Tableau, Power BI, Looker, Google Analytics, A/B testing, forecasting, financial modeling, statistical analysis, data cleaning, dashboard design, reporting automation.
Software development and IT
JavaScript, TypeScript, Java, C#, Go, REST APIs, Git, CI/CD, Docker, Kubernetes, AWS, Azure, Linux administration, network troubleshooting, SQL databases, test automation, debugging, code review.
Marketing and communications
SEO, paid search, paid social, email marketing, marketing automation (HubSpot, Marketo), copywriting, content strategy, brand positioning, CRM management, conversion optimization, media relations, event marketing, social media analytics.
Sales and customer success
Prospecting, discovery calls, pipeline management, Salesforce, contract negotiation, objection handling, account expansion, renewal management, CRM hygiene, territory planning, demo delivery, churn analysis.
Operations and project delivery
Project planning, budgeting, vendor management, procurement, process mapping, Lean, Six Sigma, inventory management, logistics coordination, scheduling, risk tracking, Jira, Asana, resource allocation, SOP documentation.
Finance and accounting
Accounts payable/receivable, month-end close, reconciliations, GAAP, financial reporting, variance analysis, payroll processing, QuickBooks, NetSuite, SAP, audit preparation, cash-flow forecasting, tax compliance.
Healthcare and care work
Patient assessment, medication administration, electronic health records (Epic, Cerner), care planning, triage, HIPAA compliance, phlebotomy, wound care, patient education, charting, infection control.
Education and training
Curriculum design, lesson planning, differentiated instruction, classroom management, learning management systems (Canvas, Moodle), assessment design, IEP implementation, adult training facilitation, e-learning development.
Administrative and office
Calendar management, travel coordination, expense reporting, meeting minutes, document management, data entry, front-desk operations, Microsoft 365, Google Workspace, event planning, records compliance.
Trades, logistics, and field work
Equipment operation, preventive maintenance, blueprint reading, OSHA compliance, quality inspection, welding, HVAC diagnostics, fleet coordination, forklift certification, route optimization, safety auditing.
Interpersonal and management (use sparingly — see below)
Team leadership, cross-functional collaboration, stakeholder communication, conflict resolution, coaching, public speaking, negotiation, prioritization, written communication.
That last category deserves a warning label: listing "communication" as a skill persuades no one, because the words themselves are unverifiable in a list. The difference between listing and proving these is the whole subject of our hard skills versus soft skills guide — the short version is that interpersonal skills belong in your bullets as demonstrated behavior, with at most one or two appearing in the skills section when the posting explicitly names them.
Choosing your 8-12: the relevance-evidence filter
Every skill on your final list must pass two gates.
Gate one: relevance. The job description mentions it, implies it, or a hiring manager in this field would expect it. If the posting never hints at it and the field does not assume it, it is trivia. Cut it — even if you are proud of it.
Gate two: evidence. Somewhere else on your resume (or in your portfolio), a bullet shows this skill in use. A skill that appears only in the skills list, with no supporting bullet, reads as aspiration. If you claim SQL, a bullet should mention a query, a dataset, or a report you built with it.
Run your raw list through both gates and you will usually land between eight and twelve survivors, which happens to be the range that reads as credible. Fewer than six can look thin for experienced candidates; more than fifteen reliably looks padded.
When two skills tie, prefer the one that is scarcer among your competition. Every project manager claims scheduling; fewer can claim earned-value analysis or contract negotiation.
Where skills belong: dedicated section vs woven into bullets
You need both, and they do different jobs.
The dedicated section is for scannability and search: a compact block, usually just below the summary for technical roles or below experience for others, holding your gated list. Where the section sits in the overall document depends on your career stage — our overview of what to put on a resume, section by section covers ordering in detail.
The bullets are for proof. A recruiter who spots "Tableau" in your skills list will look for the achievement bullet that shows what you built with it. When the two layers reinforce each other — list for the scan, bullet for the evidence — the skill becomes a claim the reader can trust.
What does not work is the third option people default to: skills mentioned nowhere except a summary paragraph ("skilled in analysis, communication, and leadership"). That construction is invisible to database search and unpersuasive to humans, a double miss.
Skills to leave off: Microsoft Word and other table stakes
Some skills cost you space and signal without buying anything:
- Assumed basics. Word, email, internet research, typing (unless the job posts a words-per-minute requirement), "computer skills." Listing these suggests they are among your peaks.
- Obsolete tools — unless the employer still runs them. A posting that mentions Lotus Notes is your permission slip; otherwise, retire it.
- Character traits disguised as skills. Hardworking, detail-oriented, passionate. These are adjectives, not skills, and they belong in demonstrated form in your bullets or nowhere.
- Skills you cannot survive an interview question about. If a five-minute conversation would expose the claim, remove it now. The interview is the audit; list only what passes it.
- Hobbies mislabeled as skills — photography on an accountant's resume is a hobby line, not a skill line, unless the job touches it.
Deleting these does more than save space. It raises the average credibility of everything that remains.
Matching skills to the job description without stuffing
Tailoring the skills section takes about five minutes per application:
- Pull the posting's must-have skills — usually three to six, found in the requirements block and repeated in the responsibilities.
- Check each against your gated list. Genuine matches move to the front of your skills section, phrased the way the posting phrases them ("project management" if they say project management, not "project delivery").
- For matches you have under a different name, adopt their term — honestly. If they say "customer relationship management" and you have five years of Salesforce, write the phrase and the tool.
- Resist adding must-haves you do not have. A skills list is not a wish list, and a false tick costs far more at interview than a missing one costs at screening.
That is the entire legitimate version of "optimizing for the ATS." White text, keyword blocks, and repeating a term twelve times are not optimization; they are visible to recruiters (who see the parsed text) and treated as the spam they are.
Skills section formats compared, with parsing notes
Three formats cover nearly every situation:
- Plain comma-separated list. One block: SQL, Python, Tableau, dbt, A/B testing, forecasting. Parses flawlessly everywhere, scans fast, and is the right default for most people.
- Categorized list. Two to four labeled lines (Analytics: ..., Tools: ..., Languages: ...). Best when you have 10-12 skills spanning distinct domains, common for technical candidates with deep tool lists. Parses cleanly as long as it stays plain text.
- Skill bars, star ratings, and graphics. Avoid. Parsers extract nothing from a filled-in bar, and human readers cannot tell whether four dots out of five means expert or optimist. If you need to signal depth, use words — "advanced," "working knowledge" — or better, let a bullet demonstrate it.
One layout note: keep the skills section out of tables and text boxes. Some parsers read table cells out of order or skip them, and a skills section that fails to parse is a skills section that never happened as far as database search is concerned.
Frequently asked questions
How many skills should I put on a resume?
Eight to twelve for most candidates. Deeply technical roles can justify up to fifteen when split into labeled categories. Below six looks thin for anyone past entry level; above fifteen dilutes trust in every individual item.
Should skills go at the top or bottom of a resume?
For technical roles where tools are a screening criterion, place the section high — just under the summary. For most other roles, after experience is fine, because your bullets are the stronger evidence. Students and career changers often benefit from placing skills higher to compensate for a thinner experience section.
Do I need to list soft skills at all?
Only when the posting explicitly names one or two as requirements. Otherwise, demonstrate them in bullets — "trained 9 new hires" proves coaching better than the word "coaching" ever will.
Should I list skill levels like beginner or expert?
Only when you can defend the label and the distinction matters for the job. "Spanish (professional working proficiency)" is useful; "Excel (expert)" invites a test. When unsure, omit the level and let your bullets set expectations.
Check your list against the posting
Workplacea's editor compares your skills section against any job description and shows the overlap — and the honest gaps — without inventing qualifications for you. Try it in the editor, or run your current resume through the free resume checker first to see how your skills section parses today.