How To Write Resume Achievements (With Examples)
Achievements are what make a resume persuasive. A formula for writing them, how to find numbers, what to do without them, and before-and-after examples across roles.
Key takeaways
- An achievement shows what you did and what changed; a duty only says what the job involved.
- Use the pattern: action verb + what you did + result or scope.
- Numbers help, but scope, frequency, recognition and adoption by others also make a bullet concrete.
- Every figure must be accurate and explainable; estimates should be described as approximate.
Most resumes describe jobs. Strong resumes describe what the person achieved in them. Recruiters already know what a customer support agent or a project manager does; what they want to know is how well you did it and what difference you made. This guide shows how to turn duties into achievements, with a formula and many examples.
Duties versus achievements
| Duty | Achievement |
|---|---|
| Handled customer complaints | Resolved escalated complaints for the region’s largest accounts; none of the 30 accounts I managed left during the year |
| Prepared monthly reports | Automated the monthly KPI report in Power BI, cutting preparation from two days to two hours |
| Managed the team’s social media | Grew LinkedIn followers from 3,000 to 11,000 in twelve months with a weekly publishing plan |
| Responsible for onboarding new staff | Created the onboarding checklist and training plan used for all 25 new hires last year |
The achievement versions are specific enough to be believed and specific enough for an interviewer to ask about, which is exactly what you want.
The formula
Action verb + what you did + result or scope.
- Action verb: a precise verb that says what you personally did: built, reduced, launched, negotiated, analysed, trained, redesigned.
- What you did: the task, project or problem, with the tools or methods if relevant.
- Result or scope: what changed, or how big the work was.
Some people know this as a short version of the STAR method (situation, task, action, result), which is also useful for interview answers; see the STAR method.
How to find your achievements
If you are struggling to think of any, ask yourself about each role:
- What did I improve, speed up, simplify or fix?
- What did I build, create, launch or write that is still used?
- What did I sell, save, earn or protect?
- Who did I train, help or lead?
- What was I chosen for, praised for or trusted with?
- What problems did I solve that others had not?
Look at old performance reviews, emails thanking you, project documents and reports. They often contain results you have forgotten.
Ways to quantify
Numbers make achievements concrete. Useful types include:
- Volume: tickets per day, accounts managed, products launched, articles written.
- Change: percentages or before-and-after figures for time, cost, errors, revenue or satisfaction.
- Money: budget managed, revenue generated, costs saved.
- Time: hours saved, deadlines beaten, processes shortened.
- People: team size, users, customers, trainees.
If you only know a figure approximately, say so: "about", "roughly", "more than". Never invent a number. You will be asked about it, and a reference may be asked too.
Achievements without numbers
Many valuable achievements have no figure attached. You can still make them concrete with:
- Scope: "for 40 stores", "across three countries", "for the whole engineering team".
- Frequency: "weekly", "for every new customer".
- Adoption: "now used by the whole team", "adopted as the company standard".
- Recognition: "chosen to lead", "asked to train new hires", "nominated for the annual award".
- Before and after: "replaced a manual process with an automated one".
Example: "Wrote the first internal guide to the refund process, now given to every new support hire" needs no number to be convincing.
Examples by role
Software engineering
- Reduced API response times by about 40% by adding caching and rewriting the slowest database queries.
- Led the migration of the billing service to a new payment provider with no customer-facing downtime.
Data and analytics
- Built the weekly revenue dashboard in Looker used by the leadership team every Monday.
- Identified the main cause of a churn increase through cohort analysis; the product change that followed reduced churn in the next quarter.
Sales
- Exceeded quota in seven of eight quarters, selling to mid-sized retailers.
- Opened the company’s first customers in a new region through targeted outreach.
Customer support and success
- Kept satisfaction ratings among the team’s highest while handling 60–80 conversations a day.
- Rewrote five of the most-used help articles, reducing repeat questions on the topics they covered.
Marketing
- Lowered cost per lead by redesigning the landing page and testing three offers.
- Planned and ran the launch campaign for a new product line across email, social and partners.
Operations and administration
- Redesigned the supplier invoice process, cutting late payments and saving the finance team several hours a week.
- Managed calendars and travel for three executives across four time zones.
Project management
- Delivered the CRM migration for a 200-person sales team on schedule, coordinating IT, sales operations and the vendor.
- Introduced a weekly written status update that replaced two recurring meetings.
Human resources and recruiting
- Shortened time to hire for engineering roles by restructuring the interview process with hiring managers.
- Rolled out a new onboarding programme; first-year departures fell over the following year.
Design
- Redesigned the checkout flow after usability testing with 12 customers; fewer customers abandoned at payment.
- Built the first shared component library, now used by every product team.
Common mistakes
- Vague results: "improved efficiency" says nothing. Say what improved and by roughly how much.
- Claiming team results as your own: say what you led or contributed to.
- Numbers without context: "managed 50 tickets" means little without a time frame.
- Too many numbers: a page full of percentages becomes hard to read; keep the most meaningful.
Writing tips
- Start each bullet with a different verb where you can; our list of resume action verbs helps.
- Keep bullets to one or two lines.
- Put the most impressive achievement first in each role.
- Say what you did, not what "we" did, while staying honest about team work ("led", "contributed to", "part of a team that").
- Use the employer’s terms for tools and methods where they are true.
Keep a running record
The easiest way to write achievements is to collect them as they happen. Keep a simple document where you note results, praise, finished projects and numbers each month. When you next update your resume or prepare for a review, the evidence is already there.
Next steps
Rewrite the top three bullets of each recent role using the formula, then put them into the full structure in how to write a resume and tailor them with how to tailor your resume. For personal feedback, try a CV review.