Weak resume bullets, rewritten: before and after examples

Every example below is a composite we wrote for this post, not a customer’s resume. The facts inside them are invented so they can be shown. The method for recovering your own facts is not.

The most common thing people ask Jen, our resume advisor, is some version of “rewrite my weakest bullet.” Not “explain my grade.” Not “what is a good score.” Rewrite it. Show me.

Fair enough. Here is the gallery. Each pair shows a bullet the way people actually write it, the same bullet after one pass, and the one thing that changed. The pairs are grouped by what was wrong, because the fix follows from the diagnosis, and most resumes have two or three of these problems repeated on every line.

Two rules govern every rewrite here. First, nothing was invented. Every fact in an “after” is something the writer already knew or could have looked up in ten minutes: a count from a schedule, a range from a report, a before and after state from memory. Where a number appears, we say where it came from. Second, the rewrite keeps the writer’s job. Nobody was promoted in the editing. If a bullet describes support work, the rewrite describes support work that mattered.

If you want the method before the examples, read how to quantify a resume without inventing numbers and how to build an evidence inventory before rewriting. If you want to know why any of this matters to a grader, what separates an A resume from an F is mostly this.

1. Responsibilities instead of results

The sign: the bullet starts with “Responsible for” or “Duties included,” or it is a noun phrase copied from the job posting. It describes the job anyone in the chair would have had. There is a longer piece on responsibilities versus achievements; the short version is that everyone applying can do the duties, so the duties do not distinguish you.

Before. Responsible for managing the front desk and answering phones.

After. Ran the front desk for a six-provider clinic, covering walk-ins, phones and scheduling, and kept the morning queue under ten minutes by moving check-in paperwork to the day before.

What changed. The job description became the scope (six providers), one thing the writer actually did (moved the paperwork earlier) and its effect (a shorter morning queue). The ten minutes is what the clinic’s wait-time board showed. She read it every day.

Before. Duties included inventory management, ordering and vendor communication.

After. Owned inventory for a restaurant pantry of about forty items: weekly counts, reorders against a par sheet I rebuilt, and the vendor swap that ended the Friday shortages the kitchen had lived with for a year.

What changed. “Inventory management” became what the inventory was, what got rebuilt and what stopped happening. The item count came off the par sheet.

Before. Responsible for maintaining accurate patient records.

After. Kept records for a 28-bed medical-surgical unit current within the shift, and caught the medication-list gaps at admission that the day team otherwise found at discharge.

What changed. The bed count is the unit’s. “Within the shift” is the standard the writer held herself to, and she can defend it in an interview, which is the test for every claim on this page.

2. No scope

The sign: the verb is fine, the result is real, and there is no sense of size. How many, how often, how big, for whom. Scope is the cheapest honest number on a resume because you can count it.

Before. Managed social media accounts and grew engagement.

After. Ran three brand accounts on a two-post-a-day schedule for a regional furniture retailer, and doubled the share of posts that drew a comment within the first quarter.

What changed. Three accounts, a cadence, a client type and a ratio. The ratio came from the platform’s own analytics export, which the writer could screenshot.

Before. Trained new employees.

After. Onboarded every new hire on the overnight warehouse shift, about two a month for two years, and cut the time to a first unsupervised pick from three weeks to two with a one-page checklist the shift still uses.

What changed. The hire count came from the schedule. The checklist is an artifact the writer can hand over.

Before. Handled customer complaints.

After. Took the escalated calls for a twelve-agent support team, roughly fifteen a day, and closed most of them without a supervisor by keeping a shared list of the twenty answers that solved the same ten problems.

What changed. The queue report showed the daily escalation volume. The answer list exists. “Most of them” is honest where a percentage would have been a guess.

3. Activity without the change

The sign: the bullet lists what you did all day, faithfully, and never says what was different afterward. Our report flags this line as “lead with the change, not the activity.” It is one of the most common notes we give.

Before. Attended weekly project meetings and prepared status reports for leadership.

After. Replaced a weekly slide deck with a one-page status report that named the blocked items first, which is why leadership started clearing blockers in the meeting instead of a week later.

What changed. No number at all. The change is the artifact and its effect, and the writer’s manager would confirm both.

Before. Worked on the migration of the customer database to the cloud.

After. Wrote the validation scripts for a customer database migration. They caught the duplicate-account problem before cutover, which turned a planned weekend rollback into a non-event.

What changed. The scripts exist. The incident did not happen, and the writer can say why.

Before. Assisted teachers in the classroom and helped students with assignments.

After. Ran the small-group reading rotation for a second-grade class of 24, four groups a day, and the two students who started the year below level were reading with the class by spring.

What changed. The roster gives the class size. The reading level is the school’s own assessment, not the writer’s estimate.

4. Vague verbs and empty adjectives

The sign: “helped,” “assisted with,” “worked with,” “various,” “multiple,” “excellent,” “strong,” “dynamic.” The verb hides who did what. The adjective is a claim with no evidence behind it.

Before. Helped with various marketing projects and provided excellent support to the team.

After. Built the email calendar for a product launch, wrote the six launch emails, and pulled the open and click numbers the morning after each send so the team could adjust the next one.

What changed. The emails are in the sent folder. Six is a count.

Before. Assisted in the development of new software features.

After. Shipped the export-to-spreadsheet feature end to end, from the ticket to the release note, in a four-person team where I was the only one who had touched the reporting code.

What changed. The commit history backs the first half. “The only one” is a fact about the team the writer can state plainly and an interviewer can check with one question.

Before. Strong communicator with a dynamic personality.

After. Delete it.

What changed. This bullet cannot be rewritten because it contains nothing. Adjectives about yourself belong in the interview, where someone can test them. If communication is the point, show a communication: “Wrote the onboarding guide new hires still use.”

5. The number was there and never got written down

The sign: the writer says “I don’t have metrics.” Almost always they have counts, ranges, frequencies and before and after states, all of which are numbers. What they lack is a dashboard. You do not need one.

Before. Improved efficiency in the accounts payable process.

After. Cut invoice approval from about two weeks to under five days by moving the three-signature routing into the accounting system’s own workflow instead of email.

What changed. The writer remembers how long it took before because vendors complained. The system shows how long it takes now. A range is honest. “About” is honest.

Before. Increased sales.

After. Grew my territory from the smallest of five to the second largest in eighteen months, mostly by winning back the twelve dormant accounts the previous rep had written off.

What changed. Territory rankings are public inside a sales team. The dormant list came out of the CRM.

Before. Reduced customer wait times.

After. Brought the average hold time on the billing line down from over eight minutes to under three by fixing the routing rule that sent every payment question to the smallest queue.

What changed. The phone system report has both numbers. The writer knows them because getting them was the whole project.

If you genuinely cannot recover a number, write the specific instead. “Every branch in the region” is a specific. “Multiple locations” is not.

6. The point arrives at the end

The sign: three clauses, and the result shows up after the second comma, if at all. A reader gives a bullet a couple of seconds. Whatever sits in the first six words is what they take away.

Before. Working closely with the operations team and using data from multiple systems, I was able to identify and resolve a long-standing scheduling issue that had affected delivery times.

After. Fixed the scheduling error that had made Monday deliveries late for two years, by matching the dispatch and warehouse calendars that had been kept in different systems.

What changed. The result moved to the front. “Two years” is how long the complaint had been open, and the ticket says so.

Before. In collaboration with the design and engineering teams, participated in the redesign of the checkout flow, which resulted in a higher conversion rate.

After. Redesigned the checkout flow with one engineer and one designer. The new flow beat the old one in the test we ran, so it shipped to everyone.

What changed. The result is stated the way it happened, with no invented percentage. If the writer knows the lift, they should write it. If not, “beat the old one in the test” is true and testable.

7. Jargon and internal names

The sign: acronyms and project codenames that meant everything inside the building and nothing outside it.

Before. Led the PHOENIX workstream for the Q3 GTM initiative in partnership with the CoE.

After. Led the launch plan for a new payments product across sales, support and marketing, and had every team trained on it two weeks before release.

What changed. The codename was translated into what it was. “Two weeks before” is on the plan.

Before. Managed the CMDB and ensured ITIL compliance across the estate.

After. Kept the inventory of every server and application the company ran, so that when the outage hit we knew within minutes which services were affected instead of finding out over hours.

What changed. The job in plain words, plus one moment where it mattered.

8. Skills dumped into a bullet

The sign: a bullet that is a list of tools. Tools belong in the skills section. A bullet is for what you did with them.

Before. Utilized Excel, SQL, Tableau and Python for data analysis and reporting.

After. Replaced a weekly report that took a full day to assemble by hand with a SQL query and a Tableau dashboard that refreshes itself, so the team stopped waiting until Tuesday for Monday’s numbers.

What changed. The dashboard exists. “A full day” is what the writer’s own timesheet showed.

9. Two jobs in one bullet

The sign: the bullet runs past two lines because it is really two accomplishments, or one accomplishment plus the entire job description.

Before. Managed a team of servers and bartenders, handled scheduling, ordering, customer complaints, cash reconciliation, training, and worked with the owner on menu changes and promotions that increased weekend revenue.

After, as two bullets.

• Ran a floor team of eleven servers and bartenders, including schedules, training and nightly cash-out.
• Proposed the Thursday prix fixe that turned the slowest night of the week into the third busiest within two months.

What changed. The headcount is on the schedule. The night ranking is in the point-of-sale report. The first bullet is the job, the second is the thing only this writer did.

10. Management work without the manager title

The sign: you ran things without a title that says so, and the bullet either overclaims (“Managed a team”) or hides it (“Assisted the manager”). There is a whole post on doing management work without the title.

Before. Assisted the store manager with daily operations.

After. Opened and closed the store four days a week as keyholder, ran the floor when the manager was off, and handled the weekly cash deposits and the schedule for eight associates.

What changed. Every clause is a duty the writer actually held. None of it requires the word “manager.”

Before. Managed a team of developers.

After, when the title was real. Led a team of four developers as tech lead: ran planning, reviewed every pull request, and made the architecture calls.

After, when it was not. Led the day-to-day work of a four-developer team as senior engineer, including sprint planning and code review, while the engineering manager owned hiring and reviews.

What changed. The second version tells the truth about the boundary, which is exactly what an interviewer will ask about.

11. No experience yet

The sign: a student or a career changer with coursework, projects and part-time work, writing bullets that apologize.

Before. Completed a group project on marketing strategy for a local business.

After. Ran the customer interviews for a class consulting project with a local bakery, fourteen interviews over three weeks, and the owner adopted two of our recommendations, a loyalty card and earlier weekend hours.

What changed. The interview count is in the project log. The outcome came from the owner, who can be a reference.

Before. Cashier at a grocery store.

After. Worked the express lane at a high-volume grocery store through two holiday seasons, trained four new cashiers, and was the one called over when a register needed an override.

What changed. All of it is true for many cashiers, and almost none of it appears on most cashier resumes.

12. The overclaim

The sign: “spearheaded,” “revolutionized,” “single-handedly,” “drove,” or a percentage nobody measured. Often it is the fingerprint of an AI tool that was asked to make a bullet stronger. Graders notice, interviewers notice, and interviewers ask. There is a reason AI resume builders make things up.

Before. Spearheaded a revolutionary transformation of the onboarding process, increasing efficiency by 300%.

After. Rewrote the onboarding checklist and moved it into the HR system, which cut new-hire paperwork from about ten forms to three and ended the chase for missing tax documents.

What changed. The form count is a count. The percentage was removed because nobody could say what it measured.

Before. Single-handedly drove $2M in revenue growth.

After. Closed the two largest deals in the team’s year, about two million dollars together, as lead rep on both, with a solutions engineer on the technical calls.

What changed. The deals are in the CRM. “Single-handedly” became who else was in the room, which is the more believable story and the one that survives a reference check.

How to do this to your own resume

1. Find the change. For each job, ask what was different because you were there. Not what you did all day. What changed. If nothing comes, ask what would have gone wrong had you not shown up. That is your result.
2. Name the scope. Count the things: people, locations, tickets, accounts, students, servers. The count lives in a schedule, a roster, a report or a system you used every day.
3. Put the result first. Rewrite so the change sits in the first six words. Cut the setup.
4. Check every number. Each one needs a source you could name in an interview. If the source is “I estimated,” write the specific instead of the number. Every number kept in the examples above passed this test. The ones that could not were deleted.
5. Read it as the hiring manager. Would they believe it, and would they ask about it? The second one is the goal.

Let Jen do the first one with you

Upload your resume to the free resume grader and the report will call out the weakest line on the page and why it is weak. Ask Jen to rewrite it. She works only from what is already in your document, shows you the before and the after side by side, and you decide whether it goes in. Your first edit is free. If you want to work through the rest of the page with her, plans are here.

Questions people ask

How many bullets per job? Three. Five if you must. More reads as hiding weakness in volume, fewer reads as incomplete.

How long should a bullet be? One line, two at most. If it needs three, it is two bullets, or one bullet plus setup you can cut.

Does every bullet need a number? No. Every bullet needs a specific. Numbers are the easiest specifics and counts are the easiest numbers, but “the checklist the shift still uses” is a specific with no digit in it.

Should every bullet start with a verb? Start with the change. Usually that is a verb. What matters is that the first six words carry the point.

Can I use AI to write my bullets? Use it to ask you questions, not to answer them. The moment it supplies a number or an adjective you did not give it, you have a bullet you cannot defend.