How to write resume bullets with real impact
Turn vague duties into clear bullets: verbs, context, numbers when you have them, and what to do when you do not.
What a good bullet does
A useful bullet answers: what did you do, in what context, and what changed? It doesn’t need corporate poetry. It needs a verb and enough detail that a stranger isn’t guessing.
A simple pattern
Start with a verb. Add the object. Add a tool or audience if it matters. Add a number only when it’s true.
- Built a fee reminder script in Python that emailed 30 club members before each event.
- Redesigned the checkout screen in Figma; cut the form from 9 fields to 5 for the pilot.
- Reconciled monthly stock counts in Excel for a 200-SKU campus store inventory.
When you don’t have metrics
Don’t invent “increased engagement by 300%.” Use scope instead: team size, duration, users in a demo, lines of a process you owned, courses you supported. “Presented to a panel of 4 faculty” is honest. “Revolutionized learning outcomes” is not.
Words that usually waste space
- Responsible for… (say what you did).
- Various / multiple (be specific or drop it).
- Successfully / diligently (the verb already implies you did it).
- Helped with… (name your part).
- Passionate team player (save personality for the interview).
Duty vs impact
Duty: “Worked on the company website.” Impact: “Shipped the pricing page in Next.js with the design team; page went live for the August launch.” Same job, clearer proof.
How many bullets
Two to four per role or project on a one-pager. If every bullet is a soft skill, cut half and replace with one concrete line. For project-heavy resumes, see projects for freshers.
Quick self-check
- Can you talk about this bullet for two minutes without freezing?
- Would a classmate know what you meant?
- Did you start with a verb?
- Did you avoid copying the JD word salad?