How to Quantify Your Achievements on a Resume, With Examples
A resume bullet point without a number is just a job description. Hiring managers do not want to know what you were supposed to do; they want to know how well you did it. But many professionals, especially outside of sales and finance, struggle to attach metrics to their work. Here is how to find the numbers in any role, with over 30 examples across different industries.
Read these two resume bullet points:
"Responsible for managing the company's social media accounts and creating content."
"Grew Instagram following by 45% (to 12k) and increased average engagement rate from 2% to 5.5% over six months by redesigning the content strategy."
The first bullet describes a duty. The second describes an impact. The difference between a resume that gets ignored and one that gets interviews is almost entirely the shift from describing duties to quantifying impact.
Many candidates assume that because they do not carry a sales quota or manage a budget, they have nothing to quantify. This is false. Every job exists to save time, save money, make money, or improve quality. All of those can be measured.
The Three Types of Resume Metrics
When you are struggling to quantify an achievement, look for one of these three categories:
1. Scale and Scope (How much?)
If you cannot measure the outcome, measure the size of the responsibility. How many people did you manage? How large was the budget? How many clients did you support? How many tickets did you resolve?
2. Time and Efficiency (How fast?)
Did you make a process faster? Did you hit a tight deadline? How many hours per week did your improvement save the team?
3. Business Impact (How much better?)
This is the gold standard. Revenue generated, costs reduced, retention improved, errors decreased, satisfaction scores raised.
The Formula: Action + Context + Result
A strong bullet point usually follows a specific structure: an action verb, the context of the work, and the quantified result. Sometimes the result comes first for emphasis.
"Reduced server costs by 22% (Result) by auditing and migrating legacy infrastructure (Action) across 3 data centers (Context)."
Examples of Quantified Achievements by Function
Marketing & Content
Weak: Wrote articles for the company blog.
Strong: Authored 45+ SEO-optimised articles, driving a 30% increase in organic blog traffic and generating 120+ qualified leads per quarter.
Weak: Managed email marketing campaigns.
Strong: Redesigned the onboarding email sequence, increasing open rates from 18% to 34% and improving trial-to-paid conversion by 12%.
Weak: Ran paid social media ads.
Strong: Managed a $50k/month ad budget across LinkedIn and Facebook, reducing Customer Acquisition Cost (CAC) by 15% over six months.
Software Engineering & IT
Weak: Improved application performance.
Strong: Refactored the core data processing pipeline, reducing average query latency by 400ms and cutting server load by 25%.
Weak: Fixed bugs and handled support tickets.
Strong: Resolved 150+ Tier 3 technical escalations with a 98% SLA compliance rate, reducing average time-to-resolution by 4 hours.
Weak: Built new features for the app.
Strong: Led a team of 3 engineers to deliver the new reporting dashboard 2 weeks ahead of schedule, resulting in adoption by 80% of enterprise users.
Operations & Project Management
Weak: Managed cross-functional projects.
Strong: Directed 5 concurrent product launches involving 20+ stakeholders across engineering, marketing, and sales, all delivered on time and under the $200k budget.
Weak: Improved the onboarding process.
Strong: Standardised the new-client onboarding workflow, reducing average setup time from 14 days to 5 days while improving client satisfaction scores to 4.8/5.
Weak: Handled vendor relationships.
Strong: Renegotiated contracts with 4 primary software vendors, securing $45,000 in annual cost savings without reducing service levels.
Customer Success & Support
Weak: Supported enterprise clients.
Strong: Managed a portfolio of 35 enterprise accounts worth $2.4M in ARR, maintaining a 96% net retention rate over two years.
Weak: Answered customer queries.
Strong: Handled an average of 60+ inbound customer tickets daily, maintaining a 99% CSAT score and a first-response time under 15 minutes.
Weak: Trained clients on the software.
Strong: Conducted 100+ training webinars for new users, directly contributing to a 20% decrease in basic support tickets within the first 30 days of implementation.
Human Resources & Recruiting
Weak: Hired new employees.
Strong: Sourced and hired 45 technical roles in 12 months, reducing average time-to-fill from 60 days to 42 days while lowering agency spend by 30%.
Weak: Improved employee retention.
Strong: Designed and implemented a new mentorship program adopted by 120 employees, correlating with a 15% reduction in first-year turnover.
Weak: Handled payroll and benefits.
Strong: Managed payroll processing for 250+ employees across 3 states with 100% accuracy, and led the annual benefits enrollment process achieving 98% participation.
Administrative & Office Management
Weak: Managed the executive's calendar.
Strong: Optimised calendar management for the CEO and COO, recovering approximately 10 hours per week of executive time by implementing strict meeting criteria and delegation workflows.
Weak: Organised company events.
Strong: Planned and executed the annual company offsite for 150 employees, managing a $40k budget and negotiating a 15% discount on venue costs.
Weak: Handled office supplies and expenses.
Strong: Audited office supply procurement, switching to a consolidated vendor model that reduced monthly administrative expenses by 22%.
What If I Don't Have the Exact Numbers?
You will not always have access to the exact data, especially for jobs you left years ago. In these cases, estimating is acceptable as long as you are honest and conservative.
Use words like approximately, roughly, up to, or average.
"Managed a team of approximately 15 contractors" is better than "Managed a team." "Reduced report generation time by roughly 50% (from 4 hours to 2 hours)" is perfectly acceptable even if you don't have the exact time logs to prove it was exactly 50%.
If you genuinely cannot estimate a result, focus entirely on the scope. How big was the project? How many people were involved? How large was the dataset? Scope provides context when results are unavailable.
The Rule of Three
Aim for at least three quantified bullet points for your most recent roles. Not every single line needs a number—sometimes a bullet point exists simply to show you possess a specific technical skill. But if a recruiter scans your resume and sees no numbers, percentages, or dollar signs, they see a list of responsibilities, not a track record of success.
Lyrra's AI Resume Builder includes specific functionality to help quantify achievements. It analyses your bullet points, identifies statements that describe duties rather than impact, and suggests ways to rewrite them with metrics, scope, and stronger action verbs.
Related articles
How to List Skills on a Resume: Examples and Tips
Learn how to list skills on a resume by selecting relevant, specific capabilities, grouping them clearly, and supporting important claims with evidence.
How to Write a Cover Letter With No Experience
Learn how to write a cover letter with no experience by turning projects, education, volunteering, and everyday responsibilities into relevant evidence.