What is your greatest achievement?

What counts as an achievement

Candidates discard their best material because it does not feel grand enough. The test an interviewer applies is narrower than you think: something changed, you were the reason, and the change can be described.

That admits a lot. Fixing a process nobody else wanted to touch. Keeping a service running while two colleagues were off. Passing a qualification while working full time. Getting a complaint rate down on a difficult account. Training someone who is now better at the job than you were at their stage. None of it requires a promotion or an award.

What does not count is a thing that happened near you. “The team hit a record quarter” is a fact about the team. If your part was real, name it; if your part was small, choose something else.

MIT’s career office asks a version of this question as “Describe your most rewarding accomplishment since you’ve started college”, which is a useful reframing. Rewarding, not impressive. The achievement you can talk about with genuine interest will land better than the one you chose because it looked big on paper.

Choosing the right one for this job

Most people have four or five candidates. Run each through three questions and the choice usually makes itself.

Does it demonstrate something in the job description? An achievement that shows a skill the advert asks for twice is worth more than a larger one that shows nothing relevant. The National Careers Service advice for achievement questions is exactly this: tailor your examples to the job description.

Is it recent enough to be evidence? Something from the last two or three years says what you can do now. A story from a decade ago invites the question of what you have done since, unless your career has one obvious peak.

Can you prove it in one sentence? If you cannot say what changed, you have a story rather than an achievement. Keep it in reserve for a behavioral question and pick another.

If two candidates survive all three questions, choose the one where your own contribution is hardest to confuse with anyone else’s. Interviewers are listening for you, and clarity about your role is what separates a strong answer from a pleasant one.

How to tell it in 90 seconds

Open with the headline, in one sentence, so the interviewer knows where the story is going: what you achieved and the result. People who save the result for the end lose the room halfway through.

Then the context, kept to two sentences. Where you were, what the problem was, why it was difficult. Difficulty is the part that gives the achievement its weight, so do not skip it: a constraint, a deadline, a resistant stakeholder, missing information.

Then what you did, which is the bulk of the answer. Say it in the first person and in order. MIT’s guidance on the STAR method is that most of your response should focus on your actions, and that applies here even though this question is phrased as a result rather than a situation. If you made a judgement call, say what you weighed.

Close with the result and one line on what it meant. Numbers if you have them, adoption or durability if you do not: the process is still in use, the client renewed, the trainee now runs the shift. The last line is where “greatest” gets earned, and it is the one place a short personal note belongs.

If you want the full four-part framework for stories like this, the STAR method page covers it in detail. This answer is a compressed version with the result pulled to the front.

Putting a number on it when nothing was measured

Plenty of real achievements were never tracked, especially outside sales and operations. You can still be concrete.

Use a before and after. The handover used to take a full day and now takes an hour. The report was nine pages and is now one. Two people ran that rota and now one person can.

Use scope. How many people, sites, accounts, cases, students or tickets your work touched. Scope is usually knowable even when outcomes are not.

Use time. How long the fix has survived, how quickly you delivered it, how much time per week it gives back to someone else.

Use adoption. Who else started using what you built, whether it became the standard way of doing it, whether another team copied it. Adoption is often more persuasive than a percentage, because it is evidence that someone other than you judged the work worth keeping.

Two cautions. Do not invent figures; a number you cannot defend will be probed, and an approximation you can explain is safer than a precise one you cannot. And do not disclose confidential data. Describe the magnitude in neutral terms, or say that the figure is commercially sensitive but the direction was a clear improvement. No interviewer thinks less of a candidate who protects a former employer’s numbers.

Sample answers

Office role, early career

The thing I am proudest of is cutting our invoice query backlog from about three weeks down to three days, and keeping it there.

I joined as the second person in a small finance team and queries arrived by email, so they got answered when someone noticed them. Two customers had put orders on hold over it.

I spent a week reading the last two hundred queries and found that most were one of four problems. I built a shared log so queries could not be lost, wrote standard replies for those four cases, and asked for an hour each morning protected for the log.

The backlog cleared in a month and stayed short after I moved teams, which is the part I am most pleased about. My replacement still uses the log.

Shift or frontline role

My biggest achievement was running the store’s stockroom through a refit without losing a day of trading.

We lost two thirds of the stockroom space for six weeks, and the delivery schedule did not change.

I rebuilt the layout around the fastest-selling lines, agreed a split delivery with the driver so we took half in the morning and half at night, and taught the evening team the new positions on their first shift rather than leaving a note.

We had no stock-outs on the main lines during the refit, and the manager kept the split delivery afterwards. It was the first time I had been given a piece of the operation to plan myself.

Technical role

The achievement I would pick is taking our overnight batch from a job that failed most weeks to one that has not failed in a year.

It was a chain of nine steps with no retries, so a single timeout meant a manual rerun and a late report for the trading desk. Two people were on call for it.

I split the chain into independent steps with their own retries, added alerting on the step rather than the whole job, and spent a fortnight on the two steps that caused most of the failures. I pushed back on rewriting the whole thing, because the failures were concentrated.

The on-call rota for it has been quiet since, and the desk gets its report before seven every morning. It also freed the second on-call engineer for project work.

Outside work

Outside of work, the thing I am proudest of is qualifying as a mountain leader while working full time.

It took two years of weekends, a logbook of twenty quality mountain days, and a first aid certificate, with an assessment I had to prepare for twice.

I planned it around shifts, found a group to walk with so the days still happened in bad weather, and took the parts I failed first time as the parts to practise rather than a reason to stop.

I now lead groups for a walking club two or three times a season. It is also where I learned to make a decision about turning back with people who do not want to.

The "greatest achievement in life" variant

Sometimes the question is wider: your proudest moment, your greatest achievement in life, or what you are most proud of outside work. Interviewers ask it for two reasons, to see what you value and to give candidates with short work histories something to answer.

You have a genuine choice here. A personal achievement is fine, and often more memorable than a work one. Qualifications earned alongside a job, sport, raising money for something, learning a language, caring for a family member through something hard, restoring something with your hands: all of these have shown up in good interviews.

Pick one that still shows a work-relevant quality. Persistence, planning, learning something uncomfortable, following through when nobody was checking. Then tell it the same way as a work example, with a result at the end.

Two things to keep out. Avoid achievements that depend on strong opinions, such as political or religious campaigning, unless they are directly relevant to the employer’s work. And avoid anything that shades into private medical or family detail you would rather not discuss, because the follow-up question is natural and you may not want to answer it.

If your work history is short, the National Careers Service suggests using examples from outside work or from volunteering experience, which is permission you can take at face value.

What spoils a good achievement answer

The “we” answer. A story told entirely in the plural leaves the interviewer unsure what you did. Credit the team once, then describe your own decisions.

The mismatch. A technically dazzling achievement that shows none of the skills in the advert is a wasted ninety seconds. Choose for relevance.

The antique. An achievement from fifteen years ago, offered without anything since, reads as a career that peaked early.

The unverifiable boast. Industry awards, revenue claims and comparisons to colleagues all invite checking. Stick to what you did and what changed.

The missing result. Interviewers forgive a modest outcome; they do not forgive an answer that trails off. Even “it still works and nobody has had to touch it” is a result.

And the over-modest answer. If you describe your best work as “nothing special, really”, the interviewer has to do your persuading for you, and they usually will not. Say what you did and let it stand.