← Back to blog
EN | ES | PT
· Daniel Zambrano

How to Quantify Your Achievements (Even If Your Job Isn't Numbers-Driven)

Most CVs describe jobs. The ones that land interviews describe impact. The difference between a duty and an achievement isn't a numbers problem — it's a framing problem — and you can fix it for almost any role, even ones that never touch a spreadsheet.

The "quantify your achievements" advice gets thrown at every job seeker regardless of field. And then a primary school teacher or a ward nurse sits down to write their CV and stares at the screen, wondering what metric they're supposed to put on "taught a class" or "provided patient care."

This is where most people give up and fall back to listing duties. Which is exactly what everyone else does. Which is exactly why most CVs look the same.

There's a better way. And it works whether your job produces revenue reports or it doesn't.

Duties vs achievements: the difference

A duty tells a recruiter what your job was. An achievement tells them what you did with it.

"Responsible for client onboarding" tells me the task was assigned to you. "Redesigned the client onboarding process and reduced time-to-active from three weeks to ten days" tells me what you did with that responsibility and what changed as a result.

ATS systems score keyword matches either way — the word "onboarding" appears in both. But the human who reads past the ATS filter makes a judgment call about which candidate sounds like someone who gets things done and which sounds like someone who showed up. You want to be in the first group.

This matters even more in roles where everyone has the same basic duties. Every nurse does patient assessments. Every teacher writes lesson plans. Every project manager runs meetings. The CV that stands out is the one that shows what you did with those standard responsibilities — what you improved, built, fixed, or delivered.

The formula: action + context + result

Every strong CV bullet follows a pattern. You don't need to memorize it as a formula, but it's useful to check your work against it:

[Strong action verb] + [what you did / the scale / the context] + [what happened as a result]

The action verb does the heavy lifting at the start: led, built, redesigned, reduced, trained, implemented, launched, streamlined. Not "was responsible for," not "helped with," not "assisted in." Own what you did.

The context gives scale and specificity: for a team of 12, across three departments, covering 200 students, in a 6-month project, from scratch, across two sites. Without context, results are hard to evaluate. With it, they're compelling.

The result closes the loop: reduced errors by 30%, cut average wait time from 45 to 20 minutes, onboarded eight new hires in the first quarter, completed two weeks ahead of schedule. Results don't have to be percentages — they can be scale, frequency, time, or quality.

When you don't have hard numbers

You don't need a financial metric to write a strong achievement. Numbers are the clearest signal, but they're not the only one. Consider what you can qualify along these dimensions:

  • Scale: How many people, students, patients, clients, products, sites?
  • Frequency: Daily, weekly, per quarter? How often did this happen?
  • Time: How long did it take? Did you hit a deadline? Did you reduce a timeline?
  • Team: How many people were involved? Did you lead them?
  • Before and after: What was the situation before you intervened? What changed?
  • Scope: Was this the first time something was done? Did you build from scratch?

A nurse who reduced average patient wait times, a teacher who achieved the school's highest literacy improvement rate in a low-decile cohort, an operations manager who implemented a process that's still in place three years later — none of these need a revenue figure. They need specificity and an outcome.

Before & after examples

Primary school teacher
Before: Responsible for teaching literacy and numeracy to Year 3 students.
After: Designed and delivered a differentiated literacy program for 28 Year 3 students, with 85% achieving at or above expected level — up from 61% the previous year.

Operations manager
Before: Managed day-to-day warehouse operations and oversaw staff scheduling.
After: Restructured shift scheduling for a 40-person warehouse team, reducing overtime costs by 22% while maintaining same-day dispatch rate above 97%.

UX designer
Before: Responsible for designing user interfaces across web and mobile products.
After: Led UX redesign of the core mobile onboarding flow, reducing drop-off at step 3 from 48% to 19% based on post-launch analytics over 90 days.

Registered nurse
Before: Provided patient care and medication administration in a surgical ward.
After: Managed care for up to 8 post-surgical patients per shift in a high-acuity ward; implemented a bedside handover protocol adopted across the unit that reduced after-handover queries by roughly a third.

Project manager
Before: Managed projects from initiation through to delivery, coordinating with stakeholders and managing timelines.
After: Delivered a 14-month infrastructure migration project on schedule and 8% under budget, coordinating a cross-functional team of 11 across three time zones and two vendors.

Where QuillCV fits in

One of the hardest parts of writing achievement-focused bullet points is objectivity — it's difficult to evaluate your own experience from the outside. When you upload your existing CV and a target job description, QuillCV helps reframe what you've provided as outcomes where possible. We look at what you've described, match it against what the role values, and rewrite your experience in the language of impact rather than duty.

You'll still need to verify the specifics — the numbers, the team sizes, the timeframes. We can't invent those. But we can reshape generic descriptions into achievement-oriented statements that reflect what you've actually done in the terms that matter most to the people reading your application.

Every role creates results. Your job is to find them. Our job is to make sure they're stated clearly enough that a recruiter reading for six seconds can't miss them.