How to Write Resume Bullet Points

Strong resume bullet points describe what you specifically did and, where you genuinely know it, the outcome -- not a vague summary of your job description.

A useful structure: Action + Task + Technology + Result

Start with a strong action verb, describe the specific task, mention the relevant technology or method, and close with a result if you actually have one to report.

Weak: "Responsible for backend APIs." Stronger: "Built and maintained REST APIs in Java and Spring Boot serving the core product's checkout flow."

Notice the stronger version doesn't invent a number -- it adds specificity about scope and technology instead, which is often what's missing from a vague bullet in the first place.

Only add a metric if you actually have it

If you genuinely know a percentage improvement, a dollar figure, or a scale (number of users, requests per second, team size), include it -- it makes a bullet far more concrete. But never estimate or invent a number to make a bullet sound stronger. An interviewer who asks you to explain a number you made up will notice.

Lead with the strongest verb you can honestly use

"Led," "built," "designed," and "reduced" all signal ownership and impact. Weaker phrasing like "helped with" or "was involved in" undersells your actual contribution -- if you did the work, say so directly.

Keep it to one line where possible

A bullet point that runs three lines is hard to scan quickly. Aim for a single, information-dense sentence per bullet.

Avoid generic filler phrases

Phrases like "team player," "hard worker," and "detail-oriented" are subjective claims that carry little weight on their own. Specific accomplishments demonstrate those qualities far more convincingly than stating them directly.