CV Skills Section: What to Put and How to Write It

The skills section is one of the most scanned parts of a CV, by both recruiters and the ATS systems they use. Yet most job seekers treat it as a static list they wrote once and never revisit. That's a mistake that quietly costs interviews.

This guide covers what belongs in your skills section, what doesn't, how to structure it, and, most importantly, how to tailor it for every application.

What Actually Belongs in a Skills Section

The skills section should contain specific, verifiable capabilities, things you could be tested on or asked to demonstrate. It is not the place for personality traits or vague soft skills.

In: hard skills and tools

These are concrete, nameable capabilities:

• Software and platforms: Salesforce, HubSpot, Tableau, Adobe Premiere, Figma, Jira
• Programming languages and frameworks: Python, SQL, React, Node.js, Terraform
• Methodologies: Agile, Scrum, PRINCE2, Six Sigma, ITIL
• Certifications and qualifications: PMP, CFA, Google Analytics, AWS Solutions Architect
• Languages: French (C1), Spanish (conversational)
• Domain expertise: Financial modelling, SEO strategy, supply chain optimisation

Out: hollow soft skills

These are not skills, they're personality descriptors that every candidate claims and no recruiter believes:

• "Strong communication skills"
• "Team player"
• "Problem solver"
• "Hard working"
• "Attention to detail"

These phrases add noise and dilute the signal of your real skills. If you have strong communication skills, the quality of your CV writing demonstrates it. If you're a problem solver, your achievement bullets show it. Don't state it, prove it elsewhere.

That said, some soft skills belong in the section when they're specific and tied to the role: "stakeholder management", "cross-functional team leadership", or "executive-level presentations" are specific enough to be meaningful.

How to Structure It

There's no single right structure, but some approaches work better than others depending on your background.

Option 1: Flat list (most common)

A comma-separated or bullet-point list of your skills, ordered by relevance to the role you're applying for. Simple, ATS-friendly, easy to scan.

Option 2: Grouped by category

Organise skills into 2–3 labelled groups. Useful if you have a mix of technical, domain, and language skills that benefit from separation. Can look cluttered if overdone.

What to avoid

Where to Put It in Your CV

The right position depends on your career stage and the role:

• Technical roles (engineering, data, IT): Skills section near the top, just below your summary. Recruiters are scanning for specific technical stacks before anything else.
• Most other roles: After your work experience. Your experience should do the heavy lifting; the skills section backs it up.
• Graduates and career changers: Near the top, since experience may be limited and skills are a stronger immediate signal.

How Many Skills to Include

Eight to fifteen is a reasonable range for most professionals. Fewer than eight and you're underselling yourself. More than twenty and the section becomes a wall of text that loses impact, everything looks equally important, which means nothing stands out.

The right number also depends on seniority. A senior professional with 15 years of experience might legitimately list 15–20 skills across a broad range of tools and disciplines. A recent graduate might have 8–10 genuinely credible skills. Quality beats quantity in both cases.

The Crucial Step Most People Skip: Tailoring per Application

Most people write their skills section once and submit it to every job unchanged. This is one of the single easiest things to fix, and one of the highest-impact changes you can make.

Here's the process for every application:

1. Read the job posting carefully and extract every specific skill, tool, and competency they mention
2. Compare to your skills section, do you have those skills? If yes and they're not listed, add them now
3. Use their exact wording, if they say "stakeholder management", don't write "relationship management". ATS matching is often exact
4. Move the most relevant skills to the top of your list, recruiter eyes and ATS weighting both favour what comes first
5. Remove irrelevant skills, a skill that's unrelated to this role adds noise without adding signal

The skills section takes 5 minutes to tailor and consistently moves CVs up the ATS rankings. Most candidates don't bother, which is exactly why it works.

A Note on Honesty

Only list skills you can genuinely defend in an interview or technical assessment. If SQL is on your CV, you should be able to write a working query. If you list Salesforce, you should know how to navigate it without a tutorial.

Listing skills you can't back up is a short-term pass rate improvement that creates a long-term problem. Interviewers will probe what's on your CV, that's the point. A skill you can demonstrate confidently is worth ten you've listed speculatively.