How to write resume achievements: put the result first

A friend's first resume filled its experience section with "responsible for managing social media," "participated in project development," "assisted the team." It went out to about forty companies and came back silent. We rewrote every line as what changed, what you did, how you did it — two phone screens inside a week.

This piece is only about that section. It is the easiest part of a resume to fill with nothing and the one most worth getting right.

1. Why "responsible for X" is a wasted line

A recruiter — and the search box they are typing into — is looking for outcomes and numbers.

"Responsible for managing social media" carries almost no information. How big was the audience? Did it grow? Did anything reach anyone? The parser finds no keyword worth indexing, and the human cannot tell what you were actually worth.

The fix is structural, not stylistic: move the result to the front of the sentence.

2. STAR with the R first

STAR is familiar: Situation, Task, Action, Result. On a resume, do not write in that order. Lead with the Result — a recruiter spends a few seconds per bullet and decides from the first half of the line whether to read the second.

The pattern: outcome (quantified) + what you did + how.

Scale, change, and method — all visible without reading twice.

3. Where the numbers come from when you think you have none

"But I don't have data" is the most common objection. Three ways out:

1. Find it. Users, revenue, followers, percentage-point efficiency gains, cost reductions — the figures are usually sitting in old dashboards, tickets, and message threads.
2. Compute a proxy. No retention figure? "Supported 200+ customers at a 95% satisfaction score" works if you actually did. No follower growth? "Published 30+ pieces; best-performing one reshared 500+ times."
3. Use a delta. "From X to Y" persuades more than a single figure: "cut response time from 2s to 0.6s" beats "improved response time."

The rule underneath all three: you may estimate, you may not invent. If it will not survive a follow-up question in an interview, leave it out.

4. Work the posting's words into the sentences, don't pile them up

As you write each achievement, use the vocabulary from the job posting. If the ad says "growth," "data analysis," "user retention," your bullet becomes "used analytics to re-target the content mix, driving 40% growth in returning users."

What not to do is add a separate keyword block at the bottom. Stuffed keyword lists read as spam to a human and add nothing for the parser, which already indexes your bullets. Keywords belong inside sentences, as above.

5. Use AI for the first pass, own the numbers yourself

If the blank document is the problem, get a draft out of a tool. Paste the experience and the job posting into ResuHive and it reorganises the achievements around the posting's language, then reports which of its terms you hit and which you missed.

On my friend's, the posting listed 12 core terms and the original resume hit 4. The missing ones — message queues, microservices — were things he had genuinely worked on and simply never written down. Filling gaps against a real posting beats staring at the page.

The boundary is the same as always: a tool can make a sentence better, but it must not supply employer names, dates or numbers. Those you verify line by line, because those are what get asked about.

6. Three ways this goes wrong

1. The experience has to be real. A tool can phrase the gap; a fabricated number is a landmine with a delay fuse.
2. Don't send one version everywhere. Regenerate and re-match per posting — growth vocabulary for a growth role, operations vocabulary for an operations role.
3. Read the output before sending. Generated phrasing does not always sound like you, and you are the one who has to say it out loud later.

7. Patterns you can copy

• Marketing/ops: Grew [metric] from A to B in X months by [method], lifting [secondary metric] from C to D.
• Engineering: Built [component] serving X daily users; cut [metric] by Y% through [technique].
• Business functions: Led [project] across an N-person group, shortening delivery by Y% and reducing cost Z%.

Substitute your real figures for the placeholders and you have a bullet that does work.