Specific does not always mean numerical
Numbers are useful when they are accurate and meaningful, but a bullet can be strong without them. Recruiters also need to understand the problem, your contribution, the complexity of the work, the people involved, and what changed.
Invented percentages weaken credibility. If you cannot explain where a number came from, leave it out.
Build the bullet from four parts
- Context: the team, customer, project, or problem
- Action: what you personally did
- Method: the tool, skill, process, or decision you used
- Outcome: what became clearer, faster, safer, easier, more consistent, or ready for the next step
Use honest forms of scale
Scale can be described through scope instead of a fabricated result. You might name the number of stakeholders, documents reviewed, product areas supported, locations covered, deadlines met, workflows documented, or tools integrated—only when those details are true.
Qualitative outcomes can also be concrete: reduced ambiguity, created a repeatable process, enabled a handoff, improved visibility, supported a launch, or resolved a recurring issue.
Audit every bullet before using it
- Can you explain the situation and your contribution in an interview?
- Does the opening verb describe what you actually did?
- Is the method specific enough to distinguish the work from a generic responsibility?
- Does the outcome follow logically from the action?
- Would a former colleague recognize the bullet as an accurate description?