How to Write Resume Bullet Points That Actually Get Read

A resume bullet earns its place by stating what you did, at what scale, with what result — in under two lines. Most bullets fail because they describe responsibilities instead of accomplishments, which produces a document that reads like a job description rather than a record of a person doing a job.

Before the craft, an uncomfortable fact about the audience. Eye-tracking research from Ladders found recruiters spend an average of 7.4 seconds on an initial resume screen, with roughly 80% of that time on six elements: your name, your current title and company, your previous title and company, position dates, and education.

Your bullets are not on that list.

This is not a reason to neglect them. It is a reason to understand what they are for. Bullets do not win the first pass — job titles and companies do. Bullets win the second pass, once someone has decided you are plausible and is now deciding whether you are interesting. They also carry nearly all the load in recruiter keyword searches and in the hiring manager's eventual closer read.

Write them for the person who has already decided to keep reading.

The core structure

One pattern handles the large majority of cases:

[Specific action] + [scope or scale] + [outcome or result]

All three parts matter, and the middle one is the one people skip.

Rebuilt the onboarding email sequence for 12,000 monthly signups, lifting 30-day activation from 34% to 48%.

Action: rebuilt the onboarding sequence. Scope: 12,000 monthly signups. Outcome: activation 34% → 48%.

Remove the scope and it weakens noticeably: "Rebuilt the onboarding email sequence, lifting 30-day activation from 34% to 48%." Still good — but a reader cannot tell whether this was 200 users or 200,000, and those are very different accomplishments.

Remove the outcome and it becomes a task: "Rebuilt the onboarding email sequence for 12,000 monthly signups." Fine as a fallback, and far better than nothing.

Responsibilities versus accomplishments

This is the single most common defect in real resumes, and it is not a writing problem so much as a framing one.

The left column describes a job that existed. The right column describes a person who held it. Two candidates with identical duties produce wildly different right-hand columns, which is exactly the information a reader is looking for.

A quick diagnostic: if a bullet would still be true on the day you started the job, it is a responsibility, not an accomplishment.

Quantifying work that was never measured

This is the objection everyone raises, and it is legitimate. Most jobs do not hand you a dashboard. Nurses, teachers, paralegals, warehouse supervisors, admin staff, lab technicians — huge categories of real work where nobody tracked your personal delta.

The mistake is assuming quantification means results. It does not. It means numbers, and numbers come in several forms you can recall without any analytics access at all.

Scope numbers — how big was the thing?

Managed a portfolio of 40 mid-market accounts totaling ~$2M in annual revenue.

Volume numbers — how much passed through you?

Processed 60–80 patient intakes per shift in a 24-bed emergency department.

Frequency numbers — how often?

Ran weekly design reviews for a 14-person engineering team across 3 time zones.

Team and stakeholder numbers — who was involved?

Trained 9 new hires and wrote the onboarding playbook now used department-wide.

Duration numbers — over what period?

Maintained 100% on-time filing across an 18-month regulatory transition.

Budget and resource numbers — what did you control?

Managed a $340K annual vendor budget across 6 suppliers.

Every one of these is quantification. None required a measurement system. If you genuinely cannot recall exact figures, approximate honestly — "roughly 50," "~$2M," "60–80" — which is both accurate and defensible in an interview. A clearly-marked estimate is far better than a vague adjective, and far safer than a precise-sounding number you invented.

What to avoid: adverbs standing in for measurements. Significantly improved. Dramatically increased. Substantially reduced. These are the shape of a metric with the metric removed, and experienced readers discount them automatically.

Verbs: strong, but not inflated

Start each bullet with a verb in a consistent tense — past tense for former roles, present for the current one.

Beyond that, the usual advice about "power verbs" needs a correction. The failure mode in 2026 is not weak verbs. It is inflated ones.

Spearheaded. Orchestrated. Championed. Pioneered. Drove. Leveraged. Helmed. These appear constantly, largely because AI drafting tools reach for them by default, and they now signal the opposite of what they intend. A reader who sees "spearheaded" attached to a routine task discounts the whole document.

Match the verb to what actually happened:

Plain verbs — built, ran, wrote, cut, grew, fixed, launched, negotiated, taught, reduced — are more credible precisely because they are unglamorous. Save the elevated verb for the one bullet where it is literally true.

Avoid opening with Responsible for, Duties included, or Helped with. The first two announce a responsibility rather than an accomplishment. The third pre-emptively minimizes you.

Length and count

Length: one to two lines, roughly 15–30 words. A three-line bullet will be skipped in a fast read, and it is almost always either two accomplishments that should be split or one that needs cutting.

Count per role:

Total across the resume: keep it under about twenty. This is a budget, and it forces the right decision — every bullet you add dilutes the attention available to the others. Cutting your weakest three bullets usually improves a resume more than adding three new ones.

Ordering

Within each role, lead with your strongest bullet, not your most chronological or most routine one. Readers apply a primacy effect to lists just as they do to pages; the first bullet under a job gets meaningfully more attention than the fourth.

"Strongest" means most relevant to the role you are applying for, not most impressive in the abstract. A national award is worth less than a directly analogous project if the analogous project is what the posting asks for.

Worked examples across fields

Most resume advice is written for software and marketing roles. The pattern generalizes.

Nursing

Before: Provided patient care in a busy hospital unit.

After: Managed care for 6–8 patients per shift in a 24-bed cardiac unit; precepted 4 new graduate nurses through their 12-week orientation.

Teaching

Before: Taught high school mathematics and developed lesson plans.

After: Taught 5 sections of Algebra II to 140 students; redesigned the unit assessment structure, raising end-of-year passing rates from 71% to 84%.

Operations

Before: Responsible for warehouse inventory management.

After: Ran inventory for a 40,000 sq ft distribution center moving ~1,200 SKUs; cut stock discrepancies 60% by introducing weekly cycle counts.

Sales

Before: Sold software to enterprise clients and exceeded targets.

After: Closed $1.4M in new ARR against a $1.1M quota across 22 enterprise accounts; shortened average sales cycle from 94 to 71 days.

Administration

Before: Provided administrative support to senior leadership.

After: Supported 3 VPs across calendar, travel, and board prep; built the expense workflow now standard for a 90-person office.

In every pair, nothing was invented. The "before" simply failed to state what was already true.

Six ways bullets fail

1. Describing the role, not the person. Would be identical on any colleague's resume.
2. Adverbs instead of numbers. Significantly, dramatically, substantially.
3. Listing tools without outcomes. "Used Salesforce, HubSpot, and Marketo daily." Put tools in a skills section; bullets are for what you did with them.
4. Burying the accomplishment. Opening with context and reaching the result at word 30. Lead with the result.
5. Inconsistent tense or punctuation. Usually a symptom of a resume assembled from several older versions. Do one consistency pass at the end.
6. Claims you cannot defend. Every number invites the question "how was that measured?" If you cannot answer, remove it.

That last one is the real constraint on everything above. A resume is an interview agenda. Anything you write is something you are volunteering to be asked about.

A short editing pass

Once written, run three checks:

The cover test. Hide your name and employer. Could these bullets belong to anyone in your field? If so, add the specific detail only you have.

The read-aloud test. Anything you would not say to a colleague gets rewritten. This catches verb inflation instantly.

The two-minute test. For each bullet, could you talk about it under questioning for two minutes? If not, cut it or make it something you can.

Where to go next

Bullets are the raw material; which ones you surface depends on the role. Our guide to tailoring a resume to a job description covers selecting and rewriting the three to five bullets that matter for a given posting, and the ATS myths piece explains what screening software actually does with them.

If you use AI to help with phrasing, the input matters far more than the prompt — supply the scope and outcome numbers from this article and the model has something real to compress. Our piece on using AI without sounding generic covers that in detail.

The short version

Bullets lose the seven-second scan and win the second read. Write them as accomplishments rather than responsibilities, quantify with scope when you have no results to cite, use plain verbs over inflated ones, and keep each under two lines.

Then cut the weakest three. A shorter resume where every line carries information beats a longer one where most lines describe a job that existed.

Cutting for quality is not the same as cutting to hit a page count, which is a separate question with its own evidence behind it.