This question sounds simple. Most candidates make it harder than it needs to be, either by picking the wrong example or by describing a genuinely strong achievement so modestly that it barely registers.
Picking the right achievement
Your greatest achievement for the purposes of an interview is not necessarily your personal proudest moment. It's the one that best demonstrates the skills and qualities this specific role requires, described in a way that gives the interviewer something concrete to remember.
Good criteria for selection:
- You had a clear, measurable impact, there's a number attached to the outcome
- You personally drove it, you made key decisions, not just contributed to a team effort
- It's relevant to the role, the skills involved map to what you'd be doing here
- The difficulty is visible, it should be clear this wasn't easy or routine
Why people undersell, and how to stop
Candidates soften achievements for a few reasons. Modesty, uncertainty about what's appropriate to claim credit for, or genuine uncertainty about the numbers. The result is answers like "we worked on a project that improved things a bit" when the reality was "I led a cross-functional initiative that saved the company £400,000 in the first year."
If you worked on something, you can claim credit for what you specifically did. You don't need to overstate your role. But you do need to be clear about it. "I led," "I designed," "I drove" are accurate and appropriate when they're true.
On numbers: if you don't know the exact figure, estimate honestly. "Roughly 20%" or "around $50k" is better than no number at all. Numbers make impact real to an interviewer in a way that descriptive language simply doesn't.
The Context-Action-Impact framework
- Context (brief): What was the situation and why did it matter?
- Action (detailed): What specifically did you do? What decisions did you make?
- Impact (specific): What changed? Use a number if you have one.
Sample answers
"My greatest professional achievement was rebuilding the onboarding flow for our mobile app. When I joined, 68% of new users dropped off before completing setup, the product was good but the first-run experience was losing people before they'd seen the value. I owned the full project: research, design, engineering coordination, and launch. We ran six rounds of usability testing, which is more than the team had ever done on a single feature. The new flow launched in Q2 and within 60 days we'd dropped abandonment to 31%. That lifted our 30-day retention by 19 percentage points and directly impacted our LTV calculation in the next funding round."
"I'd say closing our biggest ever enterprise account last year. The deal had been stalled for eight months before I took it over, the previous rep had been stuck on procurement and had lost momentum with the economic buyer. I started over: went back to the problem the client was trying to solve, got a new exec sponsor, and rebuilt the business case from their perspective rather than ours. It closed at £2.1 million, three times our average deal size at the time. It also became a case study that helped us close two similar deals the following quarter."