Writing bullets that prove something
A bullet should say what you did, how it works, and one detail that makes it checkable. Feature lists prove nothing.
The formula
Verb + what you built + how it works or why + one concrete detail. The detail is usually a number: roles, entities, users, pages, load time, bugs fixed.
Verbs to start with
Built, Implemented, Modelled, Designed, Deployed, Integrated, Optimised, Reduced, Fixed, Migrated, Refactored, Wrote, Shipped, Contributed.
Openers to delete
“Worked on”, “Responsible for”, “Helped with”, “Involved in”, “Participated in”, “Familiar with”, “Learned”.
Numbers you already have
Freshers think they have no metrics. You do:
- Number of user roles, database tables or entities, API routes, pages or screens.
- Lighthouse score before and after, page load time, bundle size.
- Bugs fixed, components reused, users on a live deployment, merged pull requests.
One idea per bullet
If a bullet runs past two lines, it holds two ideas. Split it or cut the weaker half.
Every bullet is an interview question waiting to happen. “Wrapped checkout in a transaction” will be followed by “show me”. If you used AI tools to build the project, that is normal in 2026, but you must be able to open any file and explain it. Write bullets about the parts you understand best.