Why most bullets describe duties, how to find a result when you have no metrics, how long a bullet should be, and the editing pass that fixes a resume.
Pull up your resume and read the first bullet under your current job. There is a good chance it starts with "Responsible for", describes something you were assigned rather than something you did, and would be equally true of the four other people who have held that title.
This is not carelessness. It happens because the material most people reach for when writing a resume is the job description they were given when they started. That document describes a role. Your resume needs to describe a person doing it — and those are different things.
The distinction, precisely
A duty is what the job involved. An accomplishment is what changed because you were the one doing it.
Almost every weak bullet is a duty in disguise, and the tell is that you could have written it on your first day.
"Responsible for writing Python code and fixing bugs in the backend services."
"Traced a memory leak that had been causing weekly restarts for eight months; the fix cut average API response from 420ms to 95ms and stopped the on-call pages."
The underlying pattern is: there was a situation, you did something, something changed. You do not need to name a framework, and you should not force every bullet into an identical shape. But the third part — what changed — is the part that is missing from most resumes, and adding it is the single highest-return edit available.
Finding the result when you think there isn't one
The most common objection is that the work simply did not produce numbers. Sometimes true. Usually it means the numbers are there and are not the kind people expect.
Scale. How many, how big, for how many people. "Sole administrator for a 12-person practice" is a real measure of a job.
Frequency. How often, and at what cadence. "Roughly 40 requests a week with no ticketing system" tells a reader about volume and about working without infrastructure.
Duration. How long it took, or how long it lasted. "Held the rota together through a six-month vacancy" is an outcome.
Before and after, without percentages. "We were doing it in a shared spreadsheet that broke whenever two people edited it; I moved it to a proper form and the arguments stopped." That is a result, stated in plain terms, and it is more credible than a fabricated 30%.
Comparison. "First time the department had closed the month on time in two years."
Covered reception, diary and billing for a five-partner clinic single-handed for four months during a vacancy, with no missed appointments and no backlog at handover.
Rebuilt the shift handover from a verbal briefing to a written log after a near-miss; incidents attributed to handover dropped to zero over the following year.
Neither of those contains a percentage. Both describe someone competent.
On estimating
If you know a number approximately, use it and say so. "Roughly 40 a week", "around 200 accounts", "about half". Hedged estimates are honest and read as such.
What does not work is precision you cannot support. "Increased efficiency by 34%" invites the question how was that measured, and if the answer is that you made it up, the interview goes badly from there. Every number on your resume is a question you have agreed to answer.
Length, order, and count
One line per bullet, two at the outside. Anything that wraps onto a third line has become a paragraph and will be skipped. The discipline of fitting a result into a line also forces out the padding — "in order to", "was able to", "with a focus on".
Strongest first. Readers do not finish lists. Whatever is most relevant to the job you are applying for goes at the top of the role, regardless of chronology within it.
Four to six bullets for your current role, three to four for the previous one, two or three for anything five to ten years old, and a single line for older roles. Treat the total as a budget: if your most recent job is the least relevant one, it does not automatically get the most space.
Verbs
Start each bullet with something that describes a decision or an action you took. Not "responsible for", which describes proximity to work. Not "helped with", which volunteers that someone else did it. Not "worked on", which is nearly contentless.
Two failure modes on the other side, though, which most advice ignores.
The first is the thesaurus problem. Lists of "power verbs" have circulated so widely that words like spearheaded, orchestrated, leveraged and championed now read as resume-language rather than description. They signal that someone consulted a list.
The second is verb inflation — using a word that overstates your role. If you were one of six people on a project, "led" is a claim someone can check with a reference. "Built the reporting layer" is more specific, more defensible, and more impressive than a leadership claim that does not survive scrutiny.
The plain words are usually the right ones: built, ran, cut, rewrote, negotiated, closed, hired, fixed, shipped, recovered, consolidated, replaced. Do not repeat the same verb twice inside one role.
Three rewrites
Marketing. Managed social media accounts and ran ad campaigns. → Ran paid social on a £45K quarterly budget across LinkedIn and Meta; moved spend off Meta after three months when cost per qualified lead there stayed double LinkedIn's, which brought blended CPL down by £18.
The rewrite includes a decision and its reasoning. The original describes a job that exists at every company.
Operations. Handled inventory ordering and vendor contracts. → Renegotiated terms with eight suppliers during a shortage, holding volume discounts at 14% when two competitors were paying spot prices; saved roughly £85K over the year.
Note the context — during a shortage — which converts a routine task into a demonstration of leverage.
Support. Answered customer tickets and escalated issues. → Took the escalation queue from a 3-day median response to same-day by triaging on first contact instead of round-robin assignment; the change stuck after I left.
"The change stuck after I left" is a claim about durability that no metric captures, and it is the kind of thing hiring managers notice.
The editing pass
Twenty minutes, once, over the whole resume.
- Read only the first two words of every bullet. Every "Responsible for", "Helped with", "Worked on", "Assisted in" and "Tasked with" gets rewritten.
- Find the bullets with no outcome. Add what changed, or cut the bullet — a resume with six strong bullets beats one with fourteen where eight are duties.
- Check for repetition. The same verb twice in a role, or the same achievement described under two employers.
- Cut every bullet that wraps to a third line. Usually two things have been jammed together; either split them or drop the weaker half.
- Read the whole thing aloud. Every sentence you stumble over is one a stranger will stumble over too.
That pass alone typically removes a quarter of the text and improves the document, because what it removes is the part that was describing a job rather than a person.
Once the bullets are right, most other resume decisions get easier — the summary writes itself from your three strongest lines, and the skills section becomes a shortlist of things you have already demonstrated. Our complete resume writing guide covers how the rest of the page fits around them.
Land more interviews with ATS-optimized resume tools
Rewrite Your BulletsFrequently Asked Questions
How many bullet points should each job have?
Four to six for your current and most recent role, three to four for the one before, two or three for anything five to ten years back, and a single title line for older roles. Weight them by relevance to the job you want, not by recency alone.
What if my work has no measurable results?
Use scale, frequency, or duration instead — how many, how often, how long, for how many people. These are verifiable and far more concrete than adjectives. Inventing a percentage is worse than having none.
Should bullet points end with a period?
Either is fine. Consistency is what matters — pick one and apply it to every bullet in the document, including the short ones.
How long should a single bullet be?
One line, two at most. A bullet that wraps to a third line has become a paragraph, and readers scanning the page will skip it entirely.
CraftMyDocs Editorial Team
Resume & Career Experts
The CraftMyDocs editorial team writes practical, tested guidance on resumes, cover letters, ATS, and job searching — drawing on recruiter feedback and the data behind thousands of resumes built on the platform.