How to Answer “Tell Me About an Achievement You're Proud Of” in an Interview
· by the InterviewCrusher team
When they ask you for an achievement, the recruiter doesn't want to hear that you're “proactive” or “hardworking.” They want proof. They want to see what you consider good work, how big your idea of impact is, and whether you can take credit without inflating it or handing it all to the team. Really, they're measuring your yardstick: someone who's proud of “showing up on time” is telling you something very different from someone who's proud of having won back a lost account.
The most common mistake is picking an achievement that has nothing to do with the job, or telling it without a number to ground it. “I organized the end-of-year party” says nothing if you don't know how many people it affected or what problem it solved. The question is a chance to prove, with a concrete case, exactly the skill that posting is looking for. That's why you choose the achievement by reading the job description, not by opening the drawer of your favorite memories.
The structure that works is STAR: situation, task, action, and result. But the weight isn't spread evenly. The situation stays brief, just to set the frame. The action is where you show your judgment. And the result, with a number, is what turns an anecdote into an achievement. Knowing this isn't enough: you have to be able to say it out loud, without hesitating, in under two minutes.
What mistakes should you avoid when answering “Tell me about an achievement you're proud of”?
- Choosing an achievement that's irrelevant to the job (for example, recounting an athletic feat in a data analyst interview): you waste the chance to prove the skill they're assessing.
- Telling it with no measurable result. “Everything improved” or “the client was happy” prove nothing. Without a number or a concrete before/after, it sounds like filler.
- Claiming a team achievement entirely as your own, or the opposite, dissolving so far into the “we” that it's unclear what you actually did. Be clear about your specific contribution.
- Rambling through two minutes of context before you get to what you did. If the recruiter gets lost in the situation, they're no longer listening to your action or your result.
STAR applied to an achievement
- 1
Situation and task (a brief frame)
Two or three sentences to set the scene: where you were, what problem or challenge there was, and what your specific responsibility in it was. Don't get tangled up in context. The goal is that in fifteen seconds it's clear what was at stake and why it fell to you to solve it. If the challenge isn't clear, the achievement won't impress later.
- 2
Action (your judgment on display)
This is the bulk of the answer. Explain what you did, with what decisions and why. Use the first person: “I decided,” “I proposed,” “I built.” If it was teamwork, say which part you led without erasing the rest. This is the part that reveals how you think and work, so show the reasoning, not just the tasks.
- 3
Result (the number that seals it)
Close with the impact, and make it measurable: a percentage, a saving, a timeline, a before and after. “I cut response time from 48 hours to 6” carries a thousand times more weight than “we improved service.” If you don't have an exact figure, give an honest estimate and say how you calculate it. And finish with why it makes you proud, in one sentence, no speech.
Sample answers
“At my previous company, a SaaS platform, the support team closed tickets but nobody looked at why they kept coming back. I ran the billing issues queue and I kept seeing the same five questions over and over. I decided to spend a couple of afternoons classifying the tickets from the previous three months. I found that 40 percent were about the same step of the payment process. Instead of continuing to answer them one by one, I proposed rewriting that text in the interface and building three help articles. I presented it to product with the data and they let me pilot it. Within two months, billing tickets dropped by 35 percent and the team's average first-response time went from around 9 hours to 4. It makes me proud because it wasn't about working more hours, it was about looking at the data nobody was looking at and attacking the cause, not the symptom.”
“In my final year of university we did a group project with four people: an app for a local nonprofit to manage its volunteers. The real problem was that they ran everything in a spreadsheet and kept losing shifts. I took care of the database side and of talking with the nonprofit to understand what they really needed, which wasn't what we'd assumed at first. I insisted on holding two meetings with them before writing any code, and that saved us from redoing half the app. We ended up delivering it and the nonprofit actually used it: they managed around 60 volunteers at their spring event without losing a single shift, or so they told us. We got the best grade in the class, but what makes me proud is that something we built for a course ended up being useful to someone outside the classroom.”
Quick tips
- Choose the achievement by reading the job posting first. Underline the skill that comes up most in the job description and look for your best case to prove it. The “right” achievement depends on what you're aiming for, not on which one you remember most fondly.
- Prepare the number before the interview. If you don't have it handy, track it down or estimate it honestly. An achievement without a number evaporates; one with data sticks in the recruiter's head.
- Say it out loud and time yourself: the target is a minute and a half, two at most. Having the story clear in your head is one thing; telling it without rambling or falling short is another. Practice it with the AI, which will follow up on the number and your exact role, just like a real recruiter would.
Knowing the answer isn't the same as saying it out loud
Practice this question with an AI recruiter that asks follow-ups, keeps the pressure on, and gives you honest feedback. In your language and no credit card.