Two candidates did the same job. One writes Responsible for managing the company's social media accounts. The other writes Grew a three-channel social program from 4k to 19k followers in eight months by shifting to a weekly editorial calendar.
The work was identical. Only the second version tells a recruiter anything about scale, judgment, or outcome. That gap is what this article is about, and closing it does not require a better job — only a better description of the one you had.
Why Responsibility-Based Bullets Fall Flat
A responsibility describes what you were assigned. An achievement describes what changed because you did it. Recruiters are hiring for the second thing.
Duty-based bullets fail in three specific ways.
They are unfalsifiable. "Responsible for customer support" is true of everyone who held that title, so it distinguishes nothing.
They hide scale. Supporting five customers and supporting five hundred read identically when the number is missing, and the reader will assume the smaller one.
They omit the result. If nothing measurably changed, the reader cannot tell whether you were effective or merely present.
The fix is not louder language. Words like "spearheaded" and "leveraged" attached to a vague claim make it worse. What matters is that the sentence contains something a person could verify.
The Action–Context–Result Framework
Every strong bullet has three parts, in this order.
Action — a specific verb describing what you personally did. Not "helped with" or "was involved in", but built, negotiated, automated, redesigned, recruited.
Context — the scope or difficulty that makes the action meaningful. How many, how often, for whom, under what constraint. This is where most bullets are lost, and it is the cheapest credibility available to you.
Result — what changed. A number, a time saved, a decision enabled, an error rate reduced, an outcome adopted.
Applied to an ordinary task:
Duty:Handled onboarding for new hires.Rewrite:Redesigned onboarding for 30+ new hires across two offices, cutting time-to-first-task from nine days to four.
Not every bullet needs all three parts, but a bullet with none of them is filler. Six bullets that carry evidence outperform twelve that carry adjectives, so cut before you pad.
How to Quantify Your Impact
Numbers are persuasive because they are checkable. Most people assume they have none, then find several once they look in the right places.
Ask these of any task you performed:
- How many? Users, clients, tickets, campaigns, reports, team members.
- How often? Daily, weekly, per quarter.
- How much? Revenue, budget, hours, cost, error rate.
- How fast? Turnaround before and after your change.
- How big relative to others? Largest account, first of its kind, only person covering it.
Approximate honestly when you have to. roughly 200 tickets a month is fine. ~15% faster is fine. What you must never do is invent a figure you would have to defend in an interview — recruiters ask how the number was measured, and the answer is where fabrication collapses.
What to Do When You Have No Numbers
Plenty of real work produces no clean metric. Those bullets can still be strong.
Use a before-and-after state. Replaced a shared spreadsheet with a tracked workflow, so handoffs stopped getting lost between shifts.
Use scope as the evidence. Sole analyst supporting three regional managers during a system migration.
Use adoption. Wrote the internal style guide now used by the whole content team.
Use the decision your work enabled. Ran the vendor comparison that led to switching providers.
Use difficulty. Rebuilt the reporting pipeline in two weeks after the previous owner left mid-quarter.
Each of these gives a reader something concrete. The goal is verifiable specificity, and a number is only one way to reach it.
How to Write Student Project Bullets
Students often assume coursework does not count. It does, if you describe it like work rather than like a syllabus entry.
Treat each project as a role. What was the problem, what did you build, which tools, what happened at the end.
Weak:Completed a data analysis project using Python.Stronger:Analysed 40k transaction records in Python to identify three churn drivers, presented to a faculty panel and adopted as the course's example case study.
Be explicit about your own contribution on team projects. Owned the data cleaning and modelling for a four-person capstone is honest and more useful than implying you did everything.
Include outcomes that are not grades: something shipped, something used by others, something presented, something that placed in a competition. Avoid listing the course code — nobody outside your university knows what it means.
Before-and-After Examples
Customer service
Before:Responsible for answering customer emails.After:Handled ~200 support emails a month with a 96% satisfaction rating, and wrote the macro library the team still uses for the eight most common issues.
Marketing intern
Before:Helped with social media and content.After:Planned a weekly content calendar across three channels, coordinating two contributors and lifting average post engagement 34% over one semester.
Engineering
Before:Worked on the payments team.After:Cut checkout API latency 40% by adding caching to the three slowest endpoints, reducing timeout errors during peak hours.
Finance
Before:Assisted with monthly reporting.After:Built the reconciliation template for monthly close across four entities, reducing prep time from three days to one.
The pattern is identical every time: name the action, add the scope, finish with what changed.
Strong Action Verbs to Use
Pick verbs that describe a specific action rather than a posture.
- Built or created: built, designed, developed, launched, prototyped, wrote
- Improved: automated, streamlined, reduced, accelerated, simplified, standardised
- Owned: led, coordinated, managed, oversaw, drove
- Analysed: analysed, evaluated, forecast, investigated, modelled
- Influenced: advised, negotiated, presented, persuaded, trained
Two rules keep this from becoming decoration. Never open a bullet with "responsible for", which converts an achievement into a job description. And avoid inflated verbs for small tasks — "spearheaded a comprehensive initiative" to describe scheduling three meetings reads worse than a plain, accurate sentence.
Frequently Asked Questions
How many bullet points should each job have?
Three to five for recent and relevant roles, one or two for older ones. Relevance decides the count, not seniority.
Should every bullet have a number?
No. Aim for a number in roughly half of them. Bullets built on scope, adoption or a before-and-after state work well when no metric exists.
What if my results were a team effort?
Describe your own contribution accurately and let the team scale provide context: Led the data workstream of a six-person migration that moved 12 systems in one quarter.
Can I include a project that failed?
Yes, if you can point to what came out of it. A pilot that was cancelled but produced a decision or a reusable process still demonstrates judgment.
How long should a bullet be?
One to two lines. Anything longer stops being scannable, and the detail is better saved for the interview.
Should bullets end with a period?
Either way is fine. Consistency across the whole document is what matters.
Put It Into Practice
Strong bullets come from having your work recorded while you remember the details, not reconstructed months later under deadline. Use Vibe ID™ to capture each project's scope, tools and outcome as you go, so writing a resume becomes selecting the right evidence rather than trying to remember what actually happened.
