How to Write Resume Bullets for the Job You Actually Did
Most resume bullets describe the role, not the work. The five-part formula that captures what you actually did and why it mattered.
You sit down to update the resume. You stare at the role you have been in for two years. You start typing: "Responsible for..." and immediately realize this is going to be a list of things any person in your job would write. It does not capture what you actually did. It does not capture what was hard, or what you decided, or what changed because you were the one in the seat.<br/><br/>The reason most resume bullets are flat is that they describe responsibility instead of work. Responsibility is what was assigned. Work is what you actually did with it. The fix is a five-part formula that pulls the work out.
The five elements of a bullet that earns interviews.
Start with a strong verb that names the action
"Responsible for" is not a verb, it is a job description. Replace with verbs that name the actual move: led, designed, negotiated, shipped, reduced, scaled, recovered, launched, simplified, secured. The verb should be specific to what you did, not generic to what someone in your role might do. "Led" is fine if you led; "managed" is fine if you actually managed people. Avoid "involved with" or "participated in" — those describe attendance, not contribution.
Name the scope: what, where, how big
After the verb, give the reader enough to picture the scope. "Led migration of 40-team monorepo to a new build system" is concrete. "Led infrastructure improvements" is vapor. The reader should be able to tell roughly how big this was without asking. Numbers help: number of users, dollars, teams, regions, months. Even rough numbers are better than no numbers — "40 teams" is good even if it is a 35-to-45 estimate.
Add the constraint or judgment that made it hard
What you did is half the bullet. What was hard about it is the other half. "Migrated the system in 90 days while keeping the production deploy cadence at twice-weekly" — the second half tells the reader why this was a real piece of work and not a routine task. Constraints are: deadlines, budget limits, missing resources, simultaneous demands, technical risks. Without the constraint, the bullet describes anyone with the title.
End with the outcome in numbers when possible
What changed because you did the thing? Reduced build times by 60 percent. Cut customer support volume by a third. Brought in $1.2M of new revenue. Outcomes anchor the rest of the bullet — they tell the reader the work shipped and mattered. If you genuinely cannot get a number, use a comparison instead: "the first time the team had hit the quarterly target two cycles in a row." Concrete language beats vague impact claims.
Cut everything that is not the bullet
Most bullets are too long. They include context the reader does not need, hedges, multiple verbs trying to do too many jobs. Read each bullet and ask: if I cut this clause, does the meaning survive? If yes, cut it. The strongest bullets are one line, one verb, one piece of work, one outcome. Recruiters skim — every word that does not earn its place is a word that pushes the important stuff off the page.
Turn vague work descriptions into resume bullets that interview well.
Add accomplishments however you remember them. Brag Sheet Builder transforms them into power statements with verb upgrades and runs you through metric rounds to add real numbers.