A resume bullet should help a reader understand your contribution. A useful pattern is action, context, and outcome: what you changed, what problem it addressed, and what became possible afterward.
Replace broad claims with evidence
- Name the feature, system, or user workflow rather than saying you were responsible for everything.
- Describe your own part when the result came from a team.
- Use a number only if you can explain how it was measured and what it represents.
Keep the bullet easy to scan
For example, replace 'worked on the dashboard' with a truthful description of the component you built, the data it presented, and the decision it helped a user make. If you do not know a business metric, describe the shipped behavior instead.
Review each bullet for accuracy, plain language, and relevance to the role. Remove repeated verbs and internal team acronyms that an outside reader will not recognize.