How to put numbers on your work

Four places numbers hide

Almost any role has countable work. The trick is knowing which axis to count along.

• Volume - customers, tickets, invoices, articles, shifts, sites, students, transactions per day, week or month.
• Money - budget held, revenue touched, cost saved, contract value, purchase orders approved.
• Time - hours saved per week, turnaround cut from X to Y, delivery brought forward.
• Scale - team size, number of branches, countries covered, systems supported, users of the thing you built.

An honest estimate beats a blank

You do not need audited figures. Around, approximately and a range are all acceptable, and interviewers read them as a sensible person estimating rather than as a claim.

Reconstruct from what you remember: if you served roughly one customer every two minutes across a six-hour shift, that is about 180 a shift. Write approximately 180 customers per shift and be ready to explain the arithmetic.

Percentages need a base

Improved conversion by 300 percent is meaningless if it went from one sale to four. Give the reader the starting point: raised trial-to-paid conversion from 2 percent to 8 percent across roughly 4,000 monthly signups.

When the absolute number is small, use the absolute number. When it is large, the percentage carries more weight. Never use both to inflate the same result.

Claim your actual share

If you were one of six people on a project that saved a million, do not claim the million. Write your part: owned the supplier negotiation workstream in a programme that cut annual spend by 1.2 million AED.

This is more persuasive, not less. It shows you understand your own contribution, which is exactly what an interviewer probes.

Where there is genuinely nothing to count

Some work resists measurement - early-stage research, confidential casework, creative direction. Substitute scope and outcome: the decision that followed, the audience it reached, the standard that was met, the audit that passed.

Led the internal review whose recommendations were adopted across all four regional offices has no percentage in it and still tells the reader what happened.

Numbers by function

If you are stuck, start from what your function is normally measured on.

• Sales: pipeline value, quota attainment, deal size, retention, new accounts opened.
• Support: tickets per week, first-response time, resolution rate, satisfaction score.
• Engineering: uptime, latency, deployment frequency, defects, users served.
• Finance: close time, budget managed, cost saved, audit findings closed.
• Marketing: leads, cost per acquisition, conversion rate, audience growth.
• Operations: throughput, error rate, cycle time, headcount supervised, sites covered.
• Teaching and training: cohort size, pass rates, sessions delivered, materials written.

Write the number where it lands hardest

Put the result at the front of the bullet when it is the headline, and at the end when the method is the interesting part. Cut month-end close from nine days to three by automating reconciliations leads with the win; both orders work, neither buries it in the middle.

Two quantified bullets at the top of your most recent role do more than ten scattered through the page, because that is where the first screen actually looks.