How do I write CV achievements if I don't have access to company metrics like revenue?

Use the numbers your role produces, not the ones the finance team owns. Almost every job generates measurable data the employee can see directly — tickets resolved, wait times, error rates, cycle times, pass rates, time-to-hire. Reach for those. When there's no direct number, estimate honestly by multiplying two things you do know (a task done 20 times a week, 15 minutes saved each) and mark it as an approximation. A defensible estimate beats a vague duty every time.

Isn't it arrogant to say "I did X" when the work was really a team effort?

It can feel that way, especially in cultures that emphasise "we." But a CV is read by systems and recruiters scanning for individual capability — collective phrasing gets filtered out. The honest resolution is to claim your verb and name the team's scope: "Drove the migration with a four-person squad." You're stating your genuine role, not stealing credit. Be a good teammate at work and still write "I" on the résumé — the two aren't in conflict.

What if I only have responsibilities and no real achievements to list?

You almost certainly have more than you think. Go role by role and ask: what was broken when I arrived and better when I left? What did people thank me for or copy from me? What would have gone wrong without me? What can I count? Any process you improved, template others adopted, or problem you prevented is an achievement — you just haven't framed it as one yet.

2026-07-10 · Daniel Zambrano

CV Achievements by Role: Real Before-and-After Examples for 12 Jobs

The cruel joke of modern hiring: your company sells a "no ego, we win as a team" culture, and then every recruiter wants to read "I did X, I achieved Y." You can't opt out of that game and still get the interview — but you can play it honestly. This is how to turn duties into achievements for any role, even when the impressive numbers live in a finance dashboard you'll never see.

Here's the tension nobody names out loud. Good teams train you to say "we." Standups, retros, the whole ceremony of it — nobody shipped that feature alone, nobody closed that quarter alone, and pretending otherwise is how you become the person everyone quietly resents.

Then you sit down to write your CV, and every piece of advice tells you the opposite: own it. Use "I." Lead with your impact. It feels like bragging. It feels a little dishonest. For some jobs — the ones built entirely on collaboration — it feels almost impossible.

So let's be clear about what's actually going on, and then let's make it work for you.

The "no ego" trap — and how to play it honestly

The CV is not your culture. It's the ticket into the room. A recruiter spends seconds on the first pass and an applicant tracking system spends milliseconds — neither is scanning for humility. They're scanning for evidence that you specifically can do the job. Collective phrasing gets filtered out, not because modesty is bad, but because "was involved in" tells them nothing about you.

The resolution isn't to fake solo heroics. It's truthful ownership of your slice of a team win:

Claim your verb, name the team's scope. "Drove the migration with a four-person squad" — the verb is yours, the squad is context. You're not stealing credit; you're stating your role in it.
"Contributed to" is where achievements go to die. It reads as "was in the room." Replace it with what you actually owned: led, built, designed, negotiated, unblocked, shipped, cut, grew.
Be a good teammate Monday to Friday, and still write "I" on the résumé. These aren't in conflict. One is how you work; the other is how you get hired to keep working.

Play the rules to get the interview. Live the values once you're inside. Both things are allowed.

Duty vs achievement: the one move that changes everything

A duty tells a recruiter what your job was. An achievement tells them what you did with it. That's the entire difference, and it's a framing problem, not a numbers problem.

The formula:

[Strong verb] + [what you did] + [measurable outcome] + [scope or context]

❌ "Responsible for managing the deployment pipeline"
✅ "Cut deploy time from 40 minutes to 6 by parallelizing CI — unblocked ~15 daily releases"
❌ "Handled customer support tickets"
✅ "Resolved 40+ tickets a day at 95% satisfaction, and wrote the FAQ that dropped repeat tickets 30%"
❌ "Worked on the checkout redesign"
✅ "Led the checkout redesign that lifted conversion 12%"

If you don't have a number, reach for a before/after, a frequency, or a scope (team size, budget, users, volume). Which brings us to the objection everyone raises.

"But I don't have the numbers"

This is the most important section here, because most advice quietly lies to you. "Saved $4,000 a month in cloud costs" needs a finance dashboard almost nobody on the team can actually see. So don't reach for the number your company owns. Reach for the number your role owns.

Every job sits on top of metrics the employee personally generates or can see. Five places to find them:

Things you can count yourself. Tickets closed, features shipped, clients managed, people onboarded, reports produced. No permission required.
Time — before vs. after, that you witnessed. You know the report used to take a day and now takes an hour. That's your data.
Scale of what you touched. Requests a day, users of your feature, rows in the dataset, size of the team — usually visible on tools you already use.
Quality you can observe. Error rate, bug count, defect rate, wait time, satisfaction scores — often on your own dashboards.
Adoption and reach. "Adopted as the team standard," "reused by five teams," "cited in the post-mortem as the fix." Social proof, not finance.

And when there's still no number, estimate honestly by multiplying two things you already know:

The deploy ran ~20× a day. My change saved ~15 minutes each. → "reclaimed roughly 5 hours a week of engineering time."

That's defensible math from numbers in your hands. The rules that keep it honest: use "~" and "approximately," round rather than invent, and be ready to explain the math in the interview. A truthful estimate beats a fabricated precise figure every time — and it beats a vague duty every single time.

Here's the same software-engineer win, rewritten the honest way: instead of "saved $4k/mo in compute" (needs finance), write "cut server instances from 12 to 4 and p95 latency from 800ms to 180ms." Same achievement, more credible, and you can source every number yourself. The cost saving is implied — the reader does that math — and you never claimed a figure you can't defend.

Achievements scale with seniority

The type of achievement shifts as you climb. Don't force a junior bullet to sound like a director's, or a director's to sound like a junior's.

Entry / Junior — you won't have big business metrics; claim initiative, speed, and concrete small wins. "Closed 60+ bugs in six months; automated the release checklist, saving the team ~3 hours a week."
Mid-level — you own things end to end; claim delivery and measurable output. "Shipped the notifications service handling 2M events a day; cut error rate from 4% to 0.3%."
Senior — claim technical leadership and multiplier effects. "Redesigned the billing data model, cutting month-end close from five days to one."
Staff / Principal / Lead — org-level leverage. "Set the API standards adopted by six teams; the shared gateway removed ~30% of duplicated auth code."
Manager — you claim your team's outcomes and how you built the team. "Grew the team from 4 to 11 while raising retention to 95%; the squad shipped the mobile relaunch that added 250k monthly users."

Your role, your metrics: 12 free cheat sheets

The "numbers you actually hold" are different for every job. A nurse, a salesperson, and a data analyst all have real, defensible metrics — they just live in different places. So we built a one-page cheat sheet for each of twelve common roles. Every sheet gives you: the metrics your role owns (no finance access needed), five before-and-after rewrites, an honest-estimation example, and how the bullet scales from junior to senior.

Grab any that fit you — free, no sign-up, no email.

Software Engineer Product & Project Manager Sales Marketing Customer Support & Success Finance & Accounting Operations Design & UX Healthcare Teaching & Education HR & Recruiting Data & Analytics

No achievements yet? You have more than you think

If your draft is all duties, you haven't failed at your job — you've just never mined it for wins. Go role by role and ask:

What was broken when I arrived, and better when I left? Any process you fixed, sped up, or made less painful is an achievement.
What did people thank me for, or copy from me? A template, a script, a checklist others adopted is impact with your name on it.
What would have gone wrong if I hadn't been there? Prevented a fire, caught an error, unblocked a launch — that counts.
What can I count? Volume, frequency, scope. Even "consistently handled X per week" beats "responsible for X."

And harvest continuously, while you still have access. Keep a running brag doc — one line per win, with the number, on the day it happened. The best time to record an achievement is the week it happens, not two years later from memory after you've lost the login.

Where QuillCV fits

This is exactly what our CV generator is built to do. It doesn't just reformat your experience — it reviews each bullet against the job description and your ATS score, and where it finds a duty masquerading as an achievement, it flags it. If a role has no achievement at all, it suggests realistic ones based on your experience and the target job, using the same "numbers you actually hold" thinking as these cheat sheets — so you're prompted for a countable win, never asked to invent a dollar figure you can't defend.

Because the goal was never to teach you to brag. It's to make sure the true, specific, valuable things you did don't get filtered out by a system that only reads impact.