Contents
Part 1: A resume that gets read

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.

Weak
Built seller features for shop creation, product management and order tracking.
Strong
Kept shop-level inventory separate from a shared product catalogue, and recorded every order status change in a history table for auditing.
Weak
Implemented role-based authentication.
Strong
Built 4 roles (customer, seller, manager, admin) with server-side role checks in every Server Action, not only hidden buttons in the UI.
Weak
Developed a project management application.
Strong
Built a project and issue tracker where every query is scoped to the signed-in user’s projects, so members never see another team’s issues.
Weak
Worked on the checkout page.
Strong
Wrapped checkout in a database transaction with a conditional stock decrement, so two buyers can’t purchase the last unit.
Weak
Designed a responsive dashboard.
Strong
Built role-specific dashboards with loading, empty and error states on every data view.
Weak
Responsible for fixing bugs during internship.
Strong
Fixed 20+ UI bugs reported by QA and cut the admin page load from 4.1s to 1.8s by lazy-loading charts.

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.

Only write what you can defend

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.