How to write resume bullet points that get read

Recruiters don't read resumes. They scan them. Eye-tracking studies keep landing on the same number: about seven seconds for the first pass. In those seven seconds, your bullet points are pretty much all that gets seen. Not your carefully chosen font. Not your summary. The bullets.

And most bullets waste the opportunity. I've reviewed hundreds of resumes, and the same failure shows up on nearly all of them: bullets that describe the job instead of the person. "Responsible for managing social media accounts." Sure. So was everyone else who ever held that title, including the ones who got fired.

This guide gives you a formula that works, a stack of before and after rewrites, and honest answers for the awkward cases: no numbers, boring job, career gap role you'd rather not talk about.

The formula: result, scale, method

Put the outcome first. Then show how big the job was. Then say how you did it.

Result first, because that's where the eyes land. Scale second, because a hiring manager can't judge "grew sales" without knowing if you managed three accounts or three hundred. Method last, because by then they already care.

Compare:

Before: "Responsible for email marketing campaigns and newsletter management."

After: "Grew newsletter revenue 34% in one year (from $210K to $282K) by rebuilding the welcome sequence and cutting send frequency in half."

The second version answers the three questions every screener is silently asking: did it work, how big was it, and was it you or luck?

A few more, across different jobs:

Before: "Handled customer support tickets and escalations."

After: "Resolved 40+ tickets daily at a 96% satisfaction score, and cut escalations 22% by writing macros the whole 12-person team adopted."

Before: "Assisted with month-end close process."

After: "Cut month-end close from 9 days to 6 by automating 14 recurring journal entries in NetSuite."

Before: "Taught 5th grade math and science."

After: "Raised state math test pass rates from 61% to 78% in two years for a class of 28, using small-group rotations I later trained three other teachers to run."

Notice what these have in common. Specific numbers, even small ones. A time frame. And a verb in the past tense that describes an action, not a duty. "Responsible for" is a job description. "Cut," "grew," "raised" are accomplishments.

Start with the verb, and stop recycling the same five

Every bullet starts with a verb, and the verb does more work than you'd think. "Managed" tells me you were present. "Turned around," "salvaged," "doubled" tell me something happened.

The trap is repetition. If four bullets in a row start with "Led," the fourth one reads like filler even if it isn't. Rotate through verbs that actually match what you did: built, launched, negotiated, automated, redesigned, recovered, trained, shipped, consolidated, won.

One warning here. Don't reach for a thesaurus and grab "spearheaded" or "orchestrated" if you'd never say them out loud. Recruiters have read "spearheaded" forty times today. Plain and specific beats fancy and vague every single time.

"But I don't have numbers"

The most common objection, and it's fair. Not every job produces a dashboard. Here's how to find numbers anyway, roughly in order of effort:

Count things you already know. How many customers per day? How many reports per month? How big was the team? How many locations, products, tickets, students, patients? Volume is a number, and it establishes scale even when you can't claim an outcome.

Estimate honestly with ranges. "Handled roughly 50-70 support calls per week" is legitimate. You're not under oath to the decimal point; you're giving the reader a sense of size. Just make sure you could defend the range in an interview, because you'll be asked.

Use before and after states. "Inherited a backlog of 300 unprocessed applications and cleared it in six weeks" needs no percentage.

Use relative outcomes. Rankings, ratings, being chosen. "Selected from a team of 9 to train new hires" is quantified proof that someone trusted you.

And if a bullet truly has no number available, make it concrete instead. "Wrote the onboarding guide new hires still use" beats "improved documentation processes" even though neither has a digit in it. Specificity is the actual goal. Numbers are just the easiest way to get there.

How many bullets, and in what order

Rough guide: four to six bullets for your current or most recent role, two to four for the one before, and one to three for anything older. A job from 2015 does not need six bullets. It probably needs one, or none.

Order matters more than people think. Put your best bullet first in every role, because it might be the only one that gets read. Best means most relevant to the job you're applying for, which is not always the thing you're proudest of. Your award-winning internal wiki is a great story, but if the posting is about client management, the client bullet goes first.

That's the part that trips people up: the right order changes with every application. The bullet that leads for one posting gets buried for another. Doing this reshuffle by hand for every single application is tedious enough that almost nobody does it, which is exactly why the people who do get more callbacks. If you'd rather not spend 30 minutes per application moving bullets around, JobTailor reads the job description and reorders and rewrites your bullets to match it, so each version leads with what that specific employer is scanning for.

Write for the ATS without writing like a robot

Before a human scans your bullets, software often does. Applicant tracking systems parse your resume into fields and search it for keywords from the job description. Two rules keep your bullets safe:

Use the posting's language for hard skills. If they say "Salesforce" and you wrote "CRM administration," write Salesforce. If they say "stakeholder management" and you have it, use those words somewhere. The ATS matches strings, not synonyms.

Keep formatting boring. Standard round bullets, single column, no icons, no text boxes. Fancy templates are where good bullets go to die in a parser.

What you should not do is stuff keywords into bullets where they don't belong. A human reads the resume after the software does, and a bullet like "Leveraged synergistic stakeholder management best practices" fails the human test badly enough to cancel out passing the software one.

Bullets to delete right now

Some bullets actively hurt you. If any of these are on your resume, cut them today:

The duties list. "Responsible for daily operations of the store." That's the job posting you answered, not evidence about you.

The soft skill claim. "Excellent communicator with strong attention to detail." Claims aren't bullets. If your attention to detail matters, show a bullet where it caught something expensive.

The mystery acronym. "Managed QBRs for T2 accounts via the RACI matrix." Nobody outside your old company knows your internal shorthand. Translate it.

The humble nothing. "Assisted with various projects as needed." This bullet says "I was there." Find one project, name it, and say what you did.

The ancient artifact. Proficiency in software nobody has used since 2018. It doesn't show experience, it shows you haven't updated the file.

A worked example, start to finish

Here's a real-ish transformation for a retail assistant manager, since bullet advice usually only gets tech examples.

The original:

• Responsible for opening and closing the store


• Managed employees and schedules


• Handled inventory and ordering


• Provided excellent customer service

The rewrite:

• Ran daily operations for a $2.1M/year location, including full P&L ownership of a $180K monthly inventory budget


• Scheduled and coached a team of 14 associates, cutting turnover from 6 departures a year to 2 by moving to preference-based scheduling


• Reduced inventory shrink 1.8 points in one year (worth roughly $38K) by rebuilding the weekly cycle-count routine


• Kept a 4.8 Google rating across 200+ reviews, the highest of 12 stores in the district

Same job. Same person. The first version gets seven seconds and a pass. The second one gets a phone call.

The last pass before you send it

Read each bullet and ask one question: could the person who did this job badly write the same sentence? If yes, the bullet needs a result, a number, or a specific. If no, it stays.

Then do it again for the next application, because the bullets that matter for one posting aren't the ones that matter for the next. That per-application pass is the single highest-leverage 20 minutes in a job search, and also the first thing everyone skips when application number 30 rolls around. If you've hit that wall, try JobTailor free: upload your resume, paste a posting, and see what your bullets look like tailored to that exact role. At minimum you'll spot two or three bullets worth rewriting yourself.

Seven seconds isn't much. Make every line earn its place.