Cookie consent

We use cookies to analyze site usage and improve your experience. You can accept or reject non-essential cookies.

For more information, see our Privacy policy.

Skip to main content
6 min read

From Duties to Achievements: Writing CV Bullets That Prove Impact

How to write CV achievement bullets that prove impact: action-first structure, quantification, and before/after examples by industry and career level.

The Proof Formula

Recruiters skim for proof. A good bullet makes your contribution obvious, specific, and believable.

Action + Scope + Result (default) or Result + Action + Scope (when the metric leads)
Start with a strong action verb, add scope (team size, system, region, initiative), and end with the quantified result. Lead with the result only when the metric is unambiguous without setup — "Reduced churn 12% by redesigning onboarding" works result-first because the number and context are self-evident. If you know the STAR method (Situation, Task, Action, Result), this produces the same output with context compressed into scope.

Before & After Examples

Weak
"Managed sales pipeline."
Result-first (metric is clear)
"Increased qualified pipeline by €420k by introducing a weekly qualification process."
Weak
"Led a project team."
Action-first (scope matters)
"Led 12-person team to deliver ERP migration, cutting costs by €2M annually."

When hard numbers are not available

Not every role has clear metrics. For early-career positions, humanities, social roles, or support functions, focus on qualitative impact or proxy metrics that still show scope and outcome.

  • Qualitative impact: improved process clarity, reduced team confusion, positive client feedback, fewer errors.
  • Proxy metrics: class size taught, budget managed, tickets resolved per week, events coordinated, stakeholders supported.
Weak Example
"Helped with onboarding."
Strong Example
"Redesigned onboarding materials for 15-person team, reducing new-hire ramp-up questions by half."

Writing Tips

  1. Write the duty in plain words.
  2. Add the "why it mattered" (user, team, revenue, cost, risk).
  3. Add one detail that proves it (metric, tool, scale, constraint, timeframe).
  4. Aim for 14–18 words per bullet. Keep the strongest claim at the front. If a bullet runs over 25 words, it almost certainly contains two outcomes: split it. This applies at every career level.

How the app supports this

AI-generated achievements
The AI generates achievement bullets using Action + Scope + Result as the default, shifting to result-first only when the metric is strong enough to stand alone. It adapts bullet count to your career level (3-4 for entry, 4-5 for mid, 5-6 for executive). Always review and keep only claims you can defend with real evidence.

Industry and level variations

The formula works across roles, but the right metrics and framing differ by industry and career level. A bullet that would impress a sales hiring manager may read as irrelevant to an engineering lead. Getting the frame right matters as much as having the evidence.

For tech and engineering roles, lead with scale, speed, or system impact. Recruiters in this space look for throughput, reliability, and delivery cadence.

  • Scale: users affected, requests per second, system uptime, or data volume handled.
  • Delivery speed: "shipped in 3 weeks", "reduced build time from 45 to 8 minutes".
  • Cost and efficiency: cloud spend saved, compute hours cut, deployment time reduced.
  • Example: "Reduced API response time by 40% by replacing synchronous calls with a message queue, cutting timeout errors to near zero."

For commercial and sales roles, lead with revenue, pipeline, or margin. Absolute numbers beat percentages when the absolute value is strong.

  • New business won, quota attainment, average deal size, sales cycle shortened.
  • Client retention and growth: "grew account from £80k to £210k over 18 months".
  • Pipeline metrics: qualified pipeline added, conversion rate, close rate by segment.
  • Example: "Closed £1.4M in new business in FY24, 112% of quota, focusing on mid-market manufacturing accounts."

For early-career candidates and roles without direct metrics, use proxy metrics and show clear ownership. "Helped" is not a bullet. "Built", "introduced", and "redesigned" are.

  • Proxy metrics: group size supported, budget overseen, tickets resolved per week, events coordinated.
  • Scope anchors: "for a team of 12", "across 4 departments", "used by 200 students".
  • Process ownership: "introduced", "built", "redesigned" show initiative; "assisted" and "helped" do not.
  • Example: "Built internal onboarding tracker for a 30-person department, reducing manager check-in time by half."

What weakens a bullet

Passive voice (avoid)
"Was responsible for managing client relationships across the portfolio."
Active ownership (use this)
"Managed 22 client accounts across the DACH region, maintaining a 94% renewal rate."
Vague scope (avoid)
"Collaborated with various stakeholders to improve team processes."
Specific scope (use this)
"Ran weekly planning sessions with 3 product managers and 8 engineers, cutting sprint carryover by 30%."
Unverifiable claim (avoid)
"Significantly improved team morale and built a positive culture."
Observable outcome (use this)
"Introduced peer recognition and monthly retrospectives. Team attrition dropped from 4 to 1 leavers per year."

Three patterns kill otherwise solid bullets: passive voice that hides the actor, vague scope that gives recruiters nothing to assess, and claims with no observable evidence. Fix each by naming yourself as the subject, adding at least one number or constraint, and ending on what changed as a result of your action.

Ready to apply this?

Create your first CV and tailor it to your next job application.
© 2026 ZVee
Legal