Tool
Resume Bullet Point Builder
A strong bullet says what you did and what changed because of it. Enter the four ingredients and the tool arranges them in three common patterns. Underneath, paste any bullet to check it against five simple rules.
Past tense. Start typing for suggestions.
Check a bullet
This tool runs in your browser. What you type or open here is not uploaded or stored on a server.
The pattern behind a good bullet
Most strong bullets have the same skeleton: action + what + how + result. Not every bullet needs all four parts, but every bullet needs the first two, and the best ones on a page have the fourth.
- Action: a specific past-tense verb. "Negotiated" tells a reader more than "worked on".
- What: the thing you acted on, with its scale: three depots, a 12-person team, 200 invoices a month.
- How: the method or tool, when it is part of what the employer wants.
- Result: what changed, as a number where you truthfully can: time saved, errors cut, money earned, people served.
See how to write bullet points and how to quantify achievements, including what to do when you have no figures.
What the checker looks for
- Starts with an action verb rather than "responsible for" or a noun.
- Contains a number or another measurable result.
- Is between about 10 and 30 words, so it fits on one or two lines.
- Avoids vague phrases such as "helped with" and "various".
- Leaves out "I", "my" and "we", as resume bullets usually do.
Questions and answers
What if I do not have numbers?
Use scale and frequency instead: how many people, how often, how large. "Trained four new starters" and "handled the weekly payroll for 60 staff" are both measurable without a percentage. Never invent a figure; an estimate you can explain ("roughly 40 calls a day") is fine.
How many bullets should each job have?
Three to five for recent, relevant roles and one or two for older ones. If a job needs more, check whether some bullets describe duties rather than results and cut those first.
Should bullets be in the past or present tense?
Past tense for previous jobs. For your current job, either use the present tense for ongoing duties and the past for completed achievements, or use the past throughout. Consistency within a job is what matters.
Should I use past tense or present tense for my action verbs?
Use **past tense** (Built, Reduced, Automated, Led) for all previous jobs—and even for completed projects at your current job. Use present tense (Maintain, Lead, Oversee) only for ongoing day-to-day responsibilities in your current role.
How many bullet points should I list under each job on my resume?
Use **4 to 6 bullets** for your current and most recent relevant role, **3 to 4 bullets** for the role before that, and **1 to 2 bullets** for older or junior roles from 7+ years ago.
How long should a single resume bullet point be?
Keep each bullet to **1 to 2 lines** (roughly 14 to 28 words). Bullets that wrap onto a 3rd or 4th line look like dense paragraphs and get skipped during a quick scan.
Worked example: Turning a vague duty ('Responsible for API testing') into a quantified bullet
Recruiters scan experience bullets in seconds looking for Action + Scope/Tool + Measurable Outcome. Compare the before and after for a software QA engineer:
- Weak duty statement: "Responsible for testing backend REST APIs and logging bugs in Jira." (Uses passive "Responsible for", names no scale, and states no outcome.)
- Inputs entered into the builder:
- Action verb:
Automated - What you worked on (scope & tools):
210 REST API contract and negative-boundary test cases using Java and RestAssured - Result / what changed:
catching 18 schema regressions pre-merge and cutting release sign-off time by 40%
- Action verb:
- Completed bullet (25 words): "Automated 210 REST API contract and negative-boundary test cases using Java and RestAssured, catching 18 schema regressions pre-merge and cutting release sign-off time by 40%."
Limits and what this tool cannot do
- Never invent fake percentages or metrics: If you do not have an exact percentage (
40%), use concrete operational facts you actually know—such as the number of endpoints tested (35 endpoints), release cadence (bi-weekly sprints), team size (cross-functional squad of 6), or what the work prevented (eliminated manual CSV reconciliation). - Checks single bullets (not overall resume layout): Once you refine your bullets here, assemble your full career history in the Resume Builder.