Begin with the target role
Read the role description and identify the capabilities that matter to the work. Separate true requirements from language that is merely familiar. Only include a skill when you can explain where, how and at what level you used it.
Group skills so they can be read quickly
Use small, meaningful groups such as analysis tools, programme delivery, client communication or technical platforms. Grouping reduces repetition and helps the reader understand the shape of your capability rather than scanning a long unstructured list.
Use the experience section as proof
A skills section can help discovery, but it does not create credibility by itself. Show the most important skills in action through a project, responsibility, decision or outcome in the relevant work history.
Do not rate yourself with vague bars
Visual scales suggest precision without explaining context. A tool can be used confidently in one setting and lightly in another. If level matters, describe the work you carried out rather than assigning yourself a graphic score.
Remove skills that distract
Old software, generic office tools, personality words and unrelated capabilities can bury the strengths that matter. Keep the list edited as your target changes.
A useful check
For each skill, ask whether it supports the role, whether it is current and whether you could give a concrete example in an interview. If not, it probably does not deserve space.
Select skills from the target role
Read the role description and separate actual requirements from familiar phrases. Look for technical capabilities, methods, domain knowledge, customer context, leadership expectations, and tools that you have genuinely used. Keep only skills you can explain through a role, project, decision, or outcome.
Group capabilities in meaningful categories
Rather than using one long alphabetical list, create small groups such as analytics, programme delivery, engineering tools, stakeholder management, commercial operations, or design practice. Grouping helps a reader understand the shape of your capability and stops a few important skills disappearing in a dense block of text.
Use experience bullets as evidence
If a skill matters to the role, show it in action in your experience section. For example, stakeholder management becomes more credible when it appears alongside a complex project, senior audience, or cross-functional decision. A skills list can aid discovery, but it cannot substitute for context.
Remove skills that reduce clarity
Generic office tools, outdated systems, repeated soft skills, and unrelated capabilities can bury the expertise that matters. Review the list every time you change target roles. The aim is not to show everything you have ever used. It is to make relevant capability clear and defensible.
Avoid self-ratings without context
Graphic bars and labels such as expert or advanced can suggest precision without explaining what you can actually do. If level matters, show the complexity of the work, the environment, or the responsibility you handled. Clear evidence is more useful than a decorative rating system.
Tailor the order as well as the list
Place the skills most relevant to the target role first, then use the experience section to support them. A recruiter should not need to search a long list for the few capabilities that make your application viable. Ordering is a small editorial decision that can make a relevant resume feel more intentional immediately.
Keep the section current
Remove old tools and add genuinely relevant capability as your work changes. A concise, current list is easier to defend and more useful than a record of every system you have encountered.
Frequently asked questions
Questions people ask before they write.
How many skills should I list on a resume?
List enough to show relevant range, but not so many that the important capabilities disappear. Grouped lists are usually clearer than a long inventory.
Should I include soft skills?
Include them when they are demonstrated through real work. For example, stakeholder management is more meaningful when tied to a complex project or customer relationship.
How many skills should be on a resume?
List enough to show relevant range, but not so many that the important capabilities become difficult to find. A focused, grouped list is usually stronger.
Should I include soft skills?
Include them when they are demonstrated through real work. Phrases such as communication or leadership are more credible when tied to a project, decision, team, or customer context.