Hard skills describe specific learned tasks, methods or tools. Soft skills describe how you work with people and situations. A resume needs the abilities relevant to the vacancy, supported by examples; it does not need a prescribed ratio of hard to soft skills.
This page explains the distinction and how to prove both. Use skills to put on a resume to choose a shortlist, or skills section formats to arrange it.
Hard skills and soft skills compared
| Hard skill | Soft skill used alongside it | Evidence that can show both |
|---|---|---|
| Spreadsheet analysis | Explaining findings | A report and a clear explanation of its limits |
| Software testing | Collaboration | Reproduction steps discussed with a developer |
| Invoice reconciliation | Attention to detail | A discrepancy found and referred for correction |
| Document design | Responding to feedback | Changes made after a review |
| Scheduling | Prioritisation | A revised plan when two deadlines conflicted |
The boundary is not always neat. Presenting findings involves both a learned technique and judgement about the audience. You do not need to debate the category on your resume; explain the task and your contribution.
Is your resume actually getting responses?
Your resume might be missing something important
Upload your resume → see its weakest areas → fix them, one by one.
Free. Takes less than 2 minutes.
Replace labels with observable actions
“Excellent communicator” is a claim. A specific example shows what communication involved. These original examples are fictional; adapt only the structure.
Communication
Before: “Excellent verbal and written communication.”
After: “Turned installation notes into a short customer setup guide and checked the instructions with the support team.”
Problem-solving
Before: “Strong problem solver.”
After: “Compared failed import records, identified inconsistent date formats and tested a correction on a sample before rerunning the import.”
Teamwork
Before: “A collaborative team player.”
After: “Agreed task ownership with three project partners and used a shared checklist to track the remaining work before submission.”
Leadership
Before: “Natural leader.”
After: “Coordinated the volunteer rota, explained responsibilities to new helpers and escalated unfilled shifts to the organiser.”
None of these requires an invented percentage. Add a measured result if you have one and can explain its source.
Show a hard skill at the right level
“Python” alone leaves your experience unclear. “Python: pandas data cleaning in a university project” is more precise for a learner. “Built and maintained Python validation scripts for weekly reporting” describes a different level and context.
Distinguish completed training from applied experience. A certificate can support your learning history, but it should not imply responsibilities you have never held. Name the issuing organisation and credential accurately when it matters to the role.
Where to put each type
Relevant tools and methods can sit in a compact skills section. Behaviours usually become more credible in experience and project bullets, where readers can see the context. Avoid a separate block containing only “leadership, adaptability, teamwork” with no examples elsewhere.
A fictional example:
Technical skills: Excel pivot tables and reconciliation; PowerPoint reporting; CRM case records.
Experience: Prepared the weekly service report and explained incomplete records to the team before figures were circulated.
For more complete sections, see resume skills section examples.
A short evidence exercise
Choose one technical skill and one interpersonal skill from the vacancy. For each, write down the situation, your own action and the outcome you observed. Remove anything done by the wider team that you cannot reasonably claim as your contribution.
Next, combine the related facts into a clear bullet. If the result is unknown, describe the finished output instead. “Prepared a reviewed handover checklist” is useful evidence; “transformed productivity” needs proof.
Common questions
Which type matters more?
That depends on the work. A role may require a specific technical capability alongside careful communication. Treat essential requirements as requirements, not as something a long list of unrelated strengths can compensate for.
Should every soft skill appear by name?
No. Use relevant terminology naturally, and show the behaviour in action. Repeating labels does not guarantee screening success.
Can I use examples outside paid work?
Yes, if you identify the context. Study, volunteering and personal projects can provide evidence. Our skills wording examples show how to describe contributions without inflating them.