How to write achievement bullets that land interviews

If you read fifty resumes you'll see fifty variations of the same line:

Responsible for managing the team's quarterly planning process.

It's everywhere because it's safe — it describes the work without claiming a result. The cost of safety is that the line is forgettable, undifferentiated, and gives the recruiter no reason to pick you over the next candidate who wrote something identical.

This guide is about how to write resume bullets the recruiter actually remembers. There's a structural shift that does most of the work, and a six-minute exercise that applies it to every line on your CV.

The two kinds of bullets

Every line on a resume is one of two things:

• A duty bullet — describes what you were supposed to do in the role.
• An achievement bullet — describes what you actually accomplished in the role.

The difference matters because a recruiter assumes you did your duties; that's the baseline for getting hired anywhere. What they're scanning for is evidence of impact — the achievements that separate one VP of Marketing from the next.

Most resumes are 90% duties and 10% achievements. The good ones invert that ratio.

The structural shift

Here's the move that changes a bullet from duty to achievement:

Verb (active) + Specific action (with context) + Result (quantified or comparative)

That's the same pattern as STAR (Situation, Task, Action, Result, compressed to bullet form) — but the shorthand we'll use throughout is V-A-R: Verb, Action, Result.

Compare:

Duty: Responsible for the lifecycle email programme.

V-A-R: Rebuilt the lifecycle email programme around behavioural triggers, lifting activation-to-paid conversion 22% and adding $180k in monthly contribution within two quarters.

Same work, three structural changes:

1. Verb up front. "Rebuilt" instead of "Responsible for". Past tense, active, specific.
2. Action with context. "Around behavioural triggers" tells the reader how you rebuilt it — the kind of detail that signals you actually did the work.
3. Result, quantified. Two numbers, one timeframe. Even if the recruiter only skims, those numbers stick.

The whole shift is in the verb and the result. The middle (the what) you already know — it's the work you did.

A six-minute exercise to apply this to your whole CV

Open your resume. Walk through every bullet in order. For each one:

Minute 1: Replace the verb

If the bullet starts with "Responsible for", "Worked on", "Helped with", "Tasked with", or "Involved in", swap in a real verb. The new verb should describe what you actually did:

• "Responsible for the website redesign" → "Shipped the website redesign"
• "Worked on the migration" → "Led the migration"
• "Helped with the launch" → "Built the launch playbook"

If you helped with something but didn't drive it, say so honestly: "Contributed to" is weaker than "Led" but stronger than "Worked on".

Minute 2: Add context

After the verb, in 5–10 words, describe how or with what:

• "Shipped the website redesign (Webflow + Sanity CMS, 4-person team)"
• "Led the migration from on-prem MongoDB to Atlas, across 14 services"
• "Built the launch playbook for our largest enterprise customer, in 3 weeks"

The context anchors the achievement in reality. Vague achievements feel inflated; specific ones feel credible.

Minute 3: Add the result

End with a measurable or comparative outcome. The four flavours of result that work:

• Percentage: "lifting conversion 18%"
• Dollar/number: "saving $240k annually"
• Time: "reducing onboarding from 14 days to 3"
• Comparative: "the largest single deal in the team's history"

Numbers don't have to be precise. "~30% faster" is better than no number. If you genuinely don't have one, use a comparative scale.

Minute 4–6: Repeat

That's it. Three minutes per bullet, six bullets per role, two roles to focus on (the most recent two carry the most weight). Twenty-four minutes for a resume rewrite that materially changes your interview rate.

What if you don't remember the numbers?

Three ways to recover them:

1. Check your old planning docs. Quarterly review documents, OKR retros, internal wikis. Companies usually keep this stuff longer than you expect.
2. Ask a former teammate. A two-line Slack DM to someone who worked on it with you. People remember.
3. Reconstruct conservatively. If you remember "we doubled signups" but not the exact number, "Roughly doubled sign-ups in the first quarter post-launch" is honest and specific enough. Don't round up; round down, and stay grounded.

The hierarchy of bullet quality

Once your V-A-R structure is in place, polish runs along a quality ladder:

Tier 4 (avoid): "Responsible for managing the team." Vague verb, no action, no result.

Tier 3: "Managed a team of 6." Specific number, but no result. Reads as a duty.

Tier 2: "Managed a team of 6, shipping three platform features." Action and a comparative-ish result. Better.

Tier 1 (target): "Built and managed a team of 6 platform engineers, shipping three core platform features (auth, billing, search) that now serve 80% of company revenue." Verb, scope, what got built, and a contextual result that signals impact.

You don't need every bullet at Tier 1. Two or three Tier-1 bullets per role is enough to elevate the whole CV. Aim for them on your most recent and most relevant work; let older or less-relevant bullets sit at Tier 2.

The honest summary

Strong resume bullets aren't about better prose. They're about restoring information that was already there: the verb you used, the specifics of what you did, and the outcome you produced. Duty bullets are usually the result of omitting — not exaggerating — the truth about your work.

The six-minute exercise costs nothing and compounds across every application you'll send. Do it once on each role, save the strong bullets, and reuse them. The work pays back immediately on the next JD you tailor.