How to Write Resume Bullet Points That Get Interviews

Most resumes don't fail because of formatting. They fail because the bullet points describe a job instead of a person doing it well. "Responsible for managing social media accounts" tells a reader what the job was. It doesn't tell them whether you were any good at it, and that's the only thing they're trying to figure out.

A recruiter skims a resume in well under a minute on the first pass. Your bullets are the part they actually read, so each one has to earn its line.

The formula: action, scope, result

A strong bullet answers three questions in one sentence:

1. What did you do? Start with a specific verb: built, negotiated, cut, launched, rewrote, trained.
2. How big was it? Give the scope: how many users, accounts, dollars, people, sites, or patients.
3. What changed because of it? The result, ideally with a number: time saved, revenue added, errors removed.

Here's the difference in practice:

• Weak: "Responsible for onboarding new customers."
• Strong: "Rebuilt onboarding for 120 mid-market accounts, cutting time-to-first-value from 41 to 18 days."

The strong version is longer, but every extra word carries information. A reader now knows the size of your book, that you changed a process rather than just running it, and that the change worked.

Start with the verb, not with "Responsible for"

"Responsible for", "Helped with", and "Worked on" are the three most common bullet openers, and all three hide what you did. Replace them with the verb that describes your actual contribution:

• You were in charge of it: led, ran, owned, directed
• You made something new: built, designed, launched, wrote, created
• You made something better: cut, reduced, streamlined, rebuilt, automated
• You grew something: grew, expanded, increased, won, recruited
• You persuaded people: negotiated, secured, convinced, pitched

Be honest about the verb. If you contributed to a launch someone else led, "Built the reporting module for the 2025 launch" is both truthful and stronger than "Helped launch the product."

How to find numbers when you think you don't have any

Plenty of people say their job "isn't numbers-driven." Almost every job has quantities hiding in it. Ask yourself:

• How many? Customers served, tickets closed, students taught, beds covered, events run, campaigns shipped.
• How much? Budget managed, revenue influenced, inventory value, contract size.
• How often? Daily, weekly, per shift, per quarter.
• How fast? Turnaround time before and after, time to hire, time to close.
• Compared to what? Rank on the team, percentage above target, improvement over last year.

Approximate numbers are fine as long as they're honest and you can explain them in an interview. "About 40 support tickets a month" is better than no number, and far better than an inflated one you can't defend.

Before and after: five rewrites

Sales: "Managed a territory and met with clients." Becomes: "Grew a 9-state territory from $4.1M to $6.3M in annual revenue in two years, ranking #2 of 14 reps." See how a full page of this reads in the sales manager resume example.

Engineering: "Worked on improving API performance." Becomes: "Rewrote the authorization service in Go, cutting p99 latency from 480 ms to 95 ms." The software engineer example uses this pattern throughout.

Operations: "Oversaw warehouse staff." Becomes: "Ran a 140-person, three-shift fulfillment center; raised on-time shipping from 91% to 98.6% while cutting overtime by 22%." Compare the operations manager example.

Customer success: "Handled renewals." Becomes: "Owned renewals for a $7.8M book; held gross retention at 96% and net retention at 114%." The customer success manager example shows how to pair retention numbers with the work behind them.

Teaching: "Taught 10th grade English." Becomes: "Taught four sections of 10th grade English (112 students); raised the share passing the state exam from 68% to 81% in two years."

How many bullets per job

A useful rule: the more recent and relevant the role, the more bullets it gets.

• Current or most recent role: 3–5 bullets
• Previous relevant roles: 2–3 bullets
• Older or less relevant roles: 1 bullet, or just the title line

If you're struggling to fit everything on a page, cut the weakest bullet from every job before you shrink the font. Our guide on resume length goes deeper on when two pages make sense.

Keep each bullet to one or two lines

A bullet that runs three lines is usually two bullets, or one bullet with filler in it. And watch for the bullet that wraps with one or two words alone on its second line: it wastes a whole line of space and looks careless. Trim a few words so it fits on one line, or add a detail so the second line is worth having. dotresume's live preview flags these dangling lines for you as you type.

What to leave out

• Duties every person in that role has. A nurse doesn't need "administered medications"; everyone reading knows that. Say what made your work better than average.
• Soft-skill claims without evidence. "Excellent communicator" is a claim. "Presented quarterly results to the executive team" is evidence.
• Jargon only your old company used. Internal project names mean nothing to an outside reader unless you explain what the project was.
• Every tool you've touched. Put tools in a skills section and mention them in bullets only when the tool was central to the result.

Tailor the top bullets, not the whole resume

You don't need to rewrite your resume for every application. Reorder bullets so the ones most relevant to the job description come first under each role, and adjust your skills list. That takes ten minutes and does most of the work a full rewrite would.

If you keep your resume in dotresume, you can make that change in the editor and download a fresh PDF in seconds. It's free, with no account required, and an AI agent can do the reordering for you through the agent API.