What are interviewers looking for when they ask about your biggest achievement?

They want evidence of what you count as success, how you got there and whether it resembles the work they need done. Google's guide to structured interviewing describes behavioral questions as asking candidates to "describe prior achievements and match those to what is required in the current job." The match matters as much as the size.

That line comes from Google's guide to structured interviewing, updated March 2026. The same guide says interviewers score answers with rubrics that describe what a "poor, borderline, solid, and outstanding answer would cover." Your achievement is being compared with a written standard, so specifics count more than enthusiasm.

The US Office of Personnel Management gives the reasoning behind questions like this. Its page on structured interviews says behavioral questions rest on the idea that "past behavior is the best predictor of future behavior." Your biggest achievement is a preview of the work you would do for them.

How do you choose the right achievement?

Pick the achievement closest to the job's main requirement that you can explain in detail, even if a bigger one exists. A smaller result you drove yourself usually works better than a large team result where your part is unclear. Recent examples are also easier to defend when follow-up questions come.

Run each candidate example through these checks:

  • It relates to a requirement in the job posting, ideally one near the top.
  • You personally made decisions or did the work, and you can say which parts.
  • There is a result you can state, with a number or a clear before and after.
  • Someone who worked with you would describe it the same way.
  • You can tell it in about two minutes and answer three follow-up questions.

The last two checks matter more than people expect. The BC Public Service warns candidates that "You may be asked for a reference for your examples," on its interviews and assessments page. Pick something a former manager would confirm without hesitation.

Your situationA good achievement to chooseWhy it works
Early career or new graduateA project, internship or part-time job result with a measurable outcomeShows you can deliver before you have a long track record
Career changerA result from your old field that uses a skill the new job needsConnects your past to their requirement
Individual contributorSomething you built, fixed or improved, with the effect on users or the teamYour part is easy to see
ManagerA team result where you name the decisions you madeShows judgment as well as effort
Returning after a gapA strong result from before the gap, or from volunteer or freelance workShows the skill still exists

If you are short of examples, build a list before the interview. The page on building a behavioral interview story bank shows how to collect a set of stories that cover the common questions.

How should you structure the answer?

Use STAR: situation, task, action and result, with most of the time on action and result. The BC Public Service tells candidates to keep the situation brief, to "use 'I' not 'we'," and to describe what happened, what they accomplished and what they learned. The learning step keeps a strong answer from sounding like a boast.

Amazon's interview guide asks for STAR answers "typically lasting 2-3 minutes each." It also asks for "precise metrics and data that quantify your impact" and "I" statements that show your own contribution. Those three habits turn a vague success into evidence.

A simple split for a two-minute answer is about 20 seconds of situation and task, a minute of action and 30 seconds of result and learning. The STAR method guide covers each part in detail. If you are unsure which framework fits, the page comparing STAR, CAR and SOAR sets out the differences.

What are some example answers?

Here are four example answers for different situations, all made up for this page. The names, numbers and companies are invented to show the shape of a strong answer. Swap in your own facts, and keep only numbers you could explain if an interviewer asked how you measured them.

Example: customer support team lead

"My biggest achievement was cutting our average first response time from 19 hours to 4 hours at a software company with about 3,000 customers. Tickets were piling up because every request went into one queue. I sorted a month of tickets by type and found that 40% were password and billing questions. I wrote help articles for the top ten and set up rules that routed billing tickets to two specialists. Within six weeks the response time was down to 4 hours, and our satisfaction score rose from 81% to 89%. I learned to look at the data before asking for more staff."

Example: software developer

"The achievement I'm proudest of is rebuilding our checkout page, which was failing for about 2% of mobile users. I was one of three developers, and I owned the payment form. I traced most failures to a script that loaded slowly on older phones, rewrote the form without it and added error tracking. Failed checkouts on mobile fell below 0.5% within a month, which the finance team estimated was worth about $40,000 a quarter. Since then I add tracking before I ship anything that touches payments."

Example: new graduate

"In my final year I led a four-person team in a case competition for a regional food bank. The brief was to raise volunteer sign-ups. I ran interviews with twelve past volunteers and found most stopped because shifts were posted only a few days ahead. We proposed posting shifts a month out with text reminders. The food bank tried it the next spring and told us sign-ups rose by about a third. It taught me to talk to users before designing anything."

Example: career changer from teaching to project coordination

"As a grade 9 teacher, I coordinated our school's move to a new online grading system for 40 teachers and about 900 students. I built the rollout schedule, ran four training sessions and set up a weekly check-in for problems. We went live a week early, and by the end of term every teacher had entered marks on time, compared with about 70% the year before. That project is why I'm applying for coordination roles: I enjoyed the planning more than anything else."

Each example names one result, says what the speaker personally did and ends with a number and a lesson. None runs past about two minutes when spoken. For more models of the same structure, see went above and beyond and used data to make a decision.

What mistakes weaken this answer?

The common mistakes are picking a personal milestone with no link to the job, describing a team win without your own part, giving a result with no number or comparison, and running well past three minutes. Each one leaves the interviewer without the evidence they need to score your answer against the job.

  • A personal milestone, such as running a marathon, can work for a first job. For most roles, a work example scores better because it matches a requirement.
  • "We launched the product" tells them nothing about you. Say which decisions you made.
  • "It went really well" has no size. Give a before and after, even a rough one.
  • Five achievements in one answer means none gets detail. Choose one and offer a second if they ask.
  • An achievement that contradicts your resume invites awkward questions. Make the numbers match.

If the interviewer follows up with "What would you do differently?", have an answer ready. It shows the same reflection the BC Public Service asks for. For team results, the page on the showed leadership question covers that follow-up.

What if you don't have an impressive achievement?

Use a smaller one and make the before and after clear. "Cut the weekly report from four hours to one" is a real achievement if you did it and it mattered to someone. Interviewers are scoring evidence against the job, so a modest, specific result can score better than a large, vague one.

Look for achievements in four places: something you made faster or cheaper, a problem you fixed that others had left, something you taught or documented, and feedback that named you. A recent performance review or thank-you email is a good place to start.

Keep your resume and your answer consistent. If the achievement is on your resume, the interviewer may have it in front of them, so the numbers need to match. The guide to resume bullet points shows how to write the same result in one line, and the free resume optimizer rewrites the lines that matter for a job while keeping your facts.

To find out which achievement a specific job is likely to ask about, the free interview questions tool takes a pasted job and the round you picked, and lists likely questions with what the interviewer listens for. Then practise the answer out loud. The Mock room puts you on a clock, scores each answer out of 10 and checks it against your resume, and it is included in Prept's free plan.