The distinction that matters
A hard skill is something with a right answer. You can write SQL or you cannot; you hold an active RN licence or you do not; you have closed a set of books under IFRS or you have not. Because it is checkable, listing it is meaningful — a reader can confirm it in an interview, and a parser can match it against a posting.
A soft skill is a judgement about how you work: communication, leadership, adaptability, conflict resolution. Nobody self-assesses these accurately, everybody claims them, and no reader has ever changed their mind about a candidate because the word "collaborative" appeared in a list. That is not because soft skills are unimportant. They are frequently the thing that actually decides the hire. It is because a list is the wrong instrument for them.
The rule: list the hard, demonstrate the soft
Hard skills go in the skills section, named specifically, grouped. Soft skills come out of the skills section entirely and go into your experience bullets, where they turn into events.
"Excellent communication skills" is worth nothing. "Wrote the runbook the on-call rotation still uses, cutting escalations to the team by about half" is communication, demonstrated, and it also happens to be a better bullet. "Leadership" is worth nothing; "Took over a team of six mid-project after the lead left and shipped on the original date" is leadership, and no reader needs the abstract noun once they have the sentence.
This is why deleting your soft-skill list usually improves a resume twice over — it frees a line, and it forces the evidence into the section where evidence belongs.
Where each one lives
Concrete placement, since the abstract rule is easy to nod at and hard to apply.
- Hard skills — skills section: programming languages, software by name, machinery, licences, certifications, methodologies, languages spoken with a stated level, regulatory frameworks.
- Soft skills — experience bullets: leadership, mentoring, communication, negotiation, conflict resolution, prioritisation under pressure, stakeholder management.
- Borderline cases — either, if named specifically: "technical writing" is a hard skill; "writing" is not. "Incident command" is a hard skill; "stays calm under pressure" is not. "Stakeholder management across four business units" reads as concrete; "stakeholder management" alone does not.
When soft skills are the job
Some roles are mostly soft skills: management, sales, teaching, therapy, customer service, HR. The rule does not change — it gets more important, because in those fields everybody's skills list says the same six words and the résumés that stand out are the ones with incidents in them.
For a customer service role, the bullet that wins is not "strong de-escalation skills". It is "Handled the escalation queue for a 2m-user product, resolving about 40 cases a week with a 94% satisfaction score". Same claim, made in a form that can be interrogated. If a hiring manager cannot ask a follow-up question about it, it was not evidence.
The interview check
Run this over every skill on your page: what would you say if someone asked "can you give me an example?" If a real answer comes to mind in five seconds, the skill is defensible and it should stay. If what comes to mind is a rephrasing of the skill itself, it is not evidence and it is taking up a line.
That check catches the two failures that matter — soft skills with nothing behind them, and hard skills you listed because they were on the posting rather than because you have used them. The second is worse. A skills list that overstates gets you into an interview you then fail on the first technical question.
