The STAR method, with worked examples by role

The STAR method is the most-cited framework in resume writing: Situation, Task, Action, Result. It comes up in every advice column, every recruiter training, and every "5 tips for better bullets" listicle. Despite the saturation, the average resume bullet still reads:

Responsible for managing the team's reporting workflow.

That's not STAR. That's not anything. This guide is about what STAR done well actually looks like — and the small adjustments that move bullets from "responsible for" to "shipped this, here's the proof".

What STAR actually asks of you

The four parts:

• Situation — the context the work happened in. Where? What was at stake?
• Task — what you were specifically responsible for inside that context.
• Action — what you did. The verb-led specifics.
• Result — the measurable outcome.

On a resume, you don't write all four in full sentences — that's interview-prep STAR, used for behavioural questions. Bullet STAR is a compressed form: usually Action + Result first, with Situation and Task implied or in a short prefix.

The pattern that consistently works:

[Strong verb] [specific action, with context] → [quantified result, with timeframe or scale].

That's it. Action verb up front, concrete context in the middle, measurable outcome at the end. Three components, one line, no fluff.

What "wrong" looks like

Two failure modes dominate weak STAR bullets:

1. All Task, no Action or Result.

"Responsible for the team's quarterly planning process."

This describes a job duty, not an achievement. Anyone in the role would write the same line. It tells the reader nothing about how well you did it.

2. Action without Result.

"Led the migration to a new CRM system."

You did a thing. So what? Did the migration succeed? Did it improve anything? Without the result, the bullet is half a story.

The fix is the same in both cases: ask "what changed because of me?" and put the answer at the end of the bullet.

Worked examples by role

The same pattern across five different roles. Each shows the weak version → the STAR version, so the transformation is visible.

Software engineer

Weak: Worked on the search service for the e-commerce platform.

STAR: Redesigned the search service's ranking pipeline (Elasticsearch + custom relevance scoring), cutting p95 latency from 480ms to 90ms and lifting search-driven conversion 11% in the first month.

What changed: a specific subsystem (ranking pipeline), specific tech (Elasticsearch), two quantified outcomes (latency cut, conversion lift), a timeframe (first month).

Product manager

Weak: Led the launch of a new checkout flow.

STAR: Shipped a redesigned mobile checkout (single-page, Apple Pay default) across iOS + Android, growing mobile conversion 18% and reducing support tickets about checkout failures by 34% within six weeks.

What changed: scope (mobile, two platforms), the what of the redesign (specific design decisions, not "redesigned the checkout"), two quantified outcomes on two different axes (revenue + cost).

Marketing manager

Weak: Managed the email marketing programme.

STAR: Rebuilt the lifecycle email programme around behavioural triggers (Customer.io + Segment), lifting activation-to-paid conversion 22% and raising monthly recurring revenue contribution from email channel by $180k.

What changed: a specific mechanism (behavioural triggers), specific tools (Customer.io, Segment), a funnel-stage metric (activation-to-paid), and a dollar outcome.

Operations

Weak: Improved warehouse picking efficiency.

STAR: Redesigned the warehouse picking workflow (zone-based, batch-picked, scanner-driven), reducing average pick time from 4.2 to 2.6 minutes per order and cutting mis-pick rate by 41% over two quarters.

What changed: three specific design decisions in one parenthetical, two before-and-after metrics, a clear timeframe.

Sales

Weak: Closed deals with enterprise accounts.

STAR: Closed $4.2M in new ARR across 9 enterprise accounts in FY24 (avg ACV $470k, sales cycle 4.2 months), exceeding quota by 38% and landing the largest single deal in the team's history.

What changed: total dollar outcome, deal count, average size, sales cycle context, comparison to quota, and a "first/largest" superlative.

When you don't have numbers

Not every achievement is measurable. The fix isn't to invent numbers — it's to substitute comparative scale for absolute scale:

• "Largest single migration in the company's history"
• "First successful pilot of zone-picking in our network"
• "Adopted by all three regional teams within the first quarter"
• "Used as the default playbook for subsequent migrations"

These give the reader scale and validation without a percentage. Use them when the raw data isn't available — but not as an excuse to skip the work of finding numbers when they exist.

The Verb → Context → Result test

Before submitting a CV, run every bullet through this three-question test:

1. Does it start with a specific verb? (Not "responsible for", "worked on", "helped with".)
2. Does it describe what you actually did, with enough specificity that someone in your industry would recognise the work?
3. Does it end with a measurable or comparative result?

If all three are yes, the bullet is doing its job. If one or more is no, rewrite it. A resume with 12 bullets and 6 STAR-quality lines beats one with 24 generic ones every time.

The honest summary

STAR isn't a magic framework. It's a discipline for asking the same three questions about every line on your CV: what did you do, in what context, with what outcome? The answer should be visible without the reader having to infer.

Most weak resumes don't fail because the candidate didn't achieve anything. They fail because the achievements got buried in passive language. STAR is the tool for getting them back out.