How to write resume bullet points that survive a seven-second scan
A repeatable structure for turning job duties into evidence, with before-and-after examples and the three habits that make bullets forgettable.
Updated 2026-08-04 · 5 min read
The first read of your resume is not a read. It is a scan, somewhere between six and ten seconds, and it is looking for a reason to keep going. Bullet points are where that decision gets made, because they are the only part of the document that describes what you actually did.
Most bullets fail the scan for the same three reasons. They describe the job rather than the person doing it. They stack adjectives instead of evidence. And they bury the interesting part at the end of a forty-word sentence.
The structure that works
Every strong bullet answers three questions in this order:
- What did you do? An action verb, first word.
- How, or on what? Enough specifics to make it real.
- So what? The outcome, ideally with a number.
That is it. No formula acronym to memorise, just those three in that order, because the order matches how someone scanning reads — left to right, giving up early.
Here is the same piece of work written badly and then written well.
Before: Responsible for the weekly reporting process for the customer portal, working with various stakeholders to ensure accurate and timely delivery of reports.
After: Rebuilt weekly reporting for a 1.2M-user customer portal, replacing six hand-maintained spreadsheets with one Looker model and cutting turnaround from three days to two hours.
Same job. The first version tells you a role existed. The second tells you what changed because this person held it. It is also shorter to read despite being denser, because there are no words doing nothing.
Start with a verb, and make it a real one
The first word of the bullet is the most-scanned position on the line. Spending it on "Responsible for" or "Assisted with" or "Tasked with" wastes it, and all three signal that you occupied a seat rather than moved something.
Use the verb that describes what you specifically did: built, rebuilt, launched, migrated, automated, cut, negotiated, closed, mentored, restructured, consolidated, diagnosed, rewrote.
Two cautions. Do not reach for a grander verb than the truth supports — "spearheaded" for a task you helped with reads as inflation, and an interviewer will find the seam in about one question. And do not use the same verb five times in one job; vary it or the section turns into wallpaper.
Numbers, and what to do when you have none
A figure does two things: it makes the claim checkable, and it gives the reader a sense of scale they cannot get from adjectives. "Significantly improved" could mean anything. "Cut from three days to two hours" cannot.
Aim for a number in at least half your bullets. They do not all have to be percentages. Useful quantities include:
- Scale: users, accounts, records, dollars, stores, tickets, headcount
- Rate: per week, per quarter, tests run, releases shipped
- Change: from X to Y, up N%, down N%
- Time: turnaround, cycle time, hours saved
If you genuinely do not have metrics — common in early-career roles, and in jobs where you never had access to the dashboard — you have three honest options.
Reconstruct the scale. You may not know the revenue impact, but you know how many stores were in your district and how many hours a week the report took. Both are numbers.
Use a before-and-after in words. "Replaced a manual reconciliation with a scheduled job, so the month-end close stopped slipping past the third business day" has no percentage and is still concrete.
Name the artefact. "Wrote the analytics style guide the team still uses" is evidence, because something you made outlived your involvement.
What you should not do is invent a plausible-sounding percentage. Made-up numbers are the single easiest thing to catch in an interview, because the follow-up question is always "how did you measure that?"
Length: one line, two at most
A bullet that wraps to three lines is a paragraph wearing a dot, and it gets skipped. Somewhere around thirty-two words it stops being scannable.
When a bullet runs long, it is usually because it is carrying two accomplishments. Split it. Two tight bullets read faster than one long one and give you two chances to land a hit.
Cut these on sight: various, multiple, numerous, several, successfully, effectively, efficiently, in order to, utilised, leveraged, spearheaded, results-driven, detail-oriented. None of them survive the "would I say this out loud" test.
How many bullets per job
Weight by relevance, not by recency alone.
- Current or most recent role: four to six bullets
- Previous role: three to four
- Anything older than about ten years, or unrelated: one or two, or just the title and dates
If a job has nothing to do with the one you are applying for, it does not need bullets at all. The line exists to explain the dates.
Tailoring without rewriting everything
You do not need a fresh resume per application. You need the top third to match.
Reorder so the most relevant role and its most relevant bullets appear first, and adjust the vocabulary of two or three bullets to use the posting's own words. If the posting says "experimentation" and your bullet says "A/B testing", say experimentation — parsers and the recruiters searching the database both match on strings, not synonyms.
That is a ten-minute edit, and it is most of the value of a fully rewritten resume.
Paste both documents into our ATS keyword checker and it will show you which of the posting's terms are missing from your text, so you know which two or three bullets are worth touching.
A worked example
Take a fairly ordinary support job and run it through the structure.
Raw material: I worked on the support team. We had a lot of tickets about billing. I made a help article and the tickets went down.
Now with action, specifics, and outcome:
Bullet: Traced a third of inbound tickets to one unclear billing screen, wrote the help article and in-product tooltip that replaced it, and cut billing-related tickets 31% over the following quarter.
Nothing was invented. The raw material already contained the diagnosis, the artefact, and the result — it just was not organised so a scanner could find them in that order.
That is usually the case. Most people's bullets are not weak because the work was weak. They are weak because the work got described the way it appeared in a job description rather than the way it actually happened.