A recruiter does not read your resume. She scans it — about six seconds per pass — and her eyes stop on verbs and numbers. "Managed inventory for the warehouse" tells her nothing she can compare. "Reorganized warehouse inventory control, cutting stockouts to zero and trimming holding costs" tells her what you changed and by how much. Same job, same effort, completely different signal.
This is the single highest-leverage rewrite on a resume: turning duty bullets into result bullets. It takes no new experience. It just asks one question of every line: so what?
The formula: action + work + number + impact
Every strong bullet has four parts, in this order:
Strong verb + what you worked on + a number + why it mattered
- Strong verb: what you did, precisely. Built, cut, automated, negotiated.
- The work: the system, process, or project you touched.
- The number: volume, percentage, time, money, people. Anything measured.
- The impact: what the number means for the business — faster, cheaper, bigger, calmer.
You do not need all four in every bullet. Verb + work + one of number or impact is enough for a one-liner. The point is that no bullet should be just a verb and a duty.
Before and after: four rewrites
The pattern is easier to see than to describe. Here are four real-shaped rewrites:
Before: "Responsible for answering customer support tickets."
After: "Resolved 40+ support tickets per week with a 96% satisfaction score, clearing the oldest backlog in the team."
Before: "Managed inventory for the warehouse."
After: "Reorganized the inventory tracking spreadsheet used by 8 staff, reducing stock-count errors from weekly to rare."
Before: "Worked on the reporting module."
After: "Built the weekly reporting pipeline that cut manual report prep from 6 hours to 20 minutes for a team of 12."
Before: "Helped the marketing team with social media."
After: "Drafted and scheduled 30+ social posts in 8 weeks; two became the account's highest-engagement posts of the quarter."
Notice what changed in each: a vague verb became a specific one, a number appeared, and the line ends with an outcome. That is the whole method.
Where to find numbers when you think you have none
Most people who say "my job had no numbers" are thinking of revenue. Numbers live in more places than revenue:
- Time: hours saved per week, turnaround cut from 3 days to 1.
- Volume: tickets, orders, customers, files, lines reviewed.
- Error rate: defects found, complaints reduced, audits passed.
- People: team size, trainees onboarded, stakeholders coordinated.
- Deadlines: shipped 2 weeks early, on call every third week.
- Before/after: you do not need a dashboard — "went from daily firefighting to one calm check-in per week" is a measurement.
Pull out old performance reviews, sprint boards, shift schedules, and dashboards. The numbers are usually sitting in something you already wrote.
The honest-numbers rule
Conservative estimates are fine. Saying "roughly 15%" when you saw the number move from 60 to 69 is honest. What is not fine is inventing numbers, rounding yourself into a promotion you did not earn, or taking credit for a team's result as if you did it alone. Two reasons.
First, the interview. Every number on your resume is a question waiting to happen — "how did you measure that?" — and a story you cannot back up will not survive the interview. Second, the reference. Hiring managers compare your claims against what your former manager says. The rule I use: every number on the page should be one I can defend in a five-minute conversation.
When the work genuinely had no output to measure
Some work is real but unmeasurable. Measure the input or the context instead:
- Scale: "Processed expense reports for a 60-person office."
- Stakes: "The only tester covering the checkout flow before launch."
- Difficulty: "Migrated the archive without downtime during peak season."
One measurable detail — scale, stakes, or difficulty — lifts a bullet as much as a percentage does. It is still a fact, just a different kind of fact.
Verbs: specific, varied, mirrored
Start every bullet with a verb, and make it the most specific true verb available. "Led" beats "responsible for." "Automated" beats "worked on." Vary them down the page — ten bullets starting with "managed" reads like one bullet.
And here is the part that connects to getting found: mirror the posting's verbs. If the job description says "architected" and "deployed," and you did that work, use those exact words in your bullets. Applicant tracking systems score keyword overlap, and the recruiter pattern-matches the same way. This is not keyword stuffing — it is saying the same true thing in the employer's own words.
Formatting rules that protect the work
- One bullet, one line. If it runs past two lines, cut the middle, not the number.
- Strongest first. Many readers only get through the first two bullets under each role.
- No pronouns. "Resolved 40+ tickets" — the "I" is implied and the line scans faster.
- Numbers near the front. They are the visual anchor in a six-second skim; do not bury them at the end of the sentence.
- Keep the format plain. Standard bullet characters, no graphics — the parser reads plain text, and fancy formatting is where resumes get silently mangled.
Rewriting takes about twenty minutes per role. Do the duty-to-result pass first, then the verb pass, then read each bullet once asking "could I defend this number for five minutes?" If the answer is yes, it stays. Tailoring the same bullets to each posting's keywords is the next pass — it is a separate, smaller job once the bullets themselves are true and quantified.