A weak resume bullet point describes a duty rather than a result, opens with a vague verb, runs past two lines, or contains none of the language the job posting uses. Fixing it means rewriting the line so it states what you did, how, and what changed because of it — in one to two lines, starting with a specific verb, and using the terms the employer asked for.

Most resumes fail on bullets rather than on structure. The layout is fine and the roles are right; the lines underneath each role simply do not give a reader any reason to prefer this candidate over the next one.

Bullet points are where a resume is won or lost, because they are the only part a reader actually evaluates. Job titles and dates establish that you were somewhere; the bullets are the evidence of what you did while you were there. When they are weak, the resume reads as a list of jobs held. When they are strong, it reads as a record of things accomplished — and that is the difference between a screening pass and a rejection for a candidate with exactly the same history.

This guide covers the five ways a bullet goes wrong, a formula that fixes most of them, and fifteen before-and-after rewrites you can pattern-match against your own.

Short on time? The free AI resume fixer applies everything in this guide for you: upload your resume, paste the job description, and download a tailored, ATS-ready PDF in about a minute.

The Five Ways a Bullet Fails

Almost every weak bullet has one of these problems. Diagnosing which one tells you what the rewrite needs.

Failure What it looks like The fix
Duty, not result "Responsible for managing social media accounts" Replace the responsibility with the outcome it produced
No number "Improved customer satisfaction" Add the scale, the change, or the frequency
Vague verb "Helped with", "worked on", "assisted in" Name the specific action you took
Too long Three or four lines covering several unrelated things One idea per bullet; split or cut
Keyword-free Accurate, but in none of the terms the posting uses Rewrite in the employer's vocabulary

The first two are by far the most common, and they usually appear together: a bullet that describes a duty rarely has a number in it, because duties do not produce numbers — results do.

The Formula That Fixes Most Bullets

A bullet that works has three parts, in roughly this order:

  1. A specific verb — what you did. Not "helped" or "was responsible for" but "negotiated", "rebuilt", "cut", "launched". A reference list is in resume action verbs.
  2. The what and how — the thing you acted on and the method, briefly.
  3. The result — what changed, with a number where one exists. The categories to look for when you think there is no number are in quantifying resume achievements.

Put together: Cut monthly invoice processing time from 5 days to 2 by moving approvals into the ERP workflow. Verb, what, how, result. One line and a half. Nothing to interpret.

Not every bullet can carry a number, and forcing a fake one is worse than having none. But every bullet can carry a specific verb and a concrete object, and most can carry some indication of scale — how many, how often, how big.

15 Before and After Examples

Grouped by the failure they fix. The "after" versions are not longer, in most cases — they are more specific.

Duty, not result

  • Before: Responsible for managing the company's social media accounts.
    After: Grew the company's LinkedIn following from 2,100 to 9,400 in 14 months by moving to a three-posts-a-week schedule built around customer case studies.
  • Before: Handled customer complaints and escalations.
    After: Resolved 40–50 escalated customer complaints a week, closing 85% without a refund by introducing a call-back-within-2-hours rule.
  • Before: Duties included scheduling, ordering supplies, and maintaining records for the clinic.
    After: Ran scheduling and supply ordering for a 6-practitioner clinic, cutting missed appointments by a third with SMS reminders.

No number

  • Before: Improved the onboarding process for new employees.
    After: Rebuilt new-hire onboarding into a 5-day structured programme, reducing time-to-first-ticket for support staff from 4 weeks to 9 days.
  • Before: Increased sales in my territory.
    After: Increased territory revenue 22% year on year ($1.1M to $1.34M) by re-prioritising the top 30 accounts and dropping 40 inactive ones.
  • Before: Wrote reports for senior management.
    After: Produced the weekly operations report read by the COO and 12 regional managers, consolidating six spreadsheets into one dashboard.

Vague verb

  • Before: Helped with the migration to the new CRM.
    After: Mapped and cleaned 18,000 contact records for the HubSpot migration and trained 25 sales staff on the new pipeline stages.
  • Before: Worked on improving warehouse efficiency.
    After: Redesigned the pick path for the top 200 SKUs, lifting picks per hour from 48 to 61.
  • Before: Assisted in the preparation of the annual budget.
    After: Built the department's $2.4M annual budget model and the variance tracking used in monthly reviews.

Too long

  • Before: Managed a team of five developers, ran daily standups and sprint planning, liaised with the product team on requirements, handled code reviews, dealt with production incidents, and was responsible for hiring two new developers during the year.
    After: Led a team of 5 developers shipping a two-week release cycle; hired and onboarded 2 engineers in the year. (Incidents and code review become their own bullet, or are cut.)
  • Before: Coordinated with vendors, negotiated contracts, tracked deliveries, and maintained the supplier database, ensuring that all materials arrived on time and within budget across multiple concurrent projects.
    After: Negotiated supplier contracts across 3 concurrent builds, bringing materials in 6% under budget with no schedule delays.
  • Before: Was in charge of the front desk, which involved greeting visitors, answering the phones, managing the meeting room calendar, sorting the post, and helping other departments with admin tasks when they needed it.
    After: Ran reception for a 120-person office: visitors, switchboard, and meeting-room bookings for 8 rooms.

Keyword-free

  • Before: Looked after the money coming in and going out.
    After: Managed accounts payable and receivable for a $6M-turnover business, closing the month within 5 working days.
  • Before: Made sure the website was working properly and fixed things when they broke.
    After: Maintained a WordPress/WooCommerce site with 40k monthly visitors, reducing checkout errors 70% after replacing the payment plugin.
  • Before: Got new people to buy from us and kept the existing ones happy.
    After: Owned new-business development and account management for 35 B2B clients, with 94% annual retention.

Notice that the "after" lines in the last group are written in the language a posting for that role would use — accounts payable, WooCommerce, account management, retention. That is not decoration; it is what lets both a parser and a recruiter match the line to the requirement. The mechanics are in resume keywords.

How Many Bullets, and How Long

  • Three to five bullets for each recent, relevant role. Two for older or less relevant ones. One line for anything more than ten years old, or drop it.
  • One to two lines each. If a bullet runs to three, it is either two ideas or it has filler in it.
  • Lead with the strongest. The first bullet under each role is the one most people read; the fifth is the one almost nobody does.
  • No full stops needed, but be consistent — all with or all without.
  • Present tense for the current role, past for everything else.

The way bullets sit under each role — title, employer, dates, then the lines — is covered in how to list work experience on a resume, and the layout rules that keep them readable are in how to fix resume formatting.

Fixing Bullets for a Specific Posting

A bullet that is strong in general is not necessarily strong for a particular job. The rewrite that matters most is the one you do with the posting open beside the resume: which requirements does the employer list, and which of your bullets speaks to each one? Where a requirement has no matching bullet, either you have relevant experience you have not written down, or you do not — and both are worth knowing before you apply. The full method is in tailoring a resume to a job description.

Doing that comparison by hand for every application is the part most people skip. The AI resume fixer does it in about a minute: paste the resume and the posting, and it identifies the requirements your bullets do not address, rewrites the weak lines in the employer's vocabulary, and returns a tailored PDF. The first comparison is free, with credit packages on the pricing page for further roles. If you are writing the resume from scratch, the free resume builder prompts for a result in every bullet.

Common Questions About Resume Bullet Points

How do I make my resume bullet points stronger?

Start each one with a specific verb, name the thing you acted on, and finish with what changed — ideally with a number. Replace any bullet that describes a responsibility with the result that responsibility produced. Keep each to one or two lines.

Should every bullet point have a number?

No, and inventing one is worse than leaving it out. Aim for a number in most bullets under recent roles — scale, change, frequency, or money — and make the rest specific in other ways: a named system, a named client type, a concrete deliverable.

How many bullet points should a job have on a resume?

Three to five for recent, relevant roles; two for older or less relevant ones; one line or nothing for roles more than a decade old. More than five under one role means the weaker ones are diluting the strong ones.

How long should a resume bullet point be?

One to two lines. A three-line bullet is almost always two ideas that should be separate bullets, or one idea with filler that should be cut.

Should I use "I" in resume bullet points?

No. Bullets are written as fragments starting with the verb — "Reduced", not "I reduced". The subject is understood to be you, and dropping it saves space on every line.

Can AI fix my resume bullet points?

It can do the rewriting well if it has both the resume and the job posting, since the posting is what tells it which vocabulary and which requirements matter. Given only the resume, it will polish the wording but cannot know what the employer wants — so use it with the posting, and check that any numbers it produces are ones you actually supplied.