How to list skills on a CV so they actually count

A recruiter reading a skills section is asking one question: can I believe this? A skill is a claim, and a claim only carries weight when something in the CV supports it. "Stakeholder management" in a list is an assertion. "Ran monthly steering meetings with finance, legal and three regional directors to agree release priorities" in a work history is evidence.

The second problem is specificity. "Computer skills" or "IT literate" tells the reader nothing. "Excel: pivot tables, Power Query, XLOOKUP, financial models" tells them exactly what level you are at. The more precisely a skill is named, the more useful it is to the reader and the more likely it is to match a search.

The third problem is volume. A list of thirty skills does not look impressive; it looks unfiltered. It suggests you could not decide what matters for this role, and it dilutes the skills that genuinely set you apart. A reader who sees twelve precise, relevant skills assumes expertise. A reader who sees thirty assumes padding.

Hard skills are specific, teachable and checkable: software, programming languages, analytical methods, regulations, equipment, spoken languages, certifications. These belong in the skills section, because they are exactly what recruiters search for and what hiring managers screen against.

Soft skills, like communication, leadership or adaptability, matter a great deal to employers, but listing them does almost nothing. They are shown, not stated. Move them into your experience bullets and your profile, where a result can prove them. Some lines should come off entirely:

Strong CVs repeat their most important skills in three places, each doing a different job. The profile names the two or three capabilities that define you for this role. The skills section lists the full, searchable set in a scannable block. The experience section proves the important ones in context, with results.

This is not repetition for its own sake. A recruiter scanning the top of the page sees the headline capabilities. A search in an applicant tracking system finds the terms in the skills block. A hiring manager reading properly finds the proof in the work history. If a skill appears in the list but nowhere else, ask whether it deserves to be there.

In practice, proving a skill in the experience section means naming it inside an outcome. "Built a Power BI dashboard that replaced four weekly spreadsheet reports for the operations team" proves Power BI, reporting automation and an understanding of what operations managers need, all in one line. That single bullet does more for the skill than any placement in a list.

Group skills into short labelled lines rather than one long column. Grouping makes the section readable in seconds and shows the shape of your expertise. Keep it to roughly six to fifteen items for most roles, more only in technical fields where tool lists are expected. Illustrative groupings look like this:

Skill bars, dots and star ratings are common in design templates and are best avoided. They are subjective, they cannot be verified, and they invite the wrong question: if Excel is four out of five, what is missing? Many applicant tracking systems cannot read graphics at all, so the skill may vanish from the parsed record entirely.

When proficiency genuinely matters, say it in words. Languages are the clearest case: native, fluent, professional working proficiency, conversational. Where a framework exists, such as the CEFR levels for European languages, use it. For technical tools, specifying what you actually do with them, as in the Excel example above, communicates level better than any rating.

Be careful with words like "expert" and "advanced". They are ratings in disguise and invite the same test. An interviewer who reads "expert in SQL" may well ask you to write a window function on the spot. If the claim is true, name the evidence instead: the size of the databases you work with, the kind of queries you write, the reports or pipelines you built. Evidence cannot be marked down; adjectives can.

Your master CV can hold every skill you have. Each application should show the ones this job asks for, in the order it seems to care about them. Read the posting and mark every skill, tool and qualification it names, then compare them against your list. Where you have the skill, use the posting's exact wording: if it says "stakeholder engagement", write that rather than your own synonym such as "relationship building".

Put the skills the posting emphasises first in each group, and cut ones that are irrelevant to this role even if they are impressive. A data scientist applying for a machine learning role does not need to list event planning. Where the posting names a skill you genuinely have but have never written down, add it and add a bullet that shows it. Where it names a skill you do not have, leave it out. Interviews test skills lists, and a claimed skill you cannot discuss costs more than a missing one.

Graduates and career changers lean on the skills section more heavily, because their work history does not yet speak for the target role. That is a reason to make the section stronger, not longer. Move it higher on the page, directly under the profile, and make every item something the target job actually asks for.

Then find the evidence in places other than paid work. A dissertation that involved statistical analysis in R proves R. A volunteer treasurer role proves bookkeeping and budgeting. A retail job proves stock control, cash handling and dealing with difficult customers, which matter in operations, hospitality and customer success roles. Label these sources plainly, in a projects or relevant experience section, so the reader can see where each skill was used.

Career changers should also translate their language. A teacher moving into learning and development does not "plan lessons"; they design training content, assess learning outcomes and present to groups. The skill is the same. The vocabulary has to match the field you are entering, or the reader and the search both miss it.