The “Responsible for…” tax
Every time a bullet starts with “Responsible for,” it quietly costs you a line of credibility. Here's the cheaper way to say the same thing.
“Responsible for managing the social media accounts.” It sounds like work. It isn't. It's a job description — a list of things that were assigned to you — and a recruiter reading fifty CVs before lunch has learned to skim straight past it.
The phrase quietly signs away your best asset: proof that you actually did the thing and something happened as a result. Being responsible for a budget and cutting that budget by 18% are two completely different claims, and only one of them gets you a call.
What the phrase hides
“Responsible for” describes the boundary of a role, not your performance inside it. It answers “what was your remit?” when the recruiter is silently asking “what changed because you were there?” Those are different questions, and the CV that answers the second one wins.
The swap
Replace the responsibility with the result. Start the bullet with a strong past-tense verb, name what you did, and attach a number wherever one honestly exists.
- Before: Responsible for the monthly newsletter. → After: Grew the monthly newsletter from 3,000 to 11,000 subscribers in a year.
- Before: Responsible for customer support. → After: Cut average first-response time from 9 hours to 40 minutes across a 4-person team.
- Before: Responsible for supplier relationships. → After: Renegotiated three supplier contracts, saving SAR 240k annually.
Nobody gets promoted for being responsible for something. They get promoted for what happened next.
When you don't have a number
Not every task has a clean metric, and inventing one is worse than having none. When there's no number, lead with scope and outcome instead: what you built, who used it, what problem it removed. “Built the onboarding checklist now used by every new hire in the branch” has no percentage in it and still beats “Responsible for onboarding.”
Run one pass through your CV and delete every “Responsible for.” You'll find that half of them were hiding a real achievement, and the other half were hiding the fact that there wasn't one — which is useful to know before the interview, not during it.