9 min read
Your top bullet still opens with *Responsible for weekly reports* and the metric sits in word fourteen. That's why interviews stall even when you've got the right title. Achievement lines win when the verb, scope, and outcome land in the first eight words, not when you bolt a percentage onto a duty sentence at the end. It isn't a keyword problem until the line proves you shipped something.
Check your resume for free against the posting, then compare your bullets to the rubric below. Parsers in Workday and Greenhouse attach keywords to experience rows. Humans skim three bullets. Weak duty language fails both passes, and you won't fix that with a prettier font. You'll need verb-first proof, not another template swap.
Below: the standard bullets get judged against, six before/after pairs across different roles, what weak versions share, and a copy-paste formula you can edit in ten minutes. No generic "quantify everything" lecture. Just lines you can paste tonight.
Job searching is draining. You don't need another pep talk. You need bullets that prove you moved a number, shipped a thing, or fixed a process someone else noticed.
And if you're career changing, achievement bullets matter more because your title won't carry you. The line has to show transferable proof, not a copy of the old job description.
Quick Wins
- Lead bullet one with a past-tense verb, not *Responsible for*.
- Put scope (team size, budget, volume) before the outcome.
- Name the tool from the posting once in your current role.
- Cut any bullet longer than two lines on an 11-point PDF.
The rubric achievement bullets are judged against
When a recruiter opens a profile in Greenhouse, the scan isn't creative writing. Four slots need to fill in order: strong verb, what you owned, how big the work was, what changed. Duty bullets skip straight to tasks and bury the outcome. Achievement bullets answer *so what* before anyone scrolls.
The four-slot test: Verb · Scope · Action · Outcome. If outcome is missing, it's a job description line. If scope is missing, I can't tell junior from senior. If the verb is *helped* or *assisted*, ownership is unclear.
Parsers score the same text humans skim. A bullet that says *Managed social media* might match the keyword *social media* but won't rank above a line that says *Ran Instagram and LinkedIn for three product lines; lifted engagement 22% in H1*. The second line carries tool names and a number the system can index.
Read why weak bullet points get ignored for the symptom side when your file parses fine but callbacks stay flat.
Numbers inside examples below are illustrations of strong lines, not market statistics. Use your own defensible figures in the final file.
Edge case: brand-new grads with internship-only proof. One internship bullet with scope and outcome beats five club membership lines. *Compiled weekly sales reports for 12-store region; flagged $40K inventory gap* beats *Member of finance club.*
Edge case: managers who did the work through others. Name the team size and the metric the team moved. *Led six analysts on month-end close; cut reconciliation errors 18% in two quarters* keeps your leadership visible without hiding behind *oversaw team activities.*
Hybrid and remote roles use the same rubric. Location doesn't change what proof looks like. Outcome and scope still need to sit above the fold in bullet one.
How to write resume achievements: six before/after pairs
Each pair below is a composite from files I see weekly. Swap the tools and numbers for yours. Keep the structure: verb first, scope early, outcome before the line wraps.
Marketing coordinator
Before: Responsible for email marketing campaigns and social media posts.
After: Ran HubSpot lifecycle email for three SaaS lines; lifted MQLs 22% in H1 2025 while holding unsubscribes under 0.4%.
The weak line lists channels without proof. The strong line names the platform, scope (three lines), and two outcomes recruiters can repeat in a intake call.
Software engineer
Before: Worked on backend services using Python and AWS.
After: Built Python FastAPI checkout service on AWS ECS; cut p95 latency from 840ms to 210ms for 120K daily orders.
Stack keywords sit inside action, not a comma list. The latency drop and order volume tell me seniority without reading your title twice.
Registered nurse (med-surg)
Before: Provided patient care on a busy hospital unit.
After: Cared for 5 to 6 med-surg patients per shift on 32-bed unit; precepted four orientees and maintained 96% patient satisfaction scores in 2025 audits.
Clinical bullets can quantify load, teaching, and quality without inventing recovery rates you cannot source. Patient load and precepting count are standard scope markers hiring managers expect.
Operations manager
Before: Oversaw warehouse operations and managed staff schedules.
After: Ran 85-person warehouse shift across two sites; reduced mis-picks 14% in Q3 by redesigning pick-path labels and retraining leads.
*Oversaw* hides who did the redesign. The after line shows you changed a process and attached a metric a plant manager will ask about.
Customer support representative
Before: Handled customer calls and resolved tickets in Zendesk.
After: Closed 55 to 60 Zendesk tickets daily with 94% CSAT; built 12 macro templates that cut handle time 11% for a 10-agent pod.
Volume, quality score, and a process improvement in one line. Support leaders scan for all three before they ask about schedule flexibility.
Financial analyst
Before: Prepared financial reports and supported budgeting process.
After: Built rolling 13-week cash model in Excel for $180M division; surfaced $2.1M variance two weeks before close, enabling early vendor renegotiation.
Finance bullets fail when they stop at *prepared reports*. Tie the model to division size and a decision the number enabled.
Copy-paste achievement formula
Copy-paste this block and fill the brackets for your current job:
[Past-tense verb] [what you owned] using [tool from posting]; [outcome metric] in [timeframe].
Example slots:
Verb: Built · Ran · Cut · Launched · Reduced · Automated
Scope: $ budget · N-person team · N stores · N tickets/day
Outcome: % change · $ saved · time reduced · error rate
Full line template:
[Verb] [deliverable] for [scope]; [metric change] in [quarter or year].
Second bullet template (process win):
[Verb] [process] by [action]; [metric] for [team or region].
Rewrite checklist before save:
1. Delete *Responsible for* and *Duties included*
2. Move any number from word 12+ to word 6 or earlier
3. Name one posting keyword in bullet one or two
4. Trim past two lines at 11-point Calibri
5. Scan file against posting text after edits
Pair with how ATS interprets numbers on resumes when your metrics parse but match scores stay low.
Start with your current role only. Rewrite bullets one through three tonight. Older jobs can keep one proof line each until you hear back from this week's applications.
If a bullet still feels thin after the formula, ask what would have broken if you had not done the work. Late shipments, audit findings, and escalations are outcomes even when you never tracked a dashboard.
What weak achievement drafts share
Outcome parked at the end. Recruiters skim the first eight words. If the metric is the last clause, it might as well be missing.
Duty verbs. *Managed, handled, assisted, supported* without scope read as junior filler.
Keyword comma dumps. *Salesforce, HubSpot, SQL, Tableau* at the tail of a bullet is a skills list, not proof.
Team wins with no *I* boundary. *We increased revenue* tells me the team did something. Name your slice.
Edge case: highly regulated roles where outcomes are confidential. Use banded figures or scope markers you can defend: *Supported SOX testing for $400M revenue segment; cleared 38 controls with zero material exceptions.*
Edge case: contractors with short tenures. One strong bullet per contract beats padding to five lines of task copy. Dates plus one outcome line prove you shipped in weeks, not months.
Passive voice. *Was tasked with* and *was responsible for* push you to the background.
Adjective stacks. *Significantly improved* without a number is still vague.
Duplicate metrics. Repeating the same 15% win in summary and three bullets wastes scan time.
Burying the title keyword. If the req says *project manager* and your bullets never show a project shipped, the title match alone won't carry.
This won't fix applying ten levels above your scope. It stops a qualified candidate from looking like they only ever held the job description.
Test bullets against the posting
After you rewrite bullet one, scan the upload against the job description. Fix missing duty terms only after the achievement structure is in place.
Building from scratch? Build a single-column resume with achievement slots under each employer before you tune keywords.
Strong bullets still need a readable file. A metric-rich line inside a two-column Canva PDF may never attach to the job row. Export plain, then decorate only after paste order passes.
Rewrite bullet one tonight
Learning how to write resume achievements is mostly subtraction. Delete the duty opener, pull the number forward, name the tool once, and stop when you hit two lines. The before/after pairs above are the target shape, not inspiration quotes.
Open your current role. Paste the formula. Swap one weak bullet. Run the checker. Apply with that file before you rewrite the whole work history and never hit submit.
I've screened stacks of these in Workday and Greenhouse, and the file that wins puts proof in bullet one, not bullet six. Move your best line up before you add a fourth adjective.
When the req asks for a letter, generate a cover letter that repeats one metric from bullet one instead of re-listing every duty.
Save a master bullet bank in a separate doc. Tailor the top three lines per posting without rewriting your entire career every Sunday night.
If you're stuck on numbers, pull last quarter's review, ticket exports, or project retro notes. Candidates forget they already documented the win in email. Mine that thread before you guess a percentage.
Achievement bullets age. Update bullet one when you change tools, get promoted, or finish a project that moved a metric. A stale win from three years ago in the top slot signals you haven't shipped lately.
Read more
Frequently asked questions
Aim for three to five under your current or most relevant role. Older jobs can carry one or two. Recruiters in Workday and Greenhouse skim the top three bullets first. If bullet one is still a duty line, they may never scroll to bullet four where your best metric hides.
Use defensible ranges or scope when you cannot cite a hard figure. Volume handled, team size, budget band, or time saved in weeks still beats a duty sentence. Never invent a percentage you cannot explain in an interview. A range you can defend beats a fake precision number.
Put proof under the employer where the work happened. The summary can preview one headline win, but the bullet under the job title is what parsers attach to that role row. Duplicating the same metric in summary and experience wastes space without adding a second proof point.
Yes, when the keyword names a tool or duty you actually used. Drop the posting phrase into the action or scope slot of the formula, not as a comma list at the end. One natural mention in bullet one or two on your current job beats six keyword-stuffed lines that read like a skills dump.
One or two lines in a single-column PDF at 11-point Calibri or Arial. Lead with the verb and outcome in the first eight words. If you need a third line, split into two bullets or cut the setup sentence. Long paragraphs disappear on mobile preview in Greenhouse.