How to quantify achievements when your job had no metrics

'Add metrics to your resume' is the most repeated advice in job hunting and the least useful for people whose employers never measured anything. The fix is to stop hunting for a percentage and start describing size.

Four honest number types

• Scale: headcount supported, devices managed, accounts owned, sites covered, budget touched.
• Frequency: tickets per week, reports per month, deployments per quarter, shifts covered.
• Scope: number of systems, teams, regions, product lines or vendors involved.
• Stakes: audit deadlines, contractual SLAs, regulatory windows, peak-season volume.

Estimate carefully, then round down

Reconstruct from what you remember: five tickets a day across four days is roughly twenty a week, so write '20+'. Rounding down and using a plus sign keeps you defensible if someone asks you to walk through the math in an interview — and occasionally they will.

A number you can explain calmly under questioning is worth more than a bigger number you cannot.

Rewrite examples

• Before: 'Handled customer emails.' After: 'Managed a shared inbox averaging 60+ customer emails weekly with same-day first response.'
• Before: 'Helped with onboarding.' After: 'Onboarded 12 new hires across three teams, building the checklist still used today.'
• Before: 'Maintained servers.' After: 'Maintained 30 Windows servers across two sites, including monthly patch cycles during a fixed weekend window.'

When there is genuinely nothing to count

Describe the before-and-after state instead. 'Replaced a manual spreadsheet handoff with a shared tracker, ending the weekly reconciliation meeting' contains no digits and still shows impact clearly.

The line you do not cross

Never invent a percentage improvement. Fabricated metrics are the single easiest thing to expose in a structured interview, because the follow-up is always 'how did you measure that?'