A soft skill is worth listing on a CV only when a reader could not already infer it from the rest of the document, and most of the common ones, "team player", "hard worker", "good communicator", fail that test, because they describe a trait rather than something a reader can check, and nearly every candidate would claim the same ones about themselves given the chance. The soft skills worth keeping are the ones a bullet elsewhere in the CV already demonstrates, or the handful specific enough to the target role that stating them plainly still adds information a reader did not already have.
Why a stated trait carries so little weight
A line that reads "team player" or "strong communicator" asks a reader to simply take the claim on trust, since nothing about the phrase itself is checkable, and a reader has no way to distinguish a candidate who genuinely works well on a team from one who typed the phrase because it appears on every CV template they have ever seen. The words themselves are also so common that they stop registering as information at all once a reader has skimmed a handful of CVs in the same sitting; they become background noise the eye skips over on the way to the parts of the document that actually describe something. That is the real cost of a generic soft-skills line: not that it is dishonest, but that it uses valuable space near the top of a CV to say something a reader was always going to assume anyway.
A simple filter for which ones to keep
A soft skill earns its place on a CV under one of two conditions. The first is that it is genuinely demonstrated somewhere else in the document already, in which case naming it explicitly is often redundant rather than additive, and the space is usually better spent letting the demonstrated example speak for itself. The second, narrower condition is that the skill is specific and relevant enough to the target role that naming it plainly still tells a reader something they could not safely assume, "stakeholder management" for a role that explicitly involves negotiating between competing internal teams, or "bilingual client communication" for a role where that is a genuine, checkable requirement rather than a nice-to-have. A skill that fails both conditions, generic in wording and not clearly demonstrated anywhere, is the kind worth cutting.
Showing instead of stating
Most soft skills read more convincingly when they show up inside an experience bullet rather than as a standalone line, because a bullet can carry the evidence and the trait at the same time without asking a reader to trust either one on its own. "Led a cross-functional group of five to redesign the onboarding flow" demonstrates leadership and collaboration without the word "leadership" or "team player" appearing anywhere in the sentence, and it does so with a concrete detail, the size and composition of the group, that a bare trait claim never provides. This is the same underlying shift covered in turning duties into achievements on your CV: a description of what actually happened tends to carry more weight than a description of a quality the candidate is asking the reader to believe they possess.
Illustrative example: a stated trait rewritten as a demonstrated one
Before, stated directly: "Strong communicator and collaborative team player." After, rewritten to show the same qualities through what actually happened: "Presented weekly project updates to a mixed group of engineering and non-technical stakeholders, adjusting the level of detail for each audience, and coordinated daily with two other teams to keep a shared roadmap aligned." The rewritten version never uses the words "communicator" or "team player" at all, yet a reader comes away with a clearer, more specific picture of both qualities than the original line ever gave them, because the rewrite describes something the candidate actually did rather than a trait they are asking to be believed about.
When a short, separate soft-skills line still makes sense
A short list of soft skills near the bottom of a CV, rather than woven into every bullet, can still make sense for a candidate with limited work history to draw examples from, such as someone early in their career, where a compact line naming two or three specific, role-relevant qualities fills a gap a thinner experience section cannot yet fill on its own. Even there, specificity still matters more than a generic label: "comfortable presenting technical material to a non-technical audience" tells a reader more than the word "communication" does, even sitting in the same short list, because it names a situation rather than a trait.
Building the section
How to write a resume covers where a skills section fits into the overall structure of a CV and how it should read alongside the experience section it usually sits near. Apply the same filter to every soft skill on the page: keep the ones a bullet elsewhere already demonstrates, keep the handful specific enough to genuinely inform the reader, and cut the rest rather than padding the document with claims a reader was always going to have to take on faith.
Build yours
Start from an existing CV or a blank one in the builder and run each soft skill currently listed through the two-part filter above before deciding whether it stays as a stated line, moves into a bullet as demonstrated evidence, or gets cut entirely.
