Guide
How to write resume bullet points
Turn duties into results: a simple formula, before-and-after examples, what to do when you don't have numbers, and how many bullets each role needs.
Rich Fayette, founder of StillSharp7 min
In this guide
The short answer
A good bullet says what changed because you were there. Start with what you did, add how big it was, and end with the result. Use a real number when you have one. When you don't, name the concrete outcome instead of reaching for a number you can't back up.
Duty: Responsible for vendor management.
Result: Renegotiated contracts with our three largest freight carriers, cutting shipping cost per order by 11%.
The first line describes a job. The second shows what you did with it.
A formula that works
Most career centers teach some version of the same pattern. Here's the one that fits experienced roles best:
Action + scope + result
- Action. What you did, in a plain verb: led, cut, built, rolled out, renegotiated, replaced.
- Scope. How big it was: the team, the budget, the sites, the customers, the volume.
- Result. What was different afterwards: money, time, errors, retention, growth, risk.
You don't need all three in every bullet. You do need the result in most of them, because that's the part a hiring manager is reading for.
Before and after
These show the pattern. The numbers in them are examples. Yours have to be your own.
Operations
Before
Managed daily warehouse operations.
After
Ran a 140-person, two-shift distribution center; cut order-to-ship time from 3 days to same day.
Finance
Before
Oversaw the monthly close process.
After
Rebuilt the month-end close, taking it from 12 days to 6 with no added headcount.
Customer success
Before
Responsible for key client relationships.
After
Owned 40 enterprise accounts worth $18M a year; kept all but two through a price increase.
Project and program management
Before
Led cross-functional projects.
After
Ran the ERP rollout across 9 sites and 600 users, live on the original date.
Notice what changed. The "after" versions aren't longer because of fancier words. They're longer because they contain facts.
When you don't have numbers
This is where most experienced people get stuck, and where a lot of resume advice goes wrong. "Quantify everything" turns into guessing, and a guessed number is worse than none: it's the first thing an interviewer asks about.
If you can't get a real figure, use one of these instead:
- Scope you know for certain. Team size, number of sites, number of accounts, the size of the budget you signed off on. You don't need a result to show the job was big.
- Before and after, in words. "Replaced a paper sign-off process with a shared approval workflow" is concrete without a percentage.
- A first or an only. "First plant in the region to pass the new safety audit with no findings." "Only manager asked to train the incoming leadership team."
- Who relied on it. "Built the weekly forecast the executive team used to set production."
- A rough count you can stand behind. "About 30 hires a year" is fine if it's true. "Roughly 50%" is not, if you're making it up.
If a number is in your bullet, you should be able to explain where it came from in one sentence.
How many bullets per role
There's no rule, but there is a pattern that works for a long career:
- Your current or most recent role: four to six bullets.
- The role before that: three to four.
- Older roles in your main section: one to three.
- Roles from early in your career: no bullets at all. A title and company in an "Earlier career" list is enough. Our guide on how far back a resume should go covers this.
Put the strongest bullet first in each role. Many readers stop after the first two.
Keep each one short
- One or two lines. If a bullet runs to three, it's probably two bullets.
- No "I," "my" or "we." Start with the verb.
- Past tense for past roles, present tense for the one you're in.
- Cut the warm-up. "Successfully," "effectively" and "proactively" add nothing a reader can check.
Phrases that weaken a bullet
- "Responsible for." It describes the job description, not you. Replace it with what you actually did.
- "Helped" or "assisted with," when you led it. Experienced people undersell this way all the time. If you ran it, say so.
- "Results-driven," "proven track record," "seasoned." Everyone writes them, so readers skip them. Show the result and let the reader draw the conclusion.
- A list of tools with no outcome. "Used Salesforce, Tableau and Excel" says what was on your screen. Say what you did with them.
The reverse matters too. Don't upgrade "helped" to "led" if you didn't lead it. A bullet has to survive a reference check.
Match the bullets to the job
The same work can be described several honest ways. Read the posting for the job you want and lead with the bullets that answer what it asks for. If it says "vendor management" and you've done it, use those words rather than "supplier relationships." Applicant tracking systems and recruiters both search for the posting's terms.
Don't add a skill you can't talk about in an interview. Matching the posting means choosing which true things to put first, not adding things that aren't true.
Show the tools you use now
If your recent bullets never mention the software you actually work in, including AI tools, a reader may assume you don't use any. One concrete line fixes that: "Built a weekly variance report in Power BI that replaced six manual spreadsheets." It doesn't need to be impressive. It needs to be current.
Check your bullets
The free ATS resume checker reads your resume against the role you want next. You get a score, the format problems that trip up tracking systems, and your top three fixes, with no signup. Add your email and it quotes the exact lines that undersell you, with three of them rewritten from your own facts. It never adds a number you didn't give it.
Check my resume, freeIf you'd rather have the whole thing done, the Resume Rebuild rewrites your resume and LinkedIn around your results, under the same rule.
Questions people ask
One or two lines. If it runs longer, split it or cut the setup and keep the result.
No. Use a number when you have a real one. When you don't, show scope or a concrete outcome. A made-up number does more harm than no number.
Four to six for your most recent role, fewer for each role before it, and none for roles from early in your career.
A duty is what the job asked of anyone in it. An accomplishment is what changed because you did it. "Managed the budget" is a duty. "Brought the department in 4% under budget two years running" is an accomplishment.
STAR (situation, task, action, result) is built for interview answers. On a resume it's too long. Keep the action and the result, add the scope, and save the full story for the interview.