Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Mentored Someone
Transcript
- Lucas: Luna, I want to run something by you. I've been noticing a question popping up more often in interviews lately, even for mid-level roles where the person isn't managing anyone. Luna: Which question is that? Lucas: The 'tell me about a time you mentored someone' question. It used to be reserved for senior leadership or people-manager tracks, but now I'm seeing it in finance, tech, consulting — even in individual contributor interviews. Luna: I've seen that too. In fact, I was talking to a recruiter at a big asset manager last week, and she said they've started including a mentoring question for all analyst promotions. Not just for managers. Lucas: Exactly. And I think the reason is that mentoring signals a few things hiring managers really care about: patience, communication, the ability to transfer knowledge, and — this is key — the capacity to scale yourself. If you can teach someone else to do part of your job, you're ready for more responsibility. Luna: So how do you answer it well? Because a lot of people hear 'mentoring' and think they need to have had a formal mentee with monthly one-on-ones. That's not the only way. Lucas: Right. The first step is to broaden your definition. Mentoring can be informal: helping a new hire learn the internal systems, walking a peer through a tricky Excel model, even onboarding a summer intern for a week. The key is that you took deliberate action to develop someone else's skills. Luna: I'd add that the best answers show a structure. Interviewers love the STAR method — situation, task, action, result — and it works great here, but with a mentoring twist. Lucas: Break that down for me. What's the mentoring twist? Luna: In the 'action' part, you need to show that you diagnosed what the person needed. Not just 'I taught them how to use Bloomberg' but 'I noticed they were spending two hours manually pulling data, so I showed them a keyboard shortcut and built a template that cut that to 20 minutes.' The diagnosis shows you're thinking about efficiency, not just instruction. Lucas: That's a great point. And in the 'result' part, you can quantify the impact on the mentee, but also on the team. For example: 'Within a month, my mentee was running the weekly report independently, which freed up eight hours of my own time per month for higher-level analysis.' That's the scaling piece I mentioned. Luna: Do you have a concrete example you'd use? Let's say you're interviewing for a senior analyst role at a bank. What's your story? Lucas: I do, actually. When I was a senior analyst at a regional bank, we hired a junior analyst straight out of undergrad. She was smart but overwhelmed by the reporting cycle. She kept pulling data from the wrong system and her pivot tables were a mess. Luna: So what did you do? Lucas: I set up a daily 15-minute check-in for the first two weeks — not to check her work, but to ask 'what's the hardest thing today?' The first week, we focused on data validation. I showed her how to cross-reference our internal system with the general ledger so she'd catch errors before submitting. Luna: That's smart. You're teaching the process, not just the fix. Lucas: Exactly. By the end of the second week, she was building her own pivot tables from scratch and had started suggesting improvements to our monthly report. The result? Her reports were error-free within a month, and our team's rework time dropped by about 30 percent. That junior analyst later told her manager that the onboarding was the best she'd had. Luna: That's a strong example because it shows you recognized a need, you invested time, and there's a measurable outcome. But what about someone who's never had a direct mentee? Can they still answer this question? Lucas: Absolutely. Think about times you've helped a peer learn a new tool, or you've been the go-to person for questions on a project. Even informal peer coaching counts. For instance, if you taught a teammate how to use a new data visualization tool like Tableau, that's mentoring. Luna: Or if you've ever presented a 'lunch and learn' to your team — that's mentoring a group. You're transferring knowledge in a structured way. Lucas: Right. The key is to frame it intentionally. Don't say 'I just answered their questions.' Say 'I recognized that the team had a knowledge gap in X, so I created a short training session and offered follow-up office hours.' That signals leadership. Luna: One nuance I'd add: interviewers also want to see that you can handle a mentee who's struggling. Not everyone learns at the same pace. If your story includes a moment where you had to adapt your approach, that's even better. Lucas: Great point. Let's say your mentee was resistant to feedback. How would you adjust? Maybe you shift from telling to asking — 'What do you think would make this process smoother?' That shows emotional intelligence. Luna: Exactly. And if you're in a technical field, reverse mentoring is also a thing. Have you ever mentored someone older or more senior? That can be a powerful story because it shows you can manage up. Lucas: That's a good call. I once mentored a senior partner on using a new CRM system. He was a bit skeptical, but I showed him how automating follow-ups could save him 10 emails a day. After a week, he was a convert. That story shows you can influence without authority. Luna: So the takeaway: you don't need a formal title. Think of any situation where you deliberately helped someone learn or grow, and structure it with STAR, emphasizing the diagnosis and the outcome. Lucas: Before we wrap, I want to share one more tip. When you're practicing your answer, time yourself. Aim for about 90 seconds. That's the sweet spot — enough detail to be credible, short enough to keep the interviewer's attention. Luna: And if they ask a follow-up like 'what would you do differently?' be honest. If your mentee struggled, talk about what you learned. That's a leadership quality too. Lucas: You know, speaking of learning and growth — something I've been thinking about. This show is possible because of listeners like you. We don't run ads, and we keep every episode focused on practical advice. A handful of listeners chip in monthly through Buy Me a Coffee dot com slash Fexingo, and that literally funds making this many episodes. So if you've gotten value from an episode, especially a job offer or a better interview, that's a way to keep it going. Luna: Yeah, it's a small group that makes it possible for everyone else to access this for free. We appreciate every bit of support. Lucas: Okay, back to mentoring. One last thing I want to emphasize: if you're preparing for an interview this week, take five minutes to write down one mentoring story. Even if it feels small. Practice it out loud. I promise, it will make you more confident when that question comes. Luna: And if you don't have a story yet, create one. Volunteer to onboard the next new hire, or offer to lead a knowledge-sharing session. That way, next time you're asked, you'll have a fresh example ready. Lucas: Great advice. Thanks, Luna. And thanks to all of you for listening. We'll be back next week with another behavioral question deep dive.