Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / Why Your Interview Story Feels Flat
Transcript
- Lucas: The problem isn't that candidates don't have stories. It's that they've been taught to sand down every rough edge until the narrative is smooth enough to slide off the brain without leaving a mark. You know what I mean? The classic STAR framework—Situation, Task, Action, Result—is supposed to be the gold standard, but lately, it feels like everyone is just filling out a template. Luna: Exactly. It creates this uncanny valley of competence where the answer is perfect, so you can't trust it. If I hear someone describe a conflict where they calmly talked through feelings and reached consensus, I start wondering if they even had a conflict or if they're just reciting a HR module. Lucas: Right. And here is the thing most people miss: hiring managers in September twenty twenty-six aren't looking for perfect resolution. They are looking for friction. They want to see where you got stuck, where you made a bad call, and how you corrected course. The polish is actually the red flag. When an answer is too clean, it signals that the candidate hasn't done the hard work yet. Luna: So we're seeing a shift from performance to documentation? Like, they want the scratch notes, not the final presentation? Lucas: Precisely. Let me give you a concrete example from a recent round of interviews I observed for a senior product role. The candidate was brilliant on paper. But when asked about a time she missed a deadline, she gave us this three-minute speech about how she delegated better next time. No anger, no stress, no miscommunication. Just a smooth pivot to process improvement. It was boring. It was safe. And it was useless. Luna: I bet the hiring team was dying to ask, 'Did you actually care about the project?' Because her answer erased any human element. Lucas: She didn't get the offer. The winner was a candidate who admitted she was afraid to tell her boss the feature wouldn't launch on time. She described the panic, the late-night spreadsheet, and the fact that she almost quit. That vulnerability gave the hiring manager data points: risk awareness, communication latency, emotional regulation. The loser gave us a textbook; the winner gave us a human. Luna: It’s interesting because vulnerability usually feels risky to the candidate. Why do they think hiding the mess is safer than showing it? Lucas: Because we’ve been conditioned by corporate training videos for two decades to believe that professionalism means emotional detachment. But in the current market, especially with remote work isolating teams, managers need to know who they can rely on when things go wrong. A candidate who admits fear is someone you can coach. A candidate who pretends fear doesn't exist is someone you can't predict. Luna: That makes sense. So the key is granularity. Specificity over sentiment. If you say 'I worked hard,' that's zero data. If you say 'I stayed up until two AM debugging the API,' that's one data point. Lucas: One data point. And if you add 'because I realized the initial architecture was flawed,' that's two. Now the interviewer knows you have technical judgment AND ownership. See how the second sentence does all the heavy lifting? Most candidates stop after the first. They’re trying to protect themselves, so they withhold the very evidence that proves their worth. Luna: But isn't there a line between being specific and just complaining? Where does 'I stayed up until two AM' become 'my boss is terrible'? Lucas: Great question. The line is agency. If you spend the whole story blaming external factors, you lose. If you spend the story explaining your internal decision-making process—even if that process was messy—you win. The difference between a complaint and a case study is whether you take responsibility for the outcome. Even if the outcome was bad, did you learn? Did you adjust? That’s the metric. Luna: So it’s less about the result being good, and more about the reflection being honest? Lucas: Exactly. And this brings me to the second part of the equation: the metrics. Candidates love to say 'I increased efficiency.' Increase by how much? By ten percent? By fifty percent? If you don't attach a number to your action, you're just saying you were busy. Busy is not valuable. Impact is valuable. And impact requires measurement. Luna: I see this all the time. People will say 'I improved customer satisfaction' but can't tell you the NPS score before and after. It’s like painting a picture without using color. Lucas: Or worse, they use inflated language. 'I revolutionized the workflow.' Please. You changed a spreadsheet formula. Say you changed a spreadsheet formula. Say you reduced processing time from four hours to forty minutes. That is a tangible, credible achievement. It’s also easier to verify. Hiring managers hate unverifiable claims because they create liability. Luna: So the strategy is: be boringly specific. Give me the numbers, give me the mistake, give me the fix. Lucas: Yes. And don't forget the context. In September twenty twenty-six, with AI tools handling so much routine analysis, the human value proposition is entirely about judgment. Your judgment is proven by the details you choose to share. If you share only the highlights, you look like a brochure. If you share the nuance, you look like a partner. Luna: Do you think this applies to junior roles too, or is this mostly for senior positions where judgment is the main differentiator? Lucas: It applies everywhere. For juniors, it’s about coachability. Can you articulate what went wrong? Can you admit you didn't know something? That’s huge. For seniors, it’s about strategic foresight. Can you explain why you pivoted away from a profitable idea because it wasn't sustainable? Both require the same ingredient: honesty about complexity. Luna: Okay, but let’s talk about the delivery. How do you actually structure this in a three-minute answer without rambling? Because once you start getting specific, it’s easy to go off the rails. Lucas: Use the PREP framework as a skeleton, but fill it with meat. Point: State your main conclusion. Reason: Explain why. Example: Give the specific, messy story. Point: Restate the lesson. But inside that 'Example' section, allow yourself to wander slightly. Talk about the tension. Talk about the alternative paths you considered and rejected. That’s where the intelligence shows. Luna: So the rejection of alternatives is key. Showing you thought about other options proves you weren't just lucky. Lucas: It proves you were deliberate. If you just picked option A and it worked, anyone could have done that. If you evaluated options A, B, and C, saw that B looked good on paper but failed in practice, and chose A despite the noise—that is leadership. That is what they are paying for. Luna: This is such a practical shift. Instead of performing perfection, you’re performing competence through transparency. Lucas: Performance implies acting. Competence implies doing. Stop acting. Start reporting. And while we’re talking about reporting, I want to pause for a second. This show is free because listeners like you keep it running. If today’s breakdown on interview granularity was worth a coffee to you, that’s the link — buy me a coffee dot com slash fexingo. It helps us keep the ads off and the research deep. Luna: Yeah, and honestly, if you’re using these tips to prep for a big interview this week, your support literally fuels the next insight we drop next Tuesday. Lucas: Back to the strategy. One last trap to avoid: the 'we' vs 'I' dilemma. Candidates often overuse 'we' to sound humble. 'We built the platform. We solved the crisis.' But the interviewer hired YOU, not the team. You need to clarify your individual contribution within the group effort. Luna: Right. Otherwise, how do they know you weren't just the person who fetched coffee during the crisis? Lucas: Exactly. Say 'Our team launched the platform, but I specifically designed the user onboarding flow, which reduced churn by fifteen percent.' There. You get credit for the team success, but you own the specific metric. That is the sweet spot. Humble, but precise. Luna: It’s basically data journalism applied to your own career. Report the facts, attribute the source, quantify the impact. Lucas: Love that framing. Data journalism. Because ultimately, the resume is just a headline. The interview is the article. And nobody reads headlines anymore. They read the substance. Make sure your substance has citations. Luna: So, if you’re prepping tonight, write down three stories. Strip out the fluff. Add the numbers. Admit the mistake. Then practice telling them like you’re briefing a colleague, not pitching a god. Lucas: Perfect summary. Be a colleague. Not a candidate. The moment you stop trying to impress and start trying to inform, you’ll stand out. And that’s usually the difference between a polite decline and a job offer. Luna: Thanks for listening, Lucas. I’ll see you next week. Lucas: See you. What’s the one metric you’re going to track this week?