Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About Your Biggest Accomplishment Question
Transcript
- Lucas: Luna, I was looking at hiring manager surveys from earlier this year, and there's one question that consistently lands in the top three most asked, yet almost everyone preps for it wrong. Luna: Let me guess — 'Tell me about your biggest accomplishment.' It's the one that sounds easy until you're sitting in the chair. Lucas: Exactly. And the survey I saw said nearly 70 percent of candidates give an answer that's either too vague, too personal, or just not structured in a way that shows business value. So today we're going to fix that. Luna: I love that we're drilling into this. I've seen so many people freeze on this one, especially when they think they don't have a flashy story. Lucas: Right, and that's the first myth to bust. You don't need a story that saved the company from bankruptcy. You need a story that shows you can deliver results, and that starts with picking the right accomplishment. Luna: So what makes an accomplishment 'right'? I'm guessing it's not just the one with the biggest number. Lucas: Not at all. The right story is one that's relevant to the job you're applying for, recent enough to feel fresh, and most importantly, one where you can clearly articulate your specific role. Hiring managers aren't impressed by team achievements where you were just a passenger. Luna: Okay, so relevance, recency, and ownership. But how do you actually structure the answer once you've picked the story? Lucas: That's where the STAR method comes in, but with a twist. Most people know Situation, Task, Action, Result. The problem is they spend too long on the situation and task, and then rush the action and result, which are the parts that actually matter. Luna: So you're saying the classic STAR is backwards? I've definitely been guilty of that — setting the scene for way too long. Lucas: Yeah, and I think the fix is to flip the emphasis. Spend about twenty percent on the situation and task combined, fifty percent on the actions you took, and thirty percent on the result, with a strong business metric. That's the formula. Luna: Got it. So the result isn't just 'we were happy' — it's a number that a finance person would recognize. Lucas: Exactly. Let me give you a concrete example. A friend of mine, a marketing manager, used this in an interview for a senior role. Her story was about reducing customer acquisition costs for a SaaS client. The situation was that the client was spending heavily on paid ads with declining returns. The task was to turn that around within a quarter. Luna: Okay, so a clear situation and task. What did she do that made it stand out? Lucas: She said she started by auditing the entire funnel, not just the ad campaigns. She found that the landing page was converting at under one percent, which was the real bottleneck. So she worked with the design team to rebuild the page, ran A-B tests on the headlines, and shifted budget away from the worst-performing channels. That's the action part — specific, methodical, and shows initiative. Luna: I like that she looked beyond the surface. So what was the result? Lucas: Within two months, the cost per acquisition dropped by forty percent, and the client saw a twenty-five percent increase in qualified leads. She didn't say 'I saved the company,' she said 'I reduced cost per acquisition by forty percent and increased leads by a quarter.' That's a metric a hiring manager can grasp instantly. Luna: That's a strong example. But what if someone's accomplishment isn't that quantitative? Like, what if you're in a role where results are more qualitative, like improving team morale or streamlining a process? Lucas: That's a great point, and I'd say you can still find a proxy. If you improved team morale, maybe you reduced turnover by a few percentage points, or you cut the time to onboard a new hire. If you streamlined a process, maybe you reduced the time it takes to generate a report from two days to two hours. There's almost always a number you can attach, even if it's not directly revenue. Luna: So the key is to find some measurable outcome, even if it's a soft metric. That makes sense. But I've also heard that you shouldn't pick an accomplishment that's too old. How recent should it be? Lucas: I'd say within the last two to three years is ideal. Anything older than that, and you risk sounding like you haven't done anything meaningful since. If you're early in your career, you can pull from internships or even group projects, but you need to position it with the same rigor. Luna: What about the opposite problem — someone picks a story that's too personal, like raising a child or running a marathon? I've seen that go south. Lucas: Oh, that's a classic mistake. Unless you're applying for a job as a professional marathoner, that story doesn't tell the hiring manager how you'll perform in this role. The interview is about your professional capability, so the accomplishment should be work-related. Personal stories can show resilience, but they're hard to connect to the job, and they often sound off-topic. Luna: So let's say someone has a great story, but they struggle with being concise. How do you keep it under two minutes without cutting the substance? Lucas: The two-minute rule is a good discipline. I recommend practicing with a timer, and if you can't tell your story in under two minutes, you haven't distilled it enough. The framework I just gave — twenty percent situation, fifty percent action, thirty percent result — naturally keeps you on track. Also, don't start from the beginning of the project. Start in the middle, where the problem is acute. Luna: Starting in the middle — that's a great tip. So many people begin with 'when I joined the company in 2019' and lose the interviewer by the time they get to the point. Lucas: Right, you want to hook them immediately. 'We were losing customers because our onboarding was a mess' is a stronger opening than 'In my previous role, I was responsible for...' And that also sets up a natural tension that makes your action more impressive. Luna: I want to circle back to the idea of 'business impact.' You mentioned a finance person would recognize the metric. Can you elaborate on that? Lucas: Sure. A hiring manager in a corporate role is thinking in terms of revenue, cost savings, efficiency gains, or risk reduction. If your accomplishment can be framed in one of those buckets, it's instantly more compelling. For example, 'I redesigned the billing process which reduced billing errors by thirty percent' — that's cost savings and maybe customer satisfaction. 'I launched a referral program that brought in fifty new clients' — that's revenue growth. Luna: So it's about translating your work into the language of the business. I've seen candidates who are great at their craft but can't articulate the value. That's a missed opportunity. Lucas: Exactly. And that's why we're doing this episode. It's a skill you can learn. Let's talk about a common pitfall: not owning the result. Some people say 'we achieved' instead of 'I.' Even if it was a team effort, you need to be clear about your contribution. Hiring managers want to know what you personally did. Luna: How do you handle the 'we' problem without sounding like you're taking all the credit? Lucas: You say something like, 'I led the initiative, and I worked with a team of three to execute it. My specific part was...' Then you highlight your actions and the outcome. That's honest and shows leadership. Luna: That makes sense. So we've covered the structure, the choice of story, the metric, and the 'I' problem. Is there anything else you'd flag as a common mistake? Lucas: One more: not having a backup story. You might get asked a follow-up like 'tell me about a time you overcame a challenge' and if you only have one accomplishment in your back pocket, you're stuck. I always advise preparing three stories: your biggest accomplishment, a time you failed, and a time you showed leadership. Those three cover a lot of bases. Luna: Good point. We've actually talked about failure and leadership in past episodes, but it's worth repeating. Now, what if the accomplishment is from a different industry? Is that a problem? Lucas: Not necessarily, as long as the skills translate. If you're moving from retail to tech, and your accomplishment was leading a store remodel that increased sales by fifteen percent, that shows project management and commercial acumen. The key is to frame it in a way that connects to the new role. You might need to explain the context a bit more, but it can work. Luna: So the lesson is: pick a story that shows transferable skills and is relevant to the new role. I think we've got a solid framework here. Should we walk through a live example? Maybe a less obvious one? Lucas: Let's do it. Let's take a customer service rep who wants to move into an operations role. Their accomplishment could be: they noticed that a high volume of tickets were about the same issue, so they created a troubleshooting guide that reduced repeat contacts by twenty percent. That shows they can identify a process improvement, take initiative, and deliver a measurable result. Luna: That's perfect because it's not flashy, but it's exactly what an operations manager would want to hear. They're thinking about efficiency and problem-solving. Lucas: Exactly. And you can apply that same template to any role. The point is to find a problem you solved, show your process, and quantify the impact. That's the golden rule. Luna: That's a great takeaway. And it reminds me of something we've talked about before: the importance of knowing your numbers. If you can't recall the exact percentage, it's better to give a range than to fumble. Lucas: Absolutely. 'About forty percent' is fine, but don't say 'a lot' or 'significant.' Hiring managers want specifics. And if you can bring a visual or a written summary to the interview, that can reinforce your story. Luna: That's a pro tip. Now, before we wrap up, I know we've talked about how to prepare stories, but what about the delivery? Any advice on how to sound confident without sounding rehearsed? Lucas: Practice out loud, but don't memorize word for word. You want to know your bullet points, not a script. And remember to pause briefly before you start — it makes you look thoughtful. Also, maintain eye contact and let your passion show. If you're excited about your accomplishment, the interviewer will be too. Luna: I think that's the perfect note to end on. But first, I want to mention something to our listeners. If this episode helped you think through your interview prep, and you find value in what we do here at Fexingo, consider supporting us on buy me a coffee dot com slash fexingo. It's a simple way to keep the podcast ad-free and independent. Lucas: Yeah, we appreciate that so much. It really does help us keep doing these deep dives. And we're not going anywhere either way, but if you're in a position to, it's a small gesture that goes a long way. Luna: Exactly. So back to the topic — one last thing. How do you handle a follow-up question like 'Why did you choose that as your biggest accomplishment?' Lucas: That's a chance to show your values and self-awareness. You can explain that you chose it because it had a measurable impact on the business, and it taught you something about leadership or problem-solving that you've applied since. It's a nice way to close the loop. Luna: Perfect. I think our listeners now have a clear path to answering this question with confidence. Thanks for joining us.