How to List Skills on a Resume the Right Way (2026 Guide)

The skills section is one of the most commonly mishandled parts of a resume — either stuffed with vague buzzwords ("team player," "self-starter") or left so generic it says nothing at all. Since ATS systems use this exact section to decide whether you match a role, getting it right matters more than its small size suggests.

How Many Skills Should You Actually List?

6-10 skills in a dedicated section, with the median for successful resumes sitting around 8-9. An analysis of over 93,000 resumes found this range provides enough variety to demonstrate real capability without overwhelming a recruiter or reading as padding.

Going much beyond 10-12 tends to look like you're padding the list to increase keyword matches rather than genuinely representing your strongest, most relevant skills — and a recruiter can usually tell the difference.

What's the Right Balance Between Hard and Soft Skills?

Roughly 70% hard skills, 30% soft skills is the ratio most consistently recommended for 2026. The reasoning is mechanical: hard skills are what get your resume opened — they're what ATS keyword matching weighs most heavily. Soft skills are what help decide whether you get moved forward once a human is actually reading — but they're harder to verify from a list alone, so they carry less weight in the automated screening stage.

Hard skills are technical, measurable, and typically provable through training or output — programming languages, specific software, financial modeling, project management tools, or a language certification.

Soft skills are interpersonal and behavioral — communication, leadership, adaptability, problem-solving. These matter, but they need a different treatment than hard skills (see below).

Should You List Soft Skills the Same Way You List Hard Skills?

No — and this is one of the most common mistakes. A bare soft skill sitting alone in a list ("Communication," "Leadership," "Team Player") is functionally meaningless to a reader, since anyone can claim it whether or not it's true.

The fix: let soft skills show up inside your experience bullets, backed by a real, specific result — not as standalone entries in your skills section.

Weak:

Skills: Leadership, Communication, Problem-Solving

Strong (same skills, demonstrated instead of claimed):

"Led a cross-functional team of 15 engineers, delivering a product launch 3 weeks ahead of schedule." (demonstrates leadership) "Diagnosed and resolved a critical database issue causing revenue loss, within a 6-hour SLA window." (demonstrates problem-solving)

This does double duty — it satisfies the "show, don't just tell" principle that makes a resume credible, and it naturally works the same soft-skill keyword into a results-driven sentence, which ATS systems can still register in context.

How Should You Match Skills to a Specific Job Posting?

Pull the actual job description and highlight every skill-related term in it — both explicitly listed requirements and skills implied by the responsibilities described. Then compare that list against your own genuine skills, and prioritize the overlap.

Use the exact terminology the posting uses, not a close synonym. If a posting asks for "SQL experience" and your resume says "database querying" instead, some ATS systems won't register that as a match at all — this is a literal keyword-matching process, not a conceptual one. Where an acronym is involved, include both forms the first time it appears: "Search Engine Optimization (SEO)."

Where Should the Skills Section Go, and How Should It Be Formatted?

Place it as a clearly labeled, dedicated section — labeled simply "Skills," not something like "Core Competencies," since ATS parsers are generally tuned to recognize the plainer, more standard label. For a standard chronological resume, this typically sits after your work experience, though a summary-adjacent placement works too if your skills are especially central to the role.

Formatting that works:

• Clean, scannable layout — 2-3 columns, or bullet points separated by simple dividers
• No dense paragraph blocks, and no tables (formatting mistakes here can break ATS parsing entirely)
• Hard skills listed first, soft-skill-adjacent named methodologies (Agile, Scrum, OKRs) can follow, since these score well precisely because they map to measurable frameworks rather than vague traits

Are There Skills You Should Actually Leave Off?

Yes — skip anything so baseline it's simply assumed in 2026. "Microsoft Word," "Email," or "Basic computer skills" no longer signal anything useful to a recruiter and just take up space that a more specific, differentiating skill could use instead.

Similarly, avoid ungrounded buzzwords with no evidence attached — "go-getter," "self-starter," "hardworking" — these are widely viewed as noise rather than signal, both by ATS systems and human readers who see the same phrases on every third resume.

Key Takeaways

• List 6-10 skills in a dedicated section, roughly 70% hard skills and 30% soft skills
• Use the job posting's exact terminology — ATS systems often miss synonyms entirely
• Never list a bare soft skill alone — demonstrate it through a quantified bullet instead
• Label the section simply "Skills," and keep formatting clean and scannable — no tables, no dense paragraphs
• Skip assumed-baseline skills (Microsoft Word) and unproven buzzwords (self-starter) — they waste space without adding signal

Frequently Asked Questions

Should I have a different skills section for every job I apply to?

Not a full rebuild each time, but you should adjust which 6-10 skills you lead with based on what each specific posting emphasizes — the same underlying skill set can be reordered and re-worded to match different roles.

Is it okay to include a skill I'm still learning?

Only if you're honest about proficiency level where relevant (e.g., "Beginner Python" rather than implying expert-level fluency) — misrepresenting your actual skill level creates risk if it comes up in an interview or on the job.

Do certifications count as skills, or do they belong in a separate section?

Both are reasonable — a brief certification can be named within a skills entry (e.g., "Project Management (PMP)"), or listed in its own dedicated certifications section if you have several worth highlighting.

How many soft skills should actually appear as standalone list entries versus demonstrated in bullets?

Lean toward demonstrating soft skills in your experience bullets rather than listing them standalone at all — if a soft skill doesn't have a real example behind it, it's generally better left out of the resume entirely.