Résumé Bullet Points: How to Describe Your Work Experience

By Olive Jobs · Updated August 10, 2026 · 10 min read

TL;DR — A strong résumé bullet has three parts: an action verb, what you actually did, and the result — with a number in it whenever one honestly exists. Give each recent job three to five bullets, put the most relevant first, delete every "responsible for," and keep each bullet to one or two lines. If you think your job had no numbers, it did: customers per shift, dollars in the drawer, minutes saved, people trained.

The experience section is where a hiring manager decides whether you did work or merely held a position. Most résumés lose there, and they lose the same way: the bullets read like the job posting the company already wrote. "Responsible for customer service" describes a slot on a schedule, not a person. What follows is the mechanics — the anatomy of a bullet, the verbs that carry weight, how to find numbers when you're sure you have none, how many bullets each job deserves, and a long list of before-and-after rewrites across the jobs people actually work. Retail, restaurants, warehouses, and campus desks included, because most résumé advice quietly assumes you had an office internship.

What does a strong résumé bullet actually look like?

Every serious career center teaches a version of the same three-part shape, under different initials.

  • PAR, from MIT's Career Advising & Professional Development: describe the Project or context, the Activity you did, and the Result. MIT tells you to start with a strong action verb, follow with the project, then "tell the reader the RESULT of your actions."
  • APR, from the University of Arizona's Center for Career Readiness: Action + Project/Problem + Result. Their instructions are three steps long — "Start with a strong verb," "Add details and numbers," "Include a result to show your impact."
  • Two orders, from Yale's Office of Career Strategy: either lead with the verb, name the project, and close on the quantified result — or invert it and lead with the impact you delivered, measure it, then detail what you did.

Strip the acronyms and it's one sentence with three jobs to do:

VerbRebuiltwhat you didthe weekly inventory count for a 12-person storeresultcutting Sunday close-out from 90 minutes to 35.

Assembled: "Rebuilt the weekly inventory count for a 12-person store, cutting Sunday close-out from 90 minutes to 35."

The result is the part almost everyone drops. Yale's own before-and-after shows exactly what that costs you: "Worked with a student leadership committee to increase member participation" becomes "Led a 5-person leadership team to increase student participation by 100% from 50 to 100 members by creating a stronger social media presence." Same student, same semester, same true facts. One version is a slot; the other is a person who moved a number.

Which action verbs should you use — and which words should you delete?

Purdue's Online Writing Lab is blunt about placement: "use action verbs as the first word of each bullet point to emphasize job descriptions in your resume." Their reasoning is that action verbs "make sentences and statements more concise," and concise writing is easier for a reader to absorb — which is the whole game in a document that gets skimmed.

On tense, MIT's résumé checklist gives the rule in one line: "Did you start each phrase with an action verb? (Past tense verbs for previous roles, present tense verbs for current roles)." Pick the tense per job, then stay consistent inside that job.

Verbs worth reaching for, grouped by what they claim:

  • Made something — Built, Designed, Developed, Launched, Wrote, Assembled, Produced.
  • Ran something — Managed, Coordinated, Operated, Scheduled, Oversaw, Staffed.
  • Made something better — Streamlined, Reduced, Cut, Increased, Reorganized, Automated, Standardized.
  • Dealt with people — Served, Trained, Advised, Resolved, Onboarded, Persuaded, Mediated.
  • Worked with information — Analyzed, Audited, Tracked, Tested, Reconciled, Documented, Forecasted.

And the phrases to delete on sight, because they announce that no result is coming: Responsible for, Duties included, Helped with, Worked on, Assisted with (unless you say what you actually did), Various tasks as assigned.

One caution in the other direction: don't inflate. "Spearheaded a merchandising initiative" for restocking a shelf reads as a lie, and it makes the true bullets beside it look suspect. "Reorganized" is the stronger word when it's the accurate one. Purdue also asks that bullets stay in parallel form — every item in a job grammatically built the same way.

How do you quantify achievements when you think you have no numbers?

Almost nobody has performance metrics from a first job. Everybody has scope. MIT's checklist asks whether you "give evidence and quantify relevant information (e.g. size, scale, budget, staff) for impact" — note that three of those four are just how big the thing was, not how well you did it. Four families of numbers are available to nearly every job:

  • How many — customers per shift, tickets, orders, emails, plates, boxes, students, calls, samples.
  • How much — register totals, budget managed, dollars raised, average check, inventory value.
  • How often, how fast — shifts per week, turnaround time, minutes saved, error rate.
  • How big — team size, number of locations, class size, square footage, dataset rows.

Getting to a defensible number without inventing one:

  1. Count one typical unit, then multiply. Count a single shift honestly, and you have a per-shift figure and a per-week figure.
  2. Use a range. "80 to 100 covers a night" is more credible than a suspiciously round single number.
  3. Say "roughly" or "about" when it's an estimate. Hedged and true beats precise and invented.
  4. Never write a number you can't explain out loud. Every figure on the page is an interview question you volunteered for. If you claim sales rose 30%, be ready to say how you know.
  5. When no number exists, quantify the scope, or end on a verifiable outcome — the checklist was adopted by the team, the FAQ is still posted at the desk, the protocol is what new hires train on.

So instead of the unfalsifiable "Improved sales by 30%," write what you can defend: "Signed up roughly 15 customers a shift for the loyalty program, the highest rate among six associates on the schedule."

How many bullets should each job get?

Purdue sets the floor: "Each job should have a minimum of three bulleted items with the most relevant duties listed first." That last clause matters as much as the count — order bullets by relevance to the job you want, not by the sequence you did them in.

A working rule built on top of that floor:

  • The recent, relevant job: three to five bullets.
  • The older or unrelated job: one to two, purely for the transferable mechanics.
  • Anything from more than about ten years ago, or high school once you're well into college: a title line, or nothing.

Keep the whole thing tight. MIT's checklist: "Have you kept it to one page? You may use two pages if you have an advanced degree or extensive experience (10+ years)." Each bullet should run one to two lines; if it wraps onto a third, you've either buried two accomplishments in one bullet or over-explained the setup. And cut any bullet a stranger could have guessed from your job title alone — "Answered phones" at a front desk earns nothing.

Before and after: fourteen rewrites across real jobs

The move is identical every time. Keep the same true facts, add the verb, the scope, and the outcome.

Retail sales associate

Before: Responsible for customer service and keeping the floor stocked.

After: Served 100+ customers per shift as the only associate on the floor during weekday openings, and reorganized the seasonal endcap so daily restocking took about 20 minutes less.

Restaurant server

Before: Took orders and delivered food to tables.

After: Ran a six-table section through 80 to 100 covers a night, upselling specials and desserts to raise average check by roughly $4.

Fast-food crew member

Before: Worked the front counter and drive-thru.

After: Operated drive-thru through peak dinner rush while holding average order time under three minutes, and trained four new hires on food-handling procedure.

Arizona's career center uses the same rewrite on a food-service bullet — "Led training of new employees at smoothie and sandwich prep stations to reinforce food handling and safety guidelines" — where the bolded clause is the entire difference between a task and a contribution.

Warehouse associate

Before: Picked and packed orders in a warehouse.

After: Picked and packed 250 to 300 orders per shift at 99% scan accuracy, and flagged a mislabeled bin location that had been causing repeat mis-ships.

Barista

Before: Made drinks and cleaned the store.

After: Served roughly 300 drinks a day on the opening shift, opened the store solo four mornings a week, and cut morning waste by re-sequencing the prep list.

Campus library front desk

Before: Helped students at the front desk of the library.

After: Answered 40 to 60 access and research questions per shift, and wrote a one-page FAQ covering the ten most repeated questions that the desk still uses.

Resident advisor

Before: RA for a residence hall.

After: Supported 45 first-year residents, ran monthly floor programs averaging 25 attendees, and mediated six roommate conflicts to written agreements.

Childcare and babysitting

Before: Babysat for local families.

After: Cared for three children under age eight on a standing 15-hour weekly schedule for two years, coordinating school pickup, meals, and homework with no missed commitments.

Delivery driver

Before: Delivered food orders.

After: Completed 1,200+ deliveries over 18 months at a 4.9 out of 5 customer rating, self-managing routing, fuel costs, and peak-hour scheduling.

Customer support

Before: Answered customer calls and emails.

After: Resolved 60 to 70 tickets a day across phone and chat at roughly 85% first-contact resolution, and drafted five response templates the whole team adopted.

Administrative internship

Before: Assisted with administrative tasks and data entry.

After: Cleaned and reconciled a 4,000-row client contact list, removing 22% duplicate records before the fall campaign mailed.

Marketing internship

Before: Helped manage the company's social media accounts.

After: Wrote and scheduled three posts a week across two channels, and A/B tested caption formats that lifted average post engagement about 18% over the summer.

Software internship

Before: Worked on a feature for the team's internal tool.

After: Built a CSV export feature in Python for an internal reporting tool used by 12 analysts, replacing a manual step that had cost about two hours a week.

Research assistant

Before: Assisted with research in a professor's lab.

After: Ran weekly assays on 60+ samples, logged results into a shared dataset of 3,000+ observations, and rewrote the sample-prep protocol that two new assistants now train on.

Read them back to back and the pattern is unmistakable: the "before" version is what your manager would say about the role; the "after" version is what only you could say about your time in it.

What if the job has nothing to do with the one you want?

Translate the mechanics instead of hiding the job. A closing shift is cash handling, inventory reconciliation, and customer escalation. A section of six tables is throughput under time pressure. A residence hall floor is conflict resolution with people who cannot be fired or avoided. Name the underlying skill inside the bullet's result and the relevance becomes the hiring manager's conclusion rather than your claim.

What doesn't work is apologizing for the job or padding it with corporate vocabulary. Nobody is impressed by a vague retail bullet, but everyone recognizes a person who ran a drawer to the penny for two years. If your whole history is jobs like these, that's a full résumé's worth of material — we walk through building one in how to write a résumé with no work experience.

Will an applicant tracking system read your bullets?

It reads the words, so use real ones. Echo the specific posting's language — the tools, systems, and skill names it actually lists — inside bullets that are true, rather than parking a keyword block at the bottom of the page. Keep the section as plain text bullets: no tables, columns, or text boxes wrapping your accomplishments, since those are the layouts most likely to come apart in parsing. The full mechanics are in résumé keywords and the ATS.

The mistakes that show up most

  • Duties instead of outcomes. The most common failure by a wide margin. Every bullet should end somewhere.
  • "Responsible for" as an opener. It burns the most valuable words on the line.
  • The paragraph. A block of prose in the experience section goes unread.
  • Inflated verbs. "Orchestrated" for folding shirts undermines the bullets that are true.
  • Numbers you can't source. Invented percentages collapse in the first interview question.
  • First-person pronouns. MIT's checklist frames bullets as action-driven statements without them — "Managed the closing shift," not "I managed the closing shift."
  • Mixed tense inside one job. Pick past or present per role and hold it.
  • Bullets a stranger could predict from the title. If the job explains the bullet, the bullet adds nothing.

None of this manufactures a qualification you don't have. A rewritten bullet won't make you a senior engineer, and no verb list clears a hard requirement in the posting. What it does is stop real work from being invisible — which is the actual failure mode for most people applying to entry-level roles, because the work was genuinely there and the page never said so. Write the bullets once, honestly and with numbers, and then reshape them per application against what each posting is asking for: how to tailor a résumé with AI covers that second pass.

Sources

Keep going with Olive

Related guides