Reviewers and systems both respond to relevant, credible skills. The aim is to map your real skills to what the role actually needs.
Who this guide is for
- Job seekers writing or trimming a skills section
- Career changers identifying transferable skills
- Anyone whose skills list looks generic
Choosing the right skills
Hard skills
- Specific, demonstrable abilities (tools, methods, languages)
- Name them precisely; back them up in experience bullets
Soft skills
- Behavioural strengths (communication, collaboration, ownership)
- Show them through outcomes rather than as standalone words
Role-relevant selection
- Prioritise skills the role genuinely requires
- Cut generic skills that add no signal
Match to the job description
- Map your real skills to the requirements — see how to write job descriptions to read requirements well
- Mirror genuine terminology; never fabricate to match
- Reviewers screen for relevant signal — see the candidate screening guide
Examples by category
Technical: [tools / methods you can demonstrate]
Domain: [role- or industry-specific knowledge]
Ways of working: [collaboration, ownership — shown via outcomes]
Languages: [with honest proficiency]
Common mistakes
- Long generic lists with no relevance
- Listing soft skills as bare words with no evidence
- Claiming skills you cannot demonstrate
- Identical skills section for every role
- Vague terms instead of specific, credible ones
Practical checklist
A quick, copy-friendly checklist.
☐ Skills mapped to the job’s real requirements
☐ Hard skills specific and demonstrable
☐ Soft skills evidenced through outcomes
☐ Generic, low-signal skills removed
☐ Honest and accurate throughout
☐ Tailored per role
For informational purposes only. Resume and CV expectations vary by employer, country, role and applicant-tracking system. This is general educational guidance, not a guarantee of interviews or hiring outcomes — adapt it to the specific role and market.