Hard vs. Soft Skills on a CV: What Recruiters Want (2026)

Your skills section is more than just a list. It’s a quick snapshot of your capabilities and one of the best places to improve ATS keyword match without rewriting your entire CV.

The problem: many candidates either (1) list too many random skills or (2) fill the section with vague soft skills that don’t prove anything.

This guide shows how recruiters and ATS systems actually evaluate skills, what to prioritize right now, and how to format your skills section so it’s both skimmable and machine-readable.

Want to verify your keyword match and formatting in seconds? → Run a free ATS scan

New here? Start with: Mastering ATS Optimization

Hard skills vs. soft skills: what’s the difference?

Understanding the distinction is the first step.

Hard skills (what you can do)

Hard skills are specific, teachable, and measurable abilities. They’re often technical and relate directly to the job.

Examples

• Python, SQL, React, AWS
• SEO, PPC, GA4, HubSpot
• Financial modeling, IFRS, Tableau
• Salesforce, MEDDIC, pipeline forecasting
• Spanish (professional fluency)

Soft skills (how you do it)

Soft skills describe how you work and interact with others. They matter, but they only carry weight when you prove them with context.

Examples

• communication
• teamwork
• problem-solving
• leadership
• adaptability
• time management
• stakeholder management
• prioritization

A strong CV needs both. Hard skills help you pass the initial screens. Soft skills help a recruiter believe you’ll perform in the role.

What recruiters want to see now

Recruiters use your skills section in two ways:

1. Filtering and search They search for exact terms like “Salesforce”, “SQL”, “Kubernetes”, “GA4”, “Paid Search”, “SOC 2”, “React”.

2. Confirmation They check if your experience bullets show real usage, scope, and outcomes.

So a great skills section:

• mirrors the job description language (without stuffing)
• highlights the skills that are central to the role
• stays short enough to scan fast
• uses a format ATS can parse cleanly

Need help finding the terms employers actually use in your field? → Resume keywords by industry

What skills are in-demand right now (without guessing)

Instead of chasing generic “top skills” lists, use a practical rule:

• Hard skills = what the job posting repeats
• Soft skills = what the role requires you to do daily

That said, these categories show up frequently across many roles:

High-signal hard skill categories

• Data and reporting: SQL, Excel, Tableau/Power BI, KPI dashboards
• Automation and AI usage (role-dependent): workflow automation, prompt-based tooling, experimentation
• Cloud and infrastructure (technical roles): AWS/Azure/GCP, Docker, Kubernetes, CI/CD
• Security and compliance (security/IT roles): IAM, SIEM, SOC 2, NIST/ISO
• Growth and performance (marketing/sales): CRO, lifecycle email, paid search, CRM hygiene, pipeline analytics

High-signal soft skill categories (when proven)

• prioritization and tradeoffs
• stakeholder management
• cross-functional collaboration
• ownership and execution
• structured problem-solving

How to format your skills section for maximum impact

There’s no single “right” way, but some formats are both clearer and more ATS-friendly than others.

Avoid

• tables, text boxes, multi-column skill blocks
• icons, graphics, skill bars, star ratings
• long, ungrouped keyword dumps

Example 1: Categorized list (recommended for most roles)

SKILLS
Technical: Python, SQL, React, Node.js, AWS, Docker
Analytics: Tableau, Power BI, KPI Dashboards, A/B Testing
Tools: Git, Jira, Notion
Languages: English (Native), Spanish (Professional)

Example 2: Pipe-separated inline list (compact, ATS-safe)

SKILLS
SEO/SEM · Google Analytics · HubSpot · Paid Social (Meta, LinkedIn) · A/B Testing · Marketing Automation · Content Strategy · Campaign ROI Analysis

Both formats parse cleanly. The categorized list is easier to skim for human readers; the inline list saves space and still passes ATS without issue.

Why Generic Skills Hurt Your ATS Score

Listing "Microsoft Office", "communication", or "team player" doesn't just waste space — it actively drags down your ATS match score.

Here's why: ATS systems are trained on job description language. They look for role-specific technical terms — the names of tools, platforms, methodologies, and domain-specific processes. When your skills section is full of soft-skill adjectives and generic software names, the system finds nothing to match against the job posting. Your match percentage drops, and so does your position in the shortlist.

"Communication" appears in almost every job description as a desired quality — but not as a keyword the ATS will surface you for. "HubSpot," "Salesforce," "Python," "SQL," or "Agile sprint planning" are the terms that drive keyword match. They're specific, searchable, and directly tied to what the role requires.

The rule: if a skill could appear on the CV of anyone in any industry, it's not a strong keyword. Replace it with the specific tool, platform, or method you actually used.

Side-by-side comparison

Weak (Marketing Manager): Skills: Communication, Microsoft Office, Social Media, Teamwork, Creative Thinking, Leadership

Strong (Marketing Manager): Skills: SEO/SEM · Google Analytics · HubSpot · Paid Social (Meta, LinkedIn) · A/B Testing · Marketing Automation · Content Strategy · Campaign ROI Analysis

The weak version contains zero searchable keywords. The strong version gives an ATS system eight specific terms to match against a marketing job description — and gives a recruiter immediate proof of relevant capability.

How Many Skills Should You List?

The sweet spot is 10–15 skills, grouped into 2–3 categories such as Technical Skills, Tools & Platforms, and Domain Expertise.

Why not more? More than 20 skills dilutes your profile. It signals breadth without depth, which reads as a generalist to both ATS systems and recruiters. If every skill looks equally important, none of them stand out.

Why not fewer? Fewer than 8 skills looks thin to ATS systems. There aren't enough terms to match consistently across job descriptions, and the section loses its scanning value.

The grouping principle: Group by type, not by proficiency. Proficiency ratings (stars, bars, "advanced/intermediate/beginner") don't parse cleanly in ATS and look subjective to recruiters. Just list the skills, ordered by relevance to the role you're targeting.

A practical structure for most roles:

Technical Skills: [tools, languages, platforms]
Domain Expertise: [methodologies, processes, frameworks]
Soft Skills: [2–3 only, proven in your experience bullets]

Lead with the category that matters most for the specific job. For a data engineering role, Technical Skills comes first. For a project management role, Domain Expertise (Agile, PRINCE2, stakeholder management) may be more relevant upfront.

Closing: Match Your Skills to the Role, Not to a Generic List

The biggest mistake candidates make with their skills section isn't listing bad skills — it's listing the right skills for the wrong job. A Python developer applying to a data science role and a Python developer applying to a backend engineering role need different skills sections, even though the tool is the same. The surrounding terms, the domain context, and the grouped categories all need to shift.

Not sure which skills to include for your specific role? Use the Keywords Finder at /keywords-finder to generate a role-specific keyword list — then pick the ones that genuinely match your experience.

Before you apply, validate that your skills section is being read correctly: → Run a free ATS scan