Hard Skills vs Soft Skills on a CV: How to Show Both Without Sounding Generic

Most CVs lose the skills battle in two ways. They dump 30 tools into a bullet list with no context, or they brag about being a team player and a fast learner without a single proof point. Neither convinces a recruiter, and neither helps the ATS rank your application.

This guide explains the difference between hard skills and soft skills on a CV, where each belongs, and how to show both without sounding like every other applicant.

The actual difference

A hard skill is something you can prove on demand. SQL, Python, financial modelling, Adobe Premiere, German at B2 level, AWS, double-entry bookkeeping. If a recruiter handed you a laptop and a task, you could either do it or you could not.

A soft skill is a behaviour. Communication, leadership, ownership, adaptability, empathy. There is no certificate, no version number, and no clean test. Soft skills only become real when you describe them in action.

Both matter. Hard skills get you past the ATS keyword filter. Soft skills decide whether the recruiter picks up the phone.

Where each one goes on the CV

Hard skills: in a dedicated section

Create a Skills section near the top, above your experience if you are early career, below it if you have five or more years. Group hard skills by category so the eye can scan them:

• Languages: Python, TypeScript, Go
• Data: PostgreSQL, BigQuery, dbt, Looker
• Cloud: AWS (Lambda, S3, RDS), Docker, Terraform
• Languages spoken: English (C2), French (B2)

Do not stack 40 tools. Pick 12 to 18 that match the job description. The rest dilute the signal and look like a CV-padding exercise.

Soft skills: woven into your bullets

Never list soft skills in isolation. A line that says Skills: leadership, communication, problem-solving is invisible. It is the CV equivalent of saying you breathe oxygen.

Show soft skills through outcomes in your experience section:

• Weak: Strong communicator
• Strong: Led weekly cross-team syncs with engineering and sales to align on roadmap, reducing scope conflicts from 6 to 1 per quarter

The second line proves communication without using the word.

The hard skills mistakes that kill CVs

1. The buzzword graveyard. Listing every tool you have ever touched signals desperation. The recruiter assumes you are intermediate at most of them.
2. No proficiency signal. Saying Python next to Excel makes them look equal. If you are advanced at one and beginner at the other, group them or use a level indicator.
3. Skipping the keywords from the job description. The ATS only sees what you write. If the role asks for Kubernetes and you wrote K8s, you may not match.
4. Stale tech. Listing Flash or jQuery as a current skill on a 2026 CV tells the recruiter you have not updated this document in a decade.

The soft skills mistakes that kill CVs

1. Adjective soup. Hard-working, motivated, passionate, dynamic, results-driven. Recruiters skip every word.
2. Claims without evidence. Strong leadership skills proves nothing. Mentored 4 junior engineers, two of whom were promoted within 12 months does.
3. Generic verbs. Replace was responsible for with led, built, shipped, negotiated, migrated. Verbs carry the soft skill.

How to map skills to the job

Before you submit anything, run this 10-minute exercise:

1. Copy the job description into a blank doc.
2. Highlight every hard skill mentioned (tools, languages, certifications).
3. Highlight every soft skill implied (stakeholder management, fast-paced, ambiguity).
4. Cross-check your CV: are the matching hard skills in your Skills section, in the exact wording the job uses?
5. For each soft skill the role wants, find one experience bullet that proves it. If you cannot find one, rewrite a bullet so it does.

This is the single highest-leverage thing you can do before clicking apply.

Examples by role

Software engineer

• Hard: Python, Go, Postgres, Kafka, AWS, system design
• Soft proven through bullets: ownership (owned the migration of the legacy billing service), mentoring, code review discipline

Marketing manager

• Hard: HubSpot, Google Analytics 4, SQL basics, paid social, SEO
• Soft proven through bullets: cross-functional leadership, prioritisation (shut down 3 underperforming channels, redirecting budget to the 2 that converted), narrative writing

Customer success

• Hard: Zendesk, Gainsight, Notion, SQL for retention queries
• Soft proven through bullets: empathy, account expansion (grew ARR per account from $24k to $41k average across 18-account book), de-escalation

Soft skills your CV should never claim outright

These all need proof, not labels: team player, quick learner, detail-oriented, excellent communicator, self-starter. Every recruiter has been burned by candidates who wrote these and could not back them up. Listing them now signals that you have not thought about how to show them.

The skills section format that works in 2026

```

Skills

Languages: Python (advanced), Go (intermediate), TypeScript (intermediate)

Data: PostgreSQL, BigQuery, dbt, Airflow

Infrastructure: AWS (5+ yrs), Docker, Terraform, GitHub Actions

Methods: System design, code review, on-call ownership

Languages spoken: English (C2), French (B2), Spanish (A2)

```

Five lines, scannable in 4 seconds, ATS-friendly, no graphics, no progress bars, no five-star ratings. Recruiters mistrust visual proficiency scales because anyone can fill them in.

Final pass before you send

• Every hard skill on the CV maps to either the job description or a project bullet that uses it.
• Every soft skill claim is supported by a measurable outcome.
• The skills section fits on one screen without scrolling.
• You have removed any tool you would be embarrassed to be quizzed on in the interview.

Do this once per application. It is the difference between a CV that gets filtered out and one that gets a callback.