Generic bullet points like 'worked on backend systems' or 'improved application performance' appear on thousands of CVs. Hiring managers spend an average of six to eight seconds scanning each application — and vague statements like these don't make the cut. Quantified achievements, on the other hand, instantly signal impact and make you stand out from candidates with identical job titles. This guide shows you exactly how to quantify your work, even when the numbers aren't obvious.

Why Numbers on a Technical CV Matter

Recruiters and hiring managers process hundreds of CVs, especially for competitive roles at tech companies. Numbers do three things generic bullets can't:

They prove impact, not just activity
They give context that makes your contribution legible to non-technical stakeholders (HR, hiring managers outside engineering)
They anchor your experience in real-world scale — 'optimised a query' lands differently than 'reduced query time by 65%, saving 12 server hours per day'

Even if you never tracked metrics explicitly, you can reconstruct meaningful numbers from what you know about your work.

The Formula: Action + Number + Context

Almost every quantified achievement follows the same structure:

[What you did] + [by how much / how many] + [with what result or context]

Examples:

Refactored the authentication module, reducing login time from 4.2s to 0.8s for 80,000 active users
Built a CI/CD pipeline that cut deployment time from 45 minutes to under 6 minutes, enabling daily releases
Wrote 200+ unit tests that increased code coverage from 34% to 89% and eliminated a class of production bugs

If you don't have all three elements, two is enough. The number alone is far stronger than no number at all.

How to Find Numbers You Think You Don't Have

Many engineers assume they can't quantify their work because they didn't track metrics at the time. Here's how to reconstruct meaningful figures:

Team and codebase size: 'Contributed to a codebase serving 2 million users' or 'Part of a 12-engineer team' adds instant scale.

Time saved: Think about processes you automated or sped up. Even an estimate is valid: 'Automated weekly reporting, saving the data team approximately 4 hours per week.'

Error rates and reliability: Did a bug fix or refactor reduce incidents? 'Resolved a race condition that had caused 3-4 on-call alerts per week — zero recurrences over the following 6 months.'

Volume of work: 'Reviewed and merged 300+ pull requests across 2 years', 'Shipped 14 features across 3 product cycles', 'Onboarded 8 junior engineers to the codebase.'

Business metrics (if you have access): Conversion rates, revenue impact, latency improvements that directly affect user retention — these are gold. 'A 200ms reduction in page load time contributed to a 12% uplift in checkout completions (per A/B test).'

If you genuinely have no numbers, use relative language: 'significantly reduced' or 'cut in half' is still better than nothing, and you can follow up with specifics in an interview.

Real Examples Across Different Technical Roles

Software Engineer

Weak: Worked on the payments API

Strong: Redesigned the payments API to handle peak loads of 5,000 requests per second, reducing timeout errors by 94% during Black Friday traffic

Weak: Improved test coverage

Strong: Increased unit test coverage from 28% to 81% across the core transaction service, reducing post-deployment hotfixes from ~6 per month to under 1

Data Scientist / ML Engineer

Weak: Built a recommendation model

Strong: Developed a collaborative filtering recommendation model that increased average session length by 18% and contributed to a 9% lift in monthly subscriptions

Weak: Cleaned and processed data

Strong: Automated data cleaning pipeline for 40+ GB of daily ingested records, reducing preprocessing time from 6 hours to 22 minutes

DevOps / Platform Engineer

Weak: Set up Kubernetes clusters

Strong: Migrated 30 microservices from EC2 to Kubernetes, cutting infrastructure spend by £18,000/month and improving deployment frequency from weekly to daily

Weak: Monitored system performance

Strong: Built observability dashboard in Grafana covering 15 services; identified and resolved a memory leak that had caused 2-3 weekly incidents across 6 months

Frontend Engineer / Designer

Weak: Improved page performance

Strong: Optimised Core Web Vitals on the product landing page, improving LCP from 5.1s to 1.8s and increasing organic traffic by 23% over 90 days

Weak: Built UI components

Strong: Designed and shipped a component library of 40+ reusable React components, adopted by 3 product teams and reducing front-end build time by an estimated 30%

Common Mistakes to Avoid

Using the same number for everything. If every bullet claims a '30% improvement', it reads as fabricated. Vary your metrics and be specific where possible.

Claiming credit for team efforts without context. Be honest about your role: 'As the lead engineer on a 4-person team, delivered a real-time chat feature used by 60,000 users per month' is accurate and still impactful.

Inflating numbers without evidence. You may be asked to walk through your numbers in an interview. Only use figures you can defend and explain. Estimates are fine — just know your reasoning.

Only quantifying your biggest projects. Small wins count. A script that saved your team two hours a week, over a year, saved 100 hours. That's worth writing down.

How to Add Numbers When You're Just Starting Out

If you're a recent graduate, bootcamp graduate, or self-taught developer, you might feel you have nothing to quantify. You do:

Academic or personal projects: 'Built a full-stack e-commerce app with 500+ product listings and a custom recommendation engine'
Open source: 'Contributed 8 pull requests to an open-source project with 12,000+ GitHub stars'
Hackathon: 'Placed 2nd out of 47 teams at HackManchester 2024'
Learning pace: 'Completed a 12-week bootcamp while working 20 hours per week part-time'

These numbers demonstrate initiative, scope, and productivity — all things employers care about.

Conclusion

Quantifying your achievements isn't about inventing impressive-sounding figures. It's about translating your real work into language that hiring managers, regardless of technical background, can quickly understand and evaluate. Start with what you know: team size, users served, time saved, coverage improved. Then apply the formula: action + number + result. Even one or two strong, specific bullets per role can transform a forgettable CV into one that earns a call back.