Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer the Tell Me About a Time You Led a Project
Transcript
- Lucas: Luna, let me run a question by you. 'Tell me about a time you led a project.' That is one of the most common behavioral questions out there, and I think most candidates fumble it in the same way. Luna: Oh, I've seen it. They either go too vague — 'I led a team to improve efficiency' — or they list every single task they did themselves, which sounds like they managed a to-do list, not people. Lucas: Exactly. And the interviewer is testing for a few specific things: can you set direction, can you orchestrate others, and can you handle the inevitable friction. So today I want to walk through one really concrete example — a candidate I worked with who was applying for a supply chain manager role. Luna: Let's hear it. What was the project? Lucas: She was at a mid-size logistics company, around three hundred employees. They were switching from a legacy warehouse management system to a modern cloud-based platform. Her boss asked her to lead the rollout. She had no formal authority over the team — it was a cross-functional group with people from IT, operations, and warehouse floor leads. Luna: That's a classic. No direct reports, but you're expected to get results from people who don't report to you. Lucas: Right. So the first thing we worked on was framing it with the STAR method — situation, task, action, result. But the key is that for a leadership story, the 'action' part should focus on how she mobilized the team, not what she coded or configured. Luna: So she needed to show she could delegate, make trade-offs, resolve conflicts. Lucas: Exactly. In her first draft, she spent three sentences describing her own work migrating data. That's fine as a detail, but it doesn't answer the question. The interviewer doesn't care if you can write a SQL query — they want to know if you can keep a group of stressed people moving toward a deadline. Luna: What was the tension in the story? There's always a conflict in good answers. Lucas: The warehouse floor leads were skeptical. They'd been using the old system for a decade, and they were convinced the new one would slow them down during peak season. One lead, in particular, kept skipping the training sessions. So our candidate had to decide: escalate to his manager, or try to win him over. Luna: Which did she do? Lucas: She sat down with him on the warehouse floor, watched him work for an hour, and then showed him how the new system would cut his most annoying manual step by about forty percent. She didn't just tell him — she proved it with his own process. Luna: That's a perfect micro-moment of leadership. It shows empathy, but also data-driven persuasion. Lucas: She also had to deal with IT being stretched thin. The original launch timeline was eight weeks. IT said they couldn't commit to integrations until week ten. So she renegotiated the scope — launched the core functionality at week nine, deferred two nice to have features to a phase two. Luna: So she made a trade-off. That's huge. A lot of candidates think leadership means never compromising on the plan. Lucas: Right. The best answers show you made a deliberate call, not that you just powered through. So her final answer using STAR went something like this. Situation: our company was migrating to a new warehouse system with a hard deadline before peak season. Task: I was asked to lead the cross-functional rollout with no direct authority over the team. Luna: And the actions? Lucas: She listed three. One, she built buy-in with the skeptical warehouse lead by shadowing him and showing a concrete time-saving. Two, she renegotiated the timeline with IT, cutting the scope to hit the critical launch date. Three, she set up weekly fifteen-minute stand-ups to catch blockers early, instead of waiting for a monthly status meeting. Luna: And the result? Lucas: They launched on time — week nine — and within thirty days, order accuracy improved from ninety-two percent to ninety-seven percent. The warehouse lead became an advocate and even helped train other teams. Luna: That's a strong result because it's specific and it ties back to the leadership. It's also a number that sounds credible — not inflated. Lucas: One thing I'd flag: she initially wrote 'we improved accuracy by five percent.' I told her to change it to 'from ninety-two to ninety-seven percent' because the absolute numbers are more concrete. Also, it shows she knew the baseline. Luna: What about candidates who haven't had a formal project lead role? I've had listeners write in saying 'I've never led a project, what do I do?' Lucas: That's a great question. You don't need a title. You can talk about leading a volunteer event, organizing a team offsite, or even spearheading a process improvement in your own role. The key is the same: you mobilized others toward a goal. Luna: Give me a quick example. Say someone is early in their career, like a marketing coordinator. Lucas: Sure. Situation: the company was preparing for a trade show, and the lead marketer went on leave. Task: I stepped up to coordinate the booth materials and schedule. Actions: I created a checklist, delegated tasks to three colleagues, and set up a shared drive so everyone could track progress. Result: the booth was ready two days early, and the team generated thirty qualified leads. Luna: That works. It's not a huge project, but it shows initiative, organization, and results. Lucas: Exactly. Now, a common trap I see: candidates use 'we' too much. They say 'we worked together and we achieved...' The interviewer can't tell what you personally did. So you need to say 'I identified the issue, I convened the team, I set the timeline.' You can say 'we' for the execution, but you need to own the leadership. Luna: Right. And the opposite trap: using 'I' for everything, which makes you sound like you didn't actually lead anyone. Lucas: Yeah. The sweet spot is: 'I set the direction and delegated the pieces. The team executed, and I was accountable for the outcome.' That's leadership. Luna: I want to push back a little on one thing. Do you think the STAR method can make answers sound too scripted? Lucas: It can, if you treat it like a fill-in-the-blank template. But the best candidates use it as a mental framework, not a script. They tell the story naturally, and the structure is just there to keep them from rambling. Luna: So you'd recommend practicing out loud, not just writing it down. Lucas: Absolutely. Record yourself. You'll hear where you get lost or use filler words. And time it — a good answer to this question should be about ninety seconds to two minutes. Any longer and you risk losing them. Luna: Speaking of time, I know we're nearing the end, but there's one more thing I want to highlight: if you're listening and you've got an interview coming up, we hope this episode has given you a clearer picture of what that question is really asking. And if you've found our episodes helpful, especially when thinking through career moves or interview strategies, listener support is what keeps this show ad-free and focused on practical advice. Lucas: Yeah. If you'd like to support the show, you can buy us a coffee at buy me a coffee dot com slash fexingo. It's a small gesture that goes a long way in helping us keep producing these episodes. Luna: And we genuinely appreciate every single one. Now, back to the topic — Lucas, what's one thing you'd tell a candidate to avoid at all costs in this answer? Lucas: Don't pick a project that failed and blame the team. If you choose a failure, own your part in it. But honestly, for this question, pick a success. You want them to walk away thinking 'I'd trust that person with a project.' Luna: I think that's the bottom line. Thanks, Lucas. Lucas: Thanks, Luna. Good luck out there, everyone.