Show Impact, Not Responsibilities
A job description lists what you were supposed to do. A resume should prove what changed because you did it. The gap between the two is where offers live.
Here's a test. Cover the company names on your resume and read the bullets. Could they belong to anyone in your role? If yes, you've described the job, not your performance in it.
Responsibilities are the floor, not the story
"Managed social media accounts" tells a recruiter what you were assigned. It says nothing about whether you were good at it. Everyone in the role managed the accounts. The question the resume has to answer is: and then what happened?
Find the number hiding in the work
Almost every responsibility has a measurable shadow. If you can't measure the outcome, measure the input — scale, frequency, or speed:
- A percentage change: activation, retention, error rate, revenue.
- A raw count: users, tickets, releases, people, dollars.
- A comparison: faster than, ahead of schedule, under budget.
A number does two jobs at once. It proves the claim, and it forces you to be specific — vague verbs quietly disappear when a real figure shows up beside them.
When you truly can't quantify
Some work resists numbers. Then describe the change in state: what was broken before, what was true after. "Untangled a release process that had blocked the team for months" carries impact even without a metric, because it names a before and an after.
Score → Impact reads each bullet and tells you which ones still sound like duties, so you can find the missing number before a recruiter notices it's gone.
Responsibilities tell a reader what you were given. Impact tells them what you're worth. Only one of those gets you the interview.
