How to answer “What's your greatest achievement?”

What they're actually checking

Three things sit underneath this question. First, judgment: what you pick as your greatest achievement tells the interviewer what you consider important, and a candidate who picks a flashy title over real impact is showing you their values. Second, contribution: was this clearly yours, or are you borrowing the team's win? Third, impact: did it actually matter, and can you say how? At senior levels they're also weighing scope and the “so what”, whether your proudest moment moved a number, changed how the org works, or grew people. The achievement is the vehicle; those three signals are the cargo.

The answers that backfire

The invisible-contribution answer (“we shipped a huge platform”) hides what you did and reads as riding the team. The impressive-but-irrelevant story wins on scale but says nothing about whether you can do this job. The activity-without-impact answer describes the work but never lands the result, so it sounds busy rather than effective. Over-humility that buries your role under “the team did it” throws away the question. And the title or credential (“I got promoted to senior”) isn't an achievement, it's an outcome of one, so it leaves the interviewer with nothing to evaluate.

The structure that works: STAR, led by the result

Use STAR, but put the result first so the point lands before the detail:

• Lead with the headline, the one-line outcome: what changed, and by how much.
• Situation and task, a sentence or two of context, just enough to make the result legible.
• Action, what you did, in the first person. This is where most of the time goes, and where your contribution has to be unmistakable.
• Why it mattered, the business or human impact, ideally tied to something the role cares about.

For example: “The thing I'm proudest of is cutting our checkout failure rate from 4% to under 1%, which recovered roughly two million in annual revenue. Checkout had been flaky for years and nobody owned it. I volunteered, instrumented the whole flow to find where requests were dying, rewrote the retry logic, and shipped it behind a flag to twenty million users. It mattered because it was real money the company was quietly losing every day, and it gave the team a template for owning the unglamorous reliability work that usually falls through the cracks.”

Pick the right achievement

The best achievement is recent enough to be relevant, clearly yours, measurable, and connected to what the role most needs. Read the job description and choose the story whose impact mirrors what they're hiring for: a reliability win for an infrastructure role, a launch you drove for a product role, a team you grew for a leadership role. Have a second one ready in case they ask “what else?”, and make sure at least one shows impact you can put a number on. Scale is nice, but a smaller achievement you clearly owned and can quantify beats a giant project where your part is a blur.

The fast way: rehearse the story with follow-ups

Achievement stories get tested under follow-ups, which is exactly where a real interviewer digs: “What was your specific part?”, “What would you have done differently?”, “How did you measure that?” Calibrd predicts the behavioural questions for a specific role and lets you practise your spoken answer, scoring whether your contribution was clear and the impact landed. A full mock interview then presses on your story the way a panel would, so the first time you're pushed on it isn't in the room. It's the same practice loop that works for every question.

So what do you actually do

1. Treat it as a test of judgment, contribution, and impact, not a contest of scale.
2. Pick an achievement that's relevant to the role, clearly yours, and measurable.
3. Tell it in STAR led by the result, keeping your own part unmistakable in the first person.
4. Close on why it mattered, then practise it out loud and rehearse the follow-ups.