May 9, 2026 · 4 min read

How to Quantify Achievements on Your CV (with 30 Examples)

The exact formula for turning vague duties into measurable achievements on your CV. 30 before/after examples across roles, plus a free AI quantifier.

Recruiters trust numbers. The single biggest signal that separates a strong CV from a weak one is whether each bullet shows a measurable outcome. "Led a team" tells a recruiter nothing. "Led a team of 8 engineers, delivering 12 features per quarter (+25% velocity)" tells them you can manage scope, scale, and time.

This guide gives you the exact formula and 30 before/after examples. If you want it done in 5 seconds, our [AI Quantifier](/cv-builder) takes a vague bullet and returns 3 quantified variants — pick the one that fits.

The formula

Every strong achievement bullet has 4 parts:

  1. Action verb (built, led, increased, reduced, automated)
  2. Object (what you acted on — feature, team, pipeline, revenue)
  3. Metric (the number that proves the action mattered — %, €, count, time)
  4. Outcome / context (why this number matters)

Bullet template: , ,

What to measure (by role)

Different roles count different things. Here is a starter list:

  • Engineering: latency reduced, deploys/week, bugs/quarter, pull requests reviewed, services owned, uptime, downtime saved
  • Sales: revenue, pipeline value, accounts won, conversion rate, deal cycle days
  • Marketing: leads, organic traffic, conversion %, CAC, retention rate
  • Operations: cost saved, processing time, error rate, throughput
  • Customer support: tickets resolved, CSAT score, resolution time, deflected with KB articles
  • Design: screens shipped, A/B tests won, design system components
  • Management: team size, budget owned, hiring, retention

If you cannot find a number, ask: how many, how much, how often, how fast, compared to what?

30 before / after examples

Engineering

  • Before: "Worked on backend services." → After: "Owned 3 backend microservices handling 2M requests/day; reduced p95 latency from 420ms → 180ms."
  • Before: "Wrote tests." → After: "Increased test coverage from 47% → 89% across 12 modules; halved CI failures."
  • Before: "Helped with deployments." → After: "Migrated CI from Jenkins → GitHub Actions; cut average deploy time from 28min → 6min."
  • Before: "Mentored juniors." → After: "Mentored 4 junior engineers through onboarding; all 4 promoted within 18 months."

Sales / Marketing

  • Before: "Did outreach." → After: "Booked 47 qualified meetings/quarter from cold outreach (+38% above team avg)."
  • Before: "Ran campaigns." → After: "Launched 6 paid campaigns in EU markets; generated €420k pipeline at 3.2x ROAS."
  • Before: "Wrote blog posts." → After: "Authored 22 SEO articles; one ranked #1 on Google for 'rewrite webinar landing pages'."

Operations / Support

  • Before: "Handled customer queries." → After: "Resolved 1,200 tickets/quarter at 4.7/5 CSAT; deflected 30% with new KB articles."
  • Before: "Improved processes." → After: "Redesigned onboarding workflow; reduced new-hire ramp from 6 weeks → 3 weeks across 24 hires."

Management

  • Before: "Managed a team." → After: "Built and led a team of 7 (mix of FTE + contractors); 0 attrition over 14 months."
  • Before: "Owned a budget." → After: "Owned €1.2M annual SaaS budget; renegotiated 8 contracts saving €180k/year."

Mistakes when quantifying

  • Inflating numbers — recruiters pattern-match. "+5000% growth" reads as fake.
  • Counting noise — "sent 500 emails" is volume, not outcome. Convert to outcome (replies, meetings, deals).
  • One metric per bullet — squeezing 3 numbers into one bullet makes it unreadable.
  • Forgetting the baseline — "+25%" means nothing without a starting point or peer comparison.
  • Vague qualifiers — "significantly", "many", "some". If you cannot pick a number, do not pretend.

Quality checklist

  • Every experience entry has at least 60% of bullets with a number
  • Numbers feel proportional to your level (a junior with "$100M revenue impact" is suspicious)
  • Each metric is the outcome, not the activity
  • Action verb starts the bullet — never "Responsible for"
  • Mix percentages, absolute numbers, and time savings — don't repeat the same metric type

FAQ

What if my role does not have obvious numbers?

It does — you just need to ask better questions. How many people were affected by your work? How much faster did something become? What broke less often after you arrived? Even support roles have CSAT, deflection rate, and queue length.

Should I share confidential numbers?

Use ranges or relatives. "Reduced churn by 30%" is fine even if absolute MRR is confidential. "Owned a budget in the high six figures" works for sensitive figures.

How many bullets per role?

3–5 is the sweet spot. Two is thin, six starts to lose impact. Lead with your strongest bullet.

Final takeaway

The fastest way to quantify your CV is to start with what changed because of you, then work backwards to the number. If a bullet does not contain a number or a measurable outcome, rewrite it. Or paste it into our [AI Quantifier](/cv-builder) and pick the variant that fits your reality.

Free tool

Try it yourself — no sign-up required.

📄 Try CV Builder →