Blog

How to write resume bullet points: examples

Updated , 4 min read

A good resume bullet point names what you did, the context you did it in, and the evidence that it mattered, in one or two lines. Start with a precise action verb, keep it to work you personally did, and choose the bullets that support the role you're applying for. Not every bullet needs a number.

The framework below, CARE, gives you four questions to answer for each bullet. Every example in this guide is illustrative, so replace it with facts you can verify.

Use the CARE framework

Context names the problem, audience, process, product, or constraint. Include it only when it helps the reader understand the work.

Action states what you personally did. Choose a precise verb such as designed, reconciled, investigated, documented, repaired, or negotiated. If you contributed rather than led, say “supported,” “partnered with,” or another accurate verb.

Result or evidence shows what changed, was delivered, or became possible. It can be a verified metric, a completed deliverable, a decision you enabled, a recurring problem you resolved, a quality improvement, or feedback you're allowed to share.

Relevance connects the evidence to the target role through what you select and emphasize. If cross-functional delivery matters for the job, a coordination bullet may deserve more space than an unrelated solo task. The guide to tailoring your resume to a job description helps you choose among valid examples.

Build a bullet from working notes

Answer four prompts before you draft:

  • What needed attention, and for whom?
  • What did I do or contribute?
  • What changed, was delivered, or became possible?
  • Which requirement of the target role does this support?

Notes: Support agents were working from conflicting troubleshooting documents. The candidate reviewed the current guidance with product specialists, consolidated it, and published one approved reference for onboarding and daily support.

Bullet:

Consolidated conflicting troubleshooting documents with product specialists and published one approved guide for support onboarding and daily reference.

The bullet needs no performance percentage. Its context, contribution, and deliverable are clear.

Use evidence without inventing numbers

Never invent a figure or present a guess as a measured fact. If you use an estimate, label it as one and keep the method you used to calculate it. A concrete non-numerical result is often stronger than a doubtful number.

Useful evidence includes:

  • A deliverable you created, launched, repaired, or got approved
  • A decision your analysis supported
  • A complex problem or constraint you handled
  • A process you made clearer or easier to repeat
  • A customer or colleague issue you resolved
  • A requirement, deadline, or quality standard you met

For side projects, the guide to listing personal projects on a resume explains baselines, measurement periods, and non-numerical alternatives.

Before-and-after examples

Customer support specialist

Before:

Helped customers and solved tickets.

After:

Investigated account-access issues, documented recurring causes, and shared resolution notes to improve support handoffs.

The revision names the issue, the action, the artifact, and the audience without inventing a resolution-time result.

Marketing coordinator

Before:

Responsible for email marketing.

After:

Coordinated the product-launch email calendar, verified links and audience segments, and prepared results for the next campaign review.

Add an engagement result only if you know its definition, period, and source.

Software engineer

Before:

Worked on application performance.

After:

Profiled a slow search workflow, removed redundant database queries, and documented the test so future changes could use the same baseline.

The technical change and the repeatable test provide the evidence, with no unsupported percentage.

Avoid common bullet mistakes

Don't choose dramatic verbs that change your role; “led” and “supported” are not interchangeable. Cut context that adds length without explaining scope, difficulty, or audience. Credit team outcomes fairly.

Don't estimate a percentage, customer count, budget, or time saving because a bullet feels incomplete. Check a reliable record or use another kind of evidence. And pick the target role before you polish: a strong but irrelevant bullet still takes up space.

For each important bullet, confirm that the action is yours, the evidence is accurate, and the relevance is clear. Once your bullets are solid, a targeted resume summary can point the reader to them without repeating them. You can also draft them in Better Resume's resume editor, where an AI rewrite tightens the wording but keeps your facts.

Make every bullet earn its place.

Import your resume and rewrite vague bullets into specific ones that stay true to your work.

Create your resume

Building and editing are free. Tailoring and downloads come with a 3-day free trial.

Keep reading

More from the blog

  • Illustration: a resume tailored for Project Coordinator, with a summary of what changed.

    Updated 4 min read

    How to tailor your resume to a job description

    Tailor your resume to a job description in six steps: pull out the requirements, pick your best evidence, adjust the summary and skills, and check the result.

  • Illustration: a project bullet rewritten to show who used the project.

    Updated 5 min read

    How to list personal projects on a resume

    Where to put personal projects on a resume, how to describe them, and which numbers are worth adding, with software, design and research examples.

  • Illustration: a generic resume summary rewritten around one role with AI.

    Updated 4 min read

    How to write a resume summary (with examples)

    A four-part formula for a two-to-four sentence resume summary, with examples for eight roles, from new grads to career changers, and when to skip it.