Resume Writing Guide
How to Write Resume Accomplishments That Get Interviews
The difference between a resume that gets callbacks and one that does not usually comes down to one thing: accomplishments versus duties. This guide shows you how to turn "responsible for" into "achieved" — with real examples, common pitfalls, and a method you can apply to every bullet on your resume.
Why accomplishments beat duties every time
Recruiters spend about 7 seconds on a first pass through a resume. In that time, they are asking one question: is this person different, in a concrete way, from the other fifty applications in the stack? A list of duties — what you were supposed to do — cannot answer that question. Every marketing manager runs campaigns. Every engineer ships code. Duties describe the role, not the person.
Accomplishments answer the question directly. They tell the recruiter what you specifically produced, improved, or delivered. They include scope — how big, how many, how fast — and outcome — what changed because of the work. When done right, a single accomplishment bullet communicates more than a full paragraph of duty descriptions.
The payoff compounds. Every bullet on your resume that starts with a strong accomplishment instead of a duty makes the rest of the document feel more credible. And once you have a few accomplishment statements you like, you can reuse them across multiple applications with small tweaks, rather than rewriting from scratch each time.
Duties vs Accomplishments: the core distinction
Duties describe what your job required. Accomplishments describe what you achieved while doing it. Hiring managers already know what a project manager or software engineer does. They want to know what you did differently.
Duty (weak)
"Managed a team of engineers"
Describes the role. True of every engineering manager everywhere.
Accomplishment (strong)
"Led a team of 8 engineers to deliver the payment platform redesign 2 weeks ahead of schedule, reducing checkout abandonment by 23%"
Specific scope, concrete outcome, measurable impact.
A useful test: would this bullet still be true if you replaced your name with a co-worker's? If yes, it is probably a duty, not an accomplishment.
The STAR Method
STAR stands for Situation, Task, Action, Result. It is the most reliable framework for writing accomplishment statements. You do not need to spell out all four elements in every bullet — but thinking through them ensures each bullet has substance.
What was the context or challenge? Set the scene in a few words.
What were you specifically responsible for? Who asked, and why did it matter?
What did you actually do? Lead with a strong verb and be specific about your own contribution.
What was the measurable outcome? Numbers, percentages, or concrete after-states.
In a resume bullet, you typically compress STAR into a single sentence. A template that works: "[Action verb] [what] [for/to whom] [scope], [result with a number]." Example: "Rebuilt the onboarding flow for 12,000 monthly signups, reducing time-to-first-action from 4 days to under 24 hours."
Quantify Everything — and what to do when you cannot
Numbers are the most powerful element of an accomplishment statement. They provide concrete evidence of impact. When you cannot provide exact numbers, estimate conservatively and use qualifiers like "approximately" or "over."
Weak: Improved customer satisfaction
Strong: Improved customer satisfaction scores from 72% to 91% over 6 months
Weak: Reduced costs
Strong: Reduced infrastructure costs by $45K annually by migrating to containerized deployments
Weak: Grew the user base
Strong: Grew monthly active users from 12K to 48K through targeted onboarding optimization
Weak: Led a successful launch
Strong: Led a 6-person cross-functional team to launch Android beta in 9 weeks, reaching 40K installs in month one
Weak: Improved team velocity
Strong: Introduced weekly retros and async specs that cut average feature cycle time from 18 days to 11
If you truly cannot attach a metric, reach for scope instead: team size, customer count, budget, number of projects. "Mentored 6 junior engineers through their first production deploys" is weaker than a revenue number but still far stronger than "Mentored junior engineers."
Strong Action Verbs (and which to avoid)
Start every bullet point with an action verb. Avoid passive constructions like "was responsible for" or "helped with." Use past tense for previous roles and present tense for your current role. Vary your verbs — the same word repeated across bullets makes the page read flat.
Verbs that demonstrate impact:
Verbs and phrases that weaken your bullets:
Every one of those weak verbs can almost always be replaced by the specific action you took. Instead of "Helped migrate," ask: what specifically did you do during the migration? Wrote the rollback plan? Coordinated with three downstream teams? Shipped the first 20 services? That is your action verb.
Common mistakes to avoid
Listing responsibilities in bullet form
Bullets that start with "Responsible for" or "Duties included" are just prose duties dressed up. Rewrite as actions and outcomes.
Burying the outcome
If the strongest part of your bullet is at the end, move it. Lead with what changed, then explain how.
Using buzzwords without substance
"Leveraged synergies to drive innovation" means nothing. Replace with the concrete thing you built, changed, or delivered.
Overstating scope or metrics
Recruiters talk to references. Inflated numbers get caught and poison the whole resume. Be specific and defensible.
Stacking too many metrics in one bullet
Three numbers in one bullet is hard to parse. Pick the strongest, drop or move the rest.
Hiding the team but taking all the credit
For team wins, name the team size and your specific role. "Led a team of 5" is more credible than "Single-handedly transformed the org."
A worked example: turning one week into three bullets
Say you are a product manager who just finished a sprint. Your week looked like this: shipped a pricing page redesign, unblocked two engineers who were stuck on an API spec, and ran user research with 6 customers. Here is how those become real accomplishments instead of a to-do list.
Weak (raw log entry)
"Shipped pricing page redesign"
Strong (resume-ready)
"Shipped a pricing page redesign that lifted trial-to-paid conversion from 6.1% to 8.4% in the first 30 days."
Weak (raw log entry)
"Helped engineers with the API"
Strong (resume-ready)
"Authored the v2 API spec and aligned two downstream teams, unblocking a feature that had been stalled for 3 weeks."
Weak (raw log entry)
"Ran user research"
Strong (resume-ready)
"Ran 6 customer interviews that identified two recurring onboarding drop-off points, which shipped as fixes the following sprint."
The raw log entries took a minute to jot down on Friday. The resume versions took another five minutes, three months later, once you knew the outcomes. This is the core loop of accomplishment-first resume writing: capture cheap, polish when you need to.
Where to go next
Track your accomplishments automatically
HypeUp helps you capture accomplishments as they happen, then generates tailored resume bullets using AI. Stop rewriting from scratch every time.
Start tracking for free