What Skills to Put on Your Resume in 2026 (the 10-15 Rule)

We already wrote the delete list — the 8 skills NOT to put on your resume, starting with Microsoft Office. It turned out to be one of the most-read things on this site, which tells us something: a lot of people know their skills section is wrong but aren't sure what right looks like.

This is the other half. Once you've cleared out the filler, what actually goes in that section? How many skills? Which kinds? In what order? The answer is more specific than most career advice admits, so let's be specific.

The one principle everything else follows from

Your skills section is the intersection of two lists:

1. What the job posting asks for — the tools, methods, and competencies the employer names
2. What you can defend in an interview — skills where, if the interviewer says "tell me about a time you used this," you have a real answer

That intersection is your skills section. Not everything you've ever touched. Not everything the posting mentions. The overlap.

A skill that's on the posting but not defensible gets you into interviews you then bomb. A skill that's defensible but irrelevant to the role is noise that dilutes the signal. The skills section isn't an autobiography — it's a targeting system.

The 10-15 rule

The right length for a skills section is 10 to 15 entries. Here's the reasoning on both ends:

Why not 5? Modern ATS platforms score keyword coverage, and human recruiters use the skills section as a fast index of your capabilities. Five entries under-indexes you — there are almost certainly more than five defensible, relevant skills in your background, and every one you leave off is a keyword match you're forfeiting.

Why not 40? Because a 40-item skills list reads as guessing. When a recruiter sees "leadership, communication, Excel, Python, empathy, Photoshop, negotiation, HTML, time management..." they conclude that you listed everything you could think of, which means none of it is a signal. Long lists also bury your strongest skills in the middle of your weakest — the recruiter skimming for "SQL" has to wade past "adaptable."

Ten to fifteen forces choices, and the choices are the point. A curated list says: I know what this role needs, and I know what I bring.

Hard skills go in the list. Soft skills go in the bullets.

This is the rule that instantly fixes most skills sections: the skills list is for hard skills only.

Hard skills are specific, learnable, verifiable capabilities: SQL, Google Ads, financial modeling, Figma, Spanish, phlebotomy, Salesforce administration. A recruiter can test them, an ATS can match them, an interviewer can probe them.

Soft skills — leadership, communication, problem-solving, adaptability — are real and they matter, but as list items they're unverifiable self-praise. "Communication" in a skills list carries zero information; every candidate claims it. The place soft skills belong is your experience bullets, where they show up as evidence instead of assertion:

• Instead of listing "leadership" → "Led a 5-person support team through a platform migration with zero attrition"
• Instead of listing "communication" → "Presented quarterly performance reviews to the executive team; briefs adopted as the company template"

Same trait, but one version is a claim and the other is a receipt. (If your bullets aren't doing this yet, here's the formula for fixing weak bullets, and the Bullet Surgeon will rewrite any single bullet three ways for free.) This hard-in-the-list, soft-in-the-bullets split is the whole game — here's the full breakdown of hard vs. soft skills and where each one goes.

The five categories that belong in a skills section

Build your 10-15 from these, roughly in this priority order:

1. Tools and platforms. The software the role lives in: HubSpot, Salesforce, Figma, Jira, AutoCAD, Epic, QuickBooks, Google Analytics 4. These are the highest-value ATS matches because job postings name them explicitly.

2. Technical hard skills. Capabilities that aren't a single tool: SQL, financial modeling, A/B testing, technical writing, wound care, contract negotiation, paid social strategy. Be exactly as specific as you can defend — "SEO (technical + on-page)" beats "SEO" if you can back it up.

3. Methodologies and frameworks. Agile/Scrum, Lean Six Sigma, OKR planning, double-entry accounting, HIPAA compliance workflows. These signal you've worked inside systems, not just tasks.

4. Certifications and licenses. PMP, CPA, RN licensure, AWS Solutions Architect, Google Ads certification. If the role requires one, it should also appear in a dedicated certifications line or section — but echoing it in skills helps keyword matching.

5. Human languages. With honest proficiency levels: "Spanish (professional working proficiency)." Never inflate this one; it's the easiest skill on the page to test in an interview.

Quick lists by field

Starting points — not to copy wholesale, but to calibrate the specificity level recruiters expect in 2026:

Software / tech: the languages and frameworks you actually ship in (Python, TypeScript, React), cloud platforms (AWS, GCP), infrastructure tools (Docker, Kubernetes, Terraform), databases (PostgreSQL, Redis), observability (Datadog, Grafana), CI/CD, and your methodology (Agile, trunk-based development).

Marketing: channel skills (paid social, SEO, lifecycle email, ABM), platforms (Google Ads, Meta Ads Manager, HubSpot, Marketo, GA4), analytics (attribution modeling, A/B testing, SQL for reporting), and content ops (CMS platforms, editorial workflow).

Finance: modeling (DCF, LBO, three-statement), tools (advanced Excel with the specifics named, Bloomberg Terminal, Capital IQ), reporting standards (GAAP, IFRS), and systems (SAP, NetSuite, QuickBooks).

Healthcare: clinical competencies (medication administration, wound care, telemetry), systems (Epic, Cerner, Meditech), compliance (HIPAA, Joint Commission standards), and certifications inline (BLS, ACLS, PALS).

Operations / admin: systems (NetSuite, SAP, Zendesk), process skills (inventory management, vendor negotiation, SOP development), data (Excel/Sheets at a named level, Looker Studio), and project tools (Asana, Monday, Smartsheet).

Notice what's not on any of these lists: "communication," "detail-oriented," "team player," "Microsoft Office." That's the delete list doing its job.

Pick them from the job description, not from memory

The biggest practical mistake is writing the skills section once and never touching it. The right workflow is JD-driven:

1. Open the posting. Highlight every tool, method, and competency it names.
2. Keep the ones you can defend. Those go in — using the posting's exact phrasing.
3. Fill the remaining slots with your strongest adjacent skills.

Exact phrasing matters more than people think. If the posting says "demand generation" and your resume says "lead gen," older ATS platforms treat those as different strings. Match their vocabulary — here's the full ATS keyword method if you want the deep version.

And if you'd rather not do the highlighting by hand: paste your resume plus the posting into our free Job Match tool and it returns the missing keywords ranked by importance (critical / important / nice-to-have) in about 15 seconds. The critical list is, almost by definition, your skills-section punch list.

“The skills section isn't an autobiography — it's a targeting system. The intersection of what the job wants and what you can defend. Nothing else.”

Share on X→

Formatting: make it scannable, keep it parseable

• Where: below your experience section for mid-career and senior candidates (your work history is the headline); above it only if you're early-career or career-switching and your skills are stronger than your history.
• Categories help once you pass ~10 entries. "Tools: … / Methods: … / Certifications: …" reads faster than one long line and signals organized thinking.
• Plain text, standard header. Call it "Skills." No graphics, no proficiency bars, no star ratings — skill-o-meters are unverifiable decoration to humans and unparseable soup to ATS software.
• One skill, one phrasing. Don't list "SEO" and "search engine optimization" separately to game keywords; modern systems catch it and recruiters roll their eyes.

The maintenance rule

Your skills section should change more often than any other part of your resume — ideally a light pass for every application (swap 2-3 entries to match the posting), and a real audit every few months: new tools you've genuinely learned go in, tools you haven't touched in three years come out. A skills section is a snapshot of your current toolkit, not a museum of everything you've ever used.

The 60-second self-test

Read your skills section and ask three questions of every entry:

1. Would the target job posting mention this? If no posting in your search names it, cut it.
2. Could I survive five interview minutes on it? If not, cut it or downgrade the phrasing to something you can defend.
3. Would every other applicant list it too? If yes ("Microsoft Office," "communication"), it's not a differentiator — replace it with something that is.

Anything that survives all three belongs. If you're not sure how the whole section reads to a stranger, the free roast will tell you in 30 seconds — the skills section gets its own scoring category, and the Buzzword Density Score flags any personality-trait filler that snuck back in.

Build the delete list and the build list into the same habit: cut what everyone claims, keep what you can prove, match what the posting asks. That's the entire game.