Most resumes fail at the same place.
Not formatting. Not keywords.
Bullet points.
Specifically: bullets that describe what someone was around, not what they did. If your bullets start with “responsible for,” “supported,” or “helped with,” you’re leaking signal.
Recruiters don’t care what your job description said. They care what changed because you were there.
This article is about fixing that.
Tasks don’t sell. Outcomes do.
Here’s the harsh truth: Tasks are assumed. Achievements are evaluated.
If your title is “Product Manager,” everyone already assumes you:
- Worked with engineers
- Attended meetings
- Wrote docs
- Talked to stakeholders
Repeating those tasks doesn’t differentiate you. It just confirms you existed.
Achievements answer a different question:
Why should we interview this person?
Why STAR matters (and why most people misuse it)
Yes, we’re going to talk about STAR.
No, we’re not going to tell you to write STAR bullets.
STAR is a thinking framework, not a resume format.
Used correctly, STAR forces you to:
- Stop being vague
- Identify real impact
- Remove fluff
Used incorrectly, it creates unreadable bullets nobody wants to scan.
STAR, stripped down for resumes
Here’s how to use STAR internally - then throw most of it away.
- S - Situation: What was broken, risky, slow, or unclear?
- T - Task: What were you actually accountable for?
- A - Action: What you did (not “we” unless it matters)
- R - Result: What changed? Measurably, if possible.
You use STAR to extract signal. Then you compress it into one tight bullet.
Before - After (real examples)
Example 1
Task-based (bad):
Responsible for managing cross-functional projects
This says nothing.
STAR thinking (internal):
- Situation: teams were misaligned, deadlines slipping
- Task: align product, design, and engineering
- Action: introduced weekly prioritization syncs
- Result: shipped on time, reduced rework
Achievement-focused (good):
Led cross-functional prioritization that reduced delivery delays and cut rework across teams
Same job. More signal.
Example 2
Task-based (bad):
Worked on customer analytics and reporting
Empty.
STAR thinking (internal):
- Situation: leadership lacked visibility into churn
- Task: surface actionable metrics
- Action: built dashboards, standardized reporting
- Result: churn drivers identified, decisions accelerated
Achievement-focused (good):
Built customer analytics dashboards that identified key churn drivers and informed retention strategy
Now we’re talking.
The result is not always a number (but try anyway)
People freeze up here.
“I don’t have metrics.” “Yes, you do.”
They’re just not labeled as metrics yet.
Results can be:
- Time saved
- Errors reduced
- Scope clarified
- Risk avoided
- Decisions accelerated
If something became better, faster, clearer, cheaper, or safer, that’s a result.
For a deeper dive into finding metrics, see Quantifying Your Impact: The Numbers Game.
Turning soft impact into concrete bullets
Vague:
Improved team communication
Concrete:
Improved cross-team communication by introducing a shared planning doc used by product, engineering, and sales
Still no number - but now it’s real.
Action verbs matter (but they won’t save weak bullets)
Strong verbs help. They don’t replace substance. For verb recommendations by career level and industry, see Resume Action Verbs That Make Recruiters Notice.
Better verbs:
- Led
- Built
- Owned
- Delivered
- Reduced
- Launched
Weaker verbs:
- Helped
- Assisted
- Supported
- Participated
If you didn’t own it, be honest. But if you did - say so.
A note for early-career candidates: If you were genuinely in a supporting role, don’t inflate your ownership. Instead, focus on what you specifically contributed: “Coordinated logistics for 15 client onboardings, maintaining 100% on-time delivery” is honest and strong without overclaiming.
One bullet = one idea
This is where people overstuff.
Bad bullets try to do everything:
Led roadmap planning, stakeholder communication, execution, and reporting across multiple teams
That’s four bullets hiding in one.
Split them. Prioritize impact.
How many bullets per role?
Rule of thumb:
- Recent roles: 4-6 bullets
- Older roles: 2-3 bullets
If you need 8 bullets to explain a role, you’re not editing hard enough.
Do this, not that (summary)
Do this:
- Use STAR to think, not to write
- Lead with action + result
- Be specific
- Compress aggressively
Not that:
- Describe responsibilities
- Write mini job descriptions
- Use filler verbs
- Hope recruiters infer impact
Where tools help - and where they don’t
AI tools are great at:
- Rewriting bullets
- Tightening language
- Spotting vague phrasing
They’re bad at:
- Knowing what mattered
- Guessing real impact
- Inventing outcomes (don’t let them)
Tools like Resumes Coach work best when you bring real substance and let the tool sharpen it — not fabricate it.
Final check before you move on
Read each bullet and ask:
If this line disappeared, would anyone notice?
If the answer is no, cut it.
Your resume isn’t a record of employment.
It’s a highlight reel.
Once your bullets are strong, make sure your formatting doesn’t undermine them.
Make it worth watching.
Get per-bullet scoring on your resume. Upload your resume to Resumes Coach and see which bullets are landing — and which need work — with AI-powered rewrite suggestions.