The soft skills trap on your CV (and how to replace them with proof)

Out of 100 CVs received for a project manager role, how many say "team player"? About 50. "Proactive"? 35. "Detail-oriented and organised"? 20. These keywords are so saturated they no longer say anything. Worse: they give the impression you have nothing better to say about yourself. Here's how to replace them with what actually works.

Why classic soft skills don't work anymore

Three reasons:

1. Everyone lists them. "Team player" on an English CV in 2026 is like "passionate" — it has become invisible.
2. They're not verifiable. The recruiter can't test "team spirit" by reading your CV. They need proof.
3. The ATS doesn't care. Screening software looks for specific technical skills and quantified action verbs, not fuzzy adjectives.

Maryline Albouy, recruitment lead at CGI, puts it differently: "a candidate who writes 'detail-oriented and organised' makes me move to the next application. A candidate who writes 'structured the tracking of 12 parallel job sites with an average delay of 2 days' makes me open my calendar to meet them."

The pattern to adopt: SOFT SKILL → ACTION → NUMBER

For each soft skill you want to highlight, ask three questions:

1. What concrete action illustrates this skill?
2. In what measurable context?
3. With what quantifiable result?

Five examples, before / after.

Example 1 — "Team player"

Before (cliché): Team spirit • Collaboration sense • Good interpersonal skills

After (proof): Coordinated an 8-developer team over 18 months, delivering 12 sprints with no major deadline slips

Or if you were the contributor, not the coordinator: Co-built the new code review process with 3 colleagues, 100% adoption in 6 weeks

Example 2 — "Proactive"

Before: Proactive • Initiative • Creative

After: Proposed and launched a new client onboarding program, reduced time-to-value from 14 to 5 days

Example 3 — "Detail-oriented and organised"

Before: Detail-oriented • Methodical • Organised

After: Set up a monthly tracking system for 40 client accounts, zero missed deadline over 12 months

Example 4 — "Communication"

Before: Excellent communication skills • Teaching mindset

After: Weekly facilitation of a product meeting for 25 people (designers, dev, marketing), produced a debrief read by the leadership team

Or: Wrote 8 technical blog articles, 12,000 cumulative views on LinkedIn

Example 5 — "Analytical mindset"

Before: Analytical skills • Critical thinking • Synthesis

After: Monthly analysis of churn data (cohorts, segments, scoring), identified 2 levers that reduced churn from 23% to 17% in 6 months

What if you don't have numbers?

This is the main question we get. The answer is almost always: you do, you just haven't articulated them. Look for:

Operational role

• How many files/clients/tickets handled per month?
• In what average time?
• What satisfaction rate (NPS, client feedback, complaint rate)?
• What time or money savings generated?

Management role

• How many people in your team?
• What budget managed?
• How many parallel projects?
• What turnover in your team (if low, it's a strong number)?

Product / creative role

• How many users reached?
• What adoption / conversion / retention metric?
• How many deliveries / publications?
• What direct measurable impact?

Junior / intern role

• How many training hours received?
• How many events / talks organised?
• How many pages / articles produced?
• What success rate on a course project?

If really nothing comes to mind, ask a former colleague or manager. They often have a quantified memory you no longer have.

The "hidden soft skills" rule

Some soft skills land poorly when stated directly but are in the nature of your work. Don't write them — let them be inferred.

Examples:

• If you held a customer-facing role for 5 years → you have patience and diplomacy. No need to write it.
• If you managed 12 parallel projects → you're organised. No need to write it.
• If you trained 3 juniors → you can transmit knowledge. No need to write it.

The experienced recruiter reads between the lines. Save your CV space for what isn't deducible.

Special case: junior CVs and career changes

When you have little professional experience, the instinct is to pad the "skills" section with generic soft skills. Mistake. Prefer:

• Mention school or personal projects with numbers: Built an e-commerce site end to end (Next.js, Stripe, Supabase) — 200 unique visitors over 3 months
• List specific technical tools instead of fuzzy qualities: Figma, Notion, Linear, Slack, Loom rather than Good mastery of digital tools
• Detail 1-2 community / association achievements: Treasurer of the student union, managed a €28K annual budget, organised 6 events

The Sirius method to rewrite your skills section

If you want frank feedback on your CV — which soft skills are clichés, which deserve proof, which proofs are missing — Sirius can do it. You upload your CV, you indicate the target role, and you get a diagnosis with 3 to 7 concrete points to fix: where your profile sounds generic, and how to phrase it differently.