how to answer what is your greatest achievement

by Wistkey · 26 july 2026 · 6 min read

“what is your greatest achievement?” can feel like a request to boast or name something extraordinary. it is neither. the interviewer wants one clear example that shows what you value, how you work and what changed because of your contribution.

a strong answer does not need the biggest result of your whole career. it needs a relevant result that you can explain with confidence. choose carefully, make your own contribution visible and give the story a clean ending.

what the interviewer is listening for

the achievement is the evidence, not the entire point. your interviewer is listening for the skills behind it: how you noticed a need, made decisions, worked through difficulty and delivered something useful.

your choice also says something about what matters to you. an answer about improving a confusing process might show initiative and care for colleagues. an answer about winning back a customer might show judgement and communication. an answer about completing a demanding qualification while working might show discipline.

start with the job description. pick two or three qualities the employer keeps returning to, then look for an achievement that proves one or more of them. relevance beats spectacle.

choose an example with a visible change

write down five moments when something was better after you got involved. think beyond awards and promotions. useful achievements include:

• solving a recurring problem or improving a slow process;
• finishing a difficult project or meeting a demanding deadline;
• helping a customer, colleague or team get a better outcome;
• learning a skill and applying it to real work;
• taking responsibility when nobody had a clear plan.

choose an example that is recent enough to describe accurately, relevant to the role and clearly connected to your actions. if you are applying for your first job, use an example from education, volunteering, caring responsibilities, a club or a personal project. the setting matters less than the behaviour you can prove.

build the answer around challenge, action and value

the star method is useful, but achievement answers often become overloaded with background. use three simple beats to keep the important parts in view:

• challenge — what needed to change, and why did it matter?
• action — what did you personally decide and do?
• value — what improved, and what does that show about you?

you still have the full star structure underneath: the challenge covers the situation and task, your action remains the centre of the answer, and the value gives the result meaning. this keeps you from spending a minute describing the company before you reach your contribution.

make your own contribution unmistakable

team achievements are valid, but the interviewer cannot score a foggy “we did this” answer. name the team's goal once, then switch to “i”. explain the decision you made, the conversation you led, the analysis you completed or the obstacle you removed.

be specific without turning the answer into a task list. two or three connected actions are usually enough. choose the actions that reveal judgement: why you chose that approach, how you adapted when it did not work immediately, or how you brought other people with you.

do not claim sole credit for shared work. a precise sentence such as “i owned the handover process and introduced a weekly check-in” sounds more credible than either hiding behind the team or presenting the whole result as yours.

give an honest result

use a number only when it is real and you can explain it. a measured result might be time saved, errors reduced, a deadline met or positive feedback received. if you do not have a number, describe the observable change: the new process was adopted, the customer stayed, the event ran successfully or the team could complete the work without delays.

finish by connecting the achievement to the role. one sentence is enough: “i'm proud of it because it showed me that i can bring structure to an unclear problem and keep people involved while fixing it.” that reflection turns a past event into evidence of what you can offer next.

use this answer template

try this as a starting point, then replace every general phrase with your own detail:

“one achievement i'm particularly proud of was [result]. at the time, [brief challenge]. i was responsible for [your task]. i decided to [first important action], then [second important action]. as a result, [specific change]. i'm proud of it because [what it proves that is relevant to this role].”

say it aloud and listen for the balance. the background should be short. your actions should take up most of the answer. the result and reflection should land clearly rather than trail away.

avoid the answers that weaken good evidence

• choosing something impressive but irrelevant — make the link to this role easy to hear.
• giving a list of achievements — one developed example is stronger than five headlines.
• using only “we” — respect the team while identifying your contribution.
• inventing precision — an honest observable result is better than a number you cannot support.
• stopping at the result — add one line about why the achievement matters to you or what it proves.

practise for clarity, not perfection

record one answer and review it once. first, check the content: can a listener identify the challenge, your actions and the value? then check the delivery: do you rush the result, lose energy halfway through or look apologetic when describing your success?

change one thing and record it again. you are not trying to memorise a speech. you are learning the shape of the story well enough to tell it naturally and answer follow-up questions without losing your place.