How to Write Resume Bullet Points That Show Results
A bullet should answer one question for the reader: so what? Here is a repeatable way to answer it.
The problem with most bullets
Most resume bullets describe a duty: "Responsible for preparing weekly reports". A reader learns what your job title implied, but not whether you did it well. A good bullet describes an action and its effect, so that two people with the same title look different on paper.
A formula you can reuse
Start with a strong past-tense verb (built, reduced, led, organised, designed, analysed, trained, negotiated). Say what you did in plain words. Add a measure: a number, a percentage, a time saved, a count of people or items, or a before-and-after comparison. If you know how you did it, add the tool or method at the end.
Ten rewrites
| Before | After |
|---|---|
| Responsible for weekly sales reports | Prepared weekly sales reports in Excel for a 6-person team, cutting report time from three hours to one |
| Helped customers with queries | Resolved about 40 customer queries a day by phone and email with a 95 percent same-day closure rate |
| Worked on college website | Built a 12-page college club website in HTML and CSS used by 300 students to register for events |
| Led a team in a college fest | Led a team of 15 volunteers to run a two-day fest with 1,200 attendees, finishing 10 percent under budget |
| Did data entry | Entered and verified 250 records a day with fewer than two corrections per week |
| Taught students | Tutored 8 first-year students in mathematics; 7 improved by at least one grade in the next test |
| Handled social media | Grew a club Instagram account from 400 to 1,500 followers in four months with a weekly posting plan |
| Made a project in Python | Built a Python script that cleans exam result files and reduced manual checking from two hours to ten minutes |
| Managed inventory | Tracked stock for 120 items in a spreadsheet and cut out-of-stock days from six to two a month |
| Participated in a hackathon | Built a working prototype of a bus-timing app with a team of four in 24 hours; shortlisted among 60 teams |
What if you have no numbers?
Many fresher projects and early roles do not come with metrics. You can still show scale and result without inventing anything:
- Count things you did know: number of people in the team, pages, features, items, days, events, customers.
- Use time: "in three weeks", "every Saturday for a semester".
- Say who benefited: "used by the department", "adopted by the next batch".
- Use a comparison: "replaced a paper register with a shared sheet".
- Name the tool or skill: "using Excel pivot tables", "in React".
If a bullet still has no measure, ask: what would have gone wrong if I had not done this? The answer is usually the result.
Wording tips
- Use past tense for finished work, present tense only for your current role.
- Do not start every bullet with the same verb. Build a short list and rotate.
- Keep each bullet to one or two lines. Three to five bullets per role is enough; fewer for older roles.
- Put the strongest bullet first.
- Avoid "responsible for", "worked on" and "helped with" unless nothing else is true.
- Avoid adjectives you cannot prove: "hardworking", "passionate", "excellent".
The ApplyReady resume builder has one bullet per line in each experience and project, and its Review tab checks for empty sections and other common omissions. See also how to write the summary at the top of the resume.
Frequently asked questions
How many bullets should each job have?
Three to five for recent or relevant roles, one or two for older ones. If a bullet does not help the role you are applying for, remove it.
Should bullets be full sentences?
No. Start with a verb and leave out "I". Keep each bullet to one or two lines so it scans quickly.
Can I include numbers from college projects?
Yes, as long as they are true: team size, users, pages, data size, time saved, marks or ranks. Be ready to explain how you counted.
What if I cannot remember exact figures?
Use an honest approximation with a word such as "about", or describe scale in another way (daily, weekly, across three departments). Do not invent precision.
Should I use the same verb many times?
Avoid it. A short list of varied verbs (built, led, reduced, organised, analysed, trained) reads better than repeating "worked on".