A skills section should help the reader locate relevant capabilities and connect them with evidence elsewhere in the CV. Use terms you can explain through work, projects or learning. Distinguish practical experience from current study, and avoid decorative percentages that imply a measurement you have not made.
Select skills from the work, not from a keyword list
Read the vacancy for the tasks behind its terminology. A request for reporting skills may involve preparing reliable source data, choosing an appropriate comparison and explaining limitations—not simply knowing the name of a visualization tool. Include the relevant skill when your experience supports it, and use the employer’s wording only where it is accurate.
Keep a separate list of learning goals. It can help plan development, but should not silently merge into a public list of established capabilities. A tool you have opened once, a guided course exercise and repeated professional use are different kinds of experience. Clear context is more informative than trying to assign a universal beginner-to-expert label.
Group skills in a way that helps the reader
Organize related skills around useful work contexts, such as analysis, delivery methods and communication. Avoid a long alphabetical list that makes the recruiter search for connections. Grouping also helps you notice where several tool names represent the same narrow experience rather than a broad set of independent capabilities.
For prominent skills, identify a supporting experience or project. The evidence need not appear in the same line, but it should be easy to find. ‘Facilitation’ can connect with a handover workshop you organized; ‘data cleaning’ can connect with a documented project. The skill label tells the reader where to look, while the example explains what you actually did.
Replace ungrounded ratings with useful context
Percentage bars rarely tell a reviewer what was measured, against which standard or in which environment. ‘Python 95%’ could mean many things and is difficult to defend. A short context statement such as ‘Python for cleaning service datasets’ gives the reader a more concrete starting point for discussion.
Recency and independence can matter. If a skill was last used several years ago, do not imply current fluency without checking it. If a project was heavily guided, describe that context. You can present developing skills positively while remaining explicit about what you can currently do without assistance.
Keep the working examples nearby during interview preparation. A reader may ask why you chose a method, what went wrong or when another approach would have been more appropriate; those questions reveal more than a rating bar.
Turning a rated list into an evidence map
A fictional CV lists ‘leadership 100%, Python 95%, communication expert’. The ratings have no defined assessment method. Elsewhere, the CV describes maintaining a service dataset, facilitating a handover review and writing instructions for new colleagues.
The revised skills section groups ‘Data preparation: Python and spreadsheet cleaning’, ‘Team coordination: handover reviews’ and ‘Documentation: service instructions’. The experience section explains the relevant work and its limits. This does not prove mastery of every task in those fields; it makes the candidate’s actual evidence easier to identify and discuss.
A checklist for your next step
- Select relevant and supportable skills.
- Separate learning goals from experience.
- Group capabilities by work context.
- Identify an example behind each key skill.
- Replace ungrounded percentage ratings.
Common questions
Can I list a skill learned through a personal project?
Yes, when the context is clear. Explain what you produced, whether the work was guided and what you can demonstrate independently. Do not label the project as professional client experience if it was not.
Must every skill have a separate certificate?
No. Different skills require different evidence, and some roles have specific qualification requirements. A certificate, practical example and independent verification are distinct things; do not treat one as a universal substitute for the others.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveCV.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.