How do you measure value?
Every job has some way to know if you did it well. Your resume should say what you were responsible for, and then how anyone would know it went well.
Most resumes stop at the first half. "Responsible for customer service." OK... and? The second half is the part the person reading it cares about, because it's the closest thing they have to watching you work.
Don't invent the number. If you don't know it, go find it. If you can't find it, describe the size of the thing instead. A made-up 37% falls apart the first time someone asks how you measured it.
- Free resources
- 4
- Links checked
- Sept 2026
- Skip ahead
- The free stuff
The pattern
Each bullet answers three things, usually in one sentence:
- What you did. Start with the action, not "responsible for."
- How you'd know it worked. A number, a before and after, or who it helped.
- Why it mattered. Money, time, safety, people served, problems that stopped happening.
Not every bullet needs all three. But if none of your bullets have the second part, the page reads like a job description instead of a record of what you did in the job.
Walk-throughs by job
Highlighted numbers are placeholders. Put your real ones in, or leave the line out.
-
Retail sales associate
What you were responsible for
Helping customers, running the register, keeping your section stocked, opening and closing.
How you'd know it worked
- Sales per hour or average sale compared to the store
- Add-ons against goal (protection plans, store card sign-ups)
- Damaged or missing stock in your section
- Survey comments that name you
- New hires you trained
- Before
- Responsible for customer service, register and stocking.
- After
- Hit 110% of my monthly add-on goal in 8 of 12 months; trained 5 new hires on register and returns.
-
Customer support rep
What you were responsible for
Answering calls, chats or tickets, solving the problem, and knowing when to escalate.
How you'd know it worked
- Tickets or calls handled per day
- Problems solved on the first contact
- Customer satisfaction score
- Help articles or macros you wrote, and how often the team uses them
- Before
- Handled customer inquiries via phone and email.
- After
- Resolved about 45 tickets a day at a 94% satisfaction score; wrote 6 billing help articles the team now links in 30+ replies a week.
-
Nurse or CNA
What you were responsible for
Patient care, vitals, charting, and handoffs between shifts.
How you'd know it worked
- Patients per shift and the size of the unit
- Unit results you helped move (falls, pressure injuries, patient satisfaction)
- Charting audits
- New staff you precepted or trained
- Before
- Provided patient care in a busy hospital unit.
- After
- Cared for 6 to 8 patients a shift on a 32-bed med-surg unit; precepted 4 new CNAs; no charting errors across 3 quarterly audits.
-
Warehouse associate
What you were responsible for
Picking and packing orders, loading trucks, inventory counts, running equipment safely.
How you'd know it worked
- Picks or units per hour against the target
- Accuracy rate
- Safety record
- Equipment certifications
- Before
- Picked and packed orders in a fast-paced warehouse.
- After
- Averaged 120 picks an hour against a 100 target at 99.8% accuracy; 2 years with no safety incidents; forklift certified.
-
Teacher
What you were responsible for
Planning lessons, teaching, grading, and keeping families in the loop.
How you'd know it worked
- Growth on assessments compared to the year before
- Attendance or participation
- Something you started, and how many students used it
- How many students and sections you taught
- Before
- Taught 7th grade math.
- After
- Taught 5 sections of 7th grade math (140 students); 68% met spring growth targets, up from 52%; started a weekly tutoring hour 25 students used.
-
Administrative assistant
What you were responsible for
Calendars, travel, records, the front desk, and keeping an office running.
How you'd know it worked
- How many people you supported
- Turnaround time on requests
- A process you fixed, and the time it saved
- Budgets or accounts you managed
- Before
- Managed calendars and scheduling for the office.
- After
- Ran calendars and travel for 4 executives; moved expense reports to a shared tracker, cutting turnaround from 2 weeks to 3 days.
-
Software engineer
What you were responsible for
Building features, fixing bugs, reviewing code, taking your turn on call.
How you'd know it worked
- What the feature changed for users (adoption, conversion, time saved)
- Speed or cost (load time, server spend)
- Reliability (incidents, uptime)
- How many people use what you built
- Before
- Worked on the checkout team using React and Node.
- After
- Rebuilt the payment step of checkout, cutting load time from 3.1s to 1.2s; conversion rose 4% the quarter after launch.
-
Project manager
What you were responsible for
Plans, timelines, getting people to agree, and catching problems before they land.
How you'd know it worked
- On time and on budget, or how far off and why
- Size of the work (people, sites, dollars)
- Risks you caught early
- What the project changed once it shipped
- Before
- Managed cross-functional projects.
- After
- Led a 9-month rollout of a new scheduling system across 12 clinics, on budget, with no days of downtime.
Where to find your numbers
- Performance reviews and the goals you were measured against
- Team dashboards, weekly reports, sales or ticket systems
- Emails or messages where someone thanked you for something specific
- What it looked like when you started compared to when you left
- Counts: people, orders, tickets, students, patients, projects, per day or per week
- Time: how long something took before and after you touched it
- Money: what you sold, saved, or managed
- Things that went down: errors, complaints, returns, overtime, injuries
If you still work there, pull the numbers now. It is a lot harder after you leave.
When there's no number
Some work doesn't come with a dashboard. That's fine. Use one of these instead:
- Scale: "for a 40-bed unit," "across 3 locations," "for a team of 12"
- Frequency: "every closing shift," "weekly," "for every new hire"
- Comparison: "the go-to person for returns on second shift"
- What stopped happening: "no missed deliveries after the new check-in process"
- Who asked for you: "requested by name to train new staff"
If you'd have to guess, only write "about" when you'd be comfortable explaining how you got there.
See it on a real one
For what it's worth, my own resume tries to do this on every line: what I was responsible for, then what changed. It's not a template. It's just one example of the pattern.
The free stuff
Start here3
-
My Next Move
Look up your job and see the tasks it usually involves. Handy when you can't remember everything you were responsible for.
-
Occupational Outlook Handbook
The "What they do" tab for each job lists the typical duties. Use it as a checklist, then add how you know you did them well.
-
MIT's resume guide
Sample resumes and lists of action verbs, for starting each bullet with what you did.
Good, with a catch1
-
Harvard's resume templates
A clean, single-column template to put your new bullets into.
The catch: It gives you the layout, not the words. The words are the part on this page.
Questions people ask
What if my job has no numbers?
Use scale, frequency, comparison, or what stopped happening. "Trained every new hire on second shift" is specific without a single percentage.
Can I estimate a number on my resume?
Only if you could explain how you got it. "About 40 calls a day" is fine if that was a normal day. A number you made up to sound impressive will not survive the interview.
What's the difference between a duty and an accomplishment?
A duty is what the job asked you to do. An accomplishment is how you know you did it well, or what changed because you did it.
Does every bullet need a number?
No. Aim for most of your recent bullets to say how you know it worked. A few plain duty lines are fine for context.