Writing · 2026-08-13 · 15 min read

CV achievements: examples and honest metrics

How to write CV achievements with examples and metrics you can defend. Bullet formula, before/after by role, and honest alternatives when you have no numbers. ClarCV.

Work experience is where interviews are won or lost. Recruiters do not want your contract job description; they want evidence you solved problems like those in the posting. Responsible for customer support is forgettable; cut average response time 35% in 4 months leading a team of 6 is shortlist material.

Moving from duties to achievements does not require inventing KPIs. It requires verb, context, and result or scope. This guide covers bullet formula, before/after by job type, honest metrics, alternatives without numbers, mistakes, and a checklist—plus ClarCV for clarity and an ATS PDF.

ClarCV (clarcv.com) flow: upload PDF or Word, AI analysis, ATS templates, download. Start free; Pro €7/month. ES/EN depending on the process.

Duties vs achievements

Duty: what you were supposed to do. Achievement: what changed because you intervened. Duty: Handled orders and complaints. Achievement: Resolved shipping complaints in under 48 hours across ~120 tickets/week, cutting escalations 25%. If recruiters only read three bullets from your latest role, make them achievements.

Healthy mix: 60–80% achievements or impactful contributions, plus critical ownership duties (tools, shifts, compliance). Avoid entire lists of responsible for, collaborated on, supported with no effect.

• Duty: routine with no visible change.
• Achievement: measurable change, clear scope, or solved problem.
• Contribution: part of a team outcome (be honest).
• Ownership: an area that depended on you even without a %.

Bullet formula

Verb + what you did + for whom / tools / scale + result. Example: Automated weekly reporting in Excel/Power Query for sales, removing 5 manual hours per close. Without a result, keep context: Coordinated onboarding for 15 partners in Salesforce during Q2.

Strong verbs: implemented, reduced, negotiated, launched, migrated, designed, trained, stabilized. Avoid participated without clarifying your part. Three to six bullets for recent roles; rank by relevance to the posting.

Before and after by job type

Support — Before: Phone and email support. After: ~50 contacts/day in Zendesk at 4.6/5 CSAT; 12 macros cut repetitive resolution 20%. Operations — Before: Stock control. After: Renegotiated 3 key suppliers and cut stockouts 15% in peak season.

Marketing — Before: Managed social and campaigns. After: LinkedIn Ads ≈€8k/quarter, CPL −22%. Engineering — Before: Developed and maintained apps. After: Migrated notifications to async queue; errors −40%, deploy in 12 minutes. Sales — Before: Prospecting and closing. After: 28 SMB accounts, avg ARR €4.5k, 118% quota. HR — Before: Recruiting. After: 35 technical roles end-to-end; time-to-hire 32 days (from 48) in Greenhouse.

Admin — Before: Calendar and invoicing. After: Monthly invoicing for 60+ vendors in Holded; payment delays from 12 to 4 days. Pattern: activity + scale + tool + effect.

Metrics without lying

Good metrics are specific, interview-defensible, and relevant. Prefer %, time, money, volume, quality, speed. If confidential, use ranges or relatives (~20%, six-figure book) without fake precision.

Recover numbers from OKRs, emails, tickets, repos, CRM, analytics, or a former manager. Estimate with approximately or weekly average. Never invent an indefensible 47%.

• Volume: tickets, accounts, orders, users, SKUs.
• Time: deadlines, SLAs, time-to-X.
• Money: savings, revenue, budget owned.
• Quality: errors, CSAT, compliance.
• Adoption: % usage of a new process or tool.

If you lack numbers

Options: scope (team, book, regions), frequency (daily, sprint, close), complexity (regulated, legacy, crisis), qualitative before/after, deliverable (playbook, migration, training). Example: Documented technical onboarding (20 pages) adopted by 8 engineers, fewer questions to seniors. Or coordinated a store opening in 6 weeks: vendors, shifts, compliance.

Teamwork: led, co-led, contributed as IC, partnered with Product. Do not claim the whole collective win. Better: squad launched X; my ownership was Y, which enabled Z.

Structure per role

Title, company, location, MM/YYYY dates, then 3–6 bullets. Optional one-line company context if unknown. Put tools inside bullets when they add signal, plus a clean Skills list. Older roles: 1–2 bullets or title/dates only. Internships and freelance count when they show real work.

Mistakes that weaken experience

• Copying an internal job description with no outcomes.
• Every bullet starts with Responsible for.
• Impossible or inconsistent metrics.
• Opaque internal jargon.
• 12 bullets per role.
• Ambiguous dates or mixed languages.

Print, cross out bullets without strong verb + context, rewrite, align 3–5 to the posting with truthful keywords. ATS finds terms; humans find impact.

15-minute checklist

• Title, company, readable dates?
• ≥50% achievements in the recent role?
• Honest numbers or scope?
• Varied verbs?
• Job-ad keywords in real context?
• No empty jargon?
• Figures defensible in interview?
• Selectable-text PDF?

After manual edits, ClarCV flags vague phrasing and structure friction. Upload, review, apply an ATS template if needed, download. Free to start; Pro €7/month if you iterate across many postings.

Frequently asked questions

Before you send, ask someone outside your field to read the CV for twenty seconds and say what you do. If they cannot answer, the summary or first role needs more clarity. That human test complements ATS checks and prevents surprises in real processes.

Keep one stable base version and create variants only when the posting changes role family. That reduces date errors and keeps consistency across applications. ClarCV helps regenerate clean variants without rebuilding layout by hand every week.

If your path has gaps, do not hide them with confusing dates: parsers and recruiters notice. Explain the period briefly in one line or prepare for the interview. Clarity usually builds more trust than cosmetic calendar cover-ups.

Also check consistency with LinkedIn: same titles, employers, and approximate dates. A large mismatch creates unnecessary doubt even when the CV parses well and keywords match the posting.

Prefer evidence over adjectives. Replace excellent communicator with an achievement that proves communication: client presentations, docs the team adopted, or fewer tickets after better internal guides.

When you tailor the document to a posting, change the summary first and three to five bullets from the most recent role. That twenty to thirty percent edit usually moves the match more than rewriting everything from scratch each time.

Use clear file names like Name_Surname_Role.pdf and avoid final_v12 versions. An orderly file reduces upload errors on portals with size or filename character limits.

If you hesitate between one or two pages, look at the density of relevant wins: a sharp one-pager beats two pages of repeated duties. Recruiters appreciate respect for their scanning time.

In ClarCV the flow is upload PDF or Word, review AI analysis, apply an ATS template, and download. Start free; Pro costs seven euros per month with transparent pricing, in Spanish or English depending on the application.

Do not confuse density with filler. Every line should survive the question why this matters for this role. If you have no answer, delete it or rewrite with context and result.

European portals usually accept PDF with selectable text. Run the copy-three-paragraphs-into-notepad test before you send. If you cannot select text, the ATS likely cannot either.

When you prepare for interviews, turn each strong bullet into a short STAR story. The CV opens the door; spoken evidence closes it. If you cannot tell the example, the CV verb is too ambitious.

Before you send, ask someone outside your field to read the CV for twenty seconds and say what you do. If they cannot answer, the summary or first role needs more clarity. That human test complements ATS checks and prevents surprises in real processes.

Keep one stable base version and create variants only when the posting changes role family. That reduces date errors and keeps consistency across applications. ClarCV helps regenerate clean variants without rebuilding layout by hand every week.

If your path has gaps, do not hide them with confusing dates: parsers and recruiters notice. Explain the period briefly in one line or prepare for the interview. Clarity usually builds more trust than cosmetic calendar cover-ups.

Also check consistency with LinkedIn: same titles, employers, and approximate dates. A large mismatch creates unnecessary doubt even when the CV parses well and keywords match the posting.

Prefer evidence over adjectives. Replace excellent communicator with an achievement that proves communication: client presentations, docs the team adopted, or fewer tickets after better internal guides.

When you tailor the document to a posting, change the summary first and three to five bullets from the most recent role. That twenty to thirty percent edit usually moves the match more than rewriting everything from scratch each time.