Latest / Interview Prep with Fexingo: Behavioral Questions, Case Studies, and Hiring Manager Insights / How to Answer Why Do You Want to Work Here
Transcript
- Lucas: You sit down in the interview, the hiring manager smiles, and then they say: 'So, why do you want to work here?' And suddenly your mind goes blank. Luna: It is such a common opener, and yet I think it's one of the hardest questions to answer well. Lucas: Right. Because it sounds simple, but it's actually three questions in one. First, it tests whether you've done your homework. Second, it checks if you actually understand what the job entails. And third — and this is the subtle one — it probes whether you've thought about how you specifically add value. Luna: So the worst answer is something like: 'I love your mission' or 'I've always admired your company.' Lucas: Exactly. That's the equivalent of saying 'I want this job because I need a job.' So today I want to offer a three-part structure. Part one: name a specific challenge the company is facing. Part two: connect that challenge to something you've done. Part three: articulate what you'd do differently. Luna: Let's break that down. For part one, how do you find a legitimate challenge without insider knowledge? Lucas: You use public sources. I'm talking about recent earnings call transcripts, investor day presentations, industry news, even the company's own blog. For example, let's say you're interviewing at a midsize logistics startup. You read their most recent quarterly report and notice they highlighted a 20 percent increase in last-mile delivery costs due to fuel volatility. Luna: Okay, so now you have a real, specific problem. That's much better than 'I love your culture.' Lucas: Right. Then part two: you connect that to your experience. You say something like: 'I saw in your Q1 filing that last-mile costs jumped 20 percent. In my previous role at a regional carrier, I led a route-optimization project that cut our fuel spend by 12 percent within six months. That experience makes me confident I can help tackle a similar challenge here.' Luna: And part three is where you show you're not just rehashing the past — you're thinking forward. Lucas: Exactly. You add: 'Specifically, I'd start by analyzing your current route density and then pilot a dynamic scheduling algorithm in one region. Based on my prior results, I'd aim for a 10 percent reduction in fuel costs within the first year.' Now they see you as someone who can solve their actual problem, not just a candidate who rehearsed a script. Luna: What about the trap of oversharing personal motivations? Like 'I want to work here because I need more flexibility for my family' or 'I'm passionate about this industry.' Lucas: Those can be honest, but they're risky. Unless the interviewer explicitly asks about work-life balance or passion, leading with personal reasons can make it seem like the company needs to accommodate you before you've proven you can contribute. The safer bet is to frame everything around what you can do for them. Luna: So the formula really is: company's problem plus your proven skill plus your proposed action. That's it. Lucas: Exactly. And it works for any level — from entry-level to executive. The research changes, but the structure stays the same. Luna: Now I want to talk about the elephant in the room. What do you do when the company's mission doesn't resonate with you? Or when the job is just a stepping stone? Lucas: That's a great point. You don't have to fake enthusiasm about the mission. You can focus on the work itself. For example: 'I'm drawn to this role because it's a chance to build a data pipeline from scratch, and I've done that successfully twice before. That kind of challenge energizes me.' That's still honest and value-based. Luna: And it's more believable than pretending you've been dreaming about working for a widget manufacturer since childhood. Lucas: Right. Let me give one more concrete example. I recently coached a friend who was interviewing at a financial services firm that had been in the news for a data breach. Instead of ignoring it, she addressed it head-on. Luna: That's bold. How did she frame it? Lucas: She said: 'I read about the security incident last quarter. I know it's sensitive, but I see it as a moment of real commitment to rebuilding trust. In my last role, I helped implement a zero-trust architecture after a breach, and I'd love to bring that experience to help strengthen your security posture going forward.' Luna: Wow. That shows confidence, empathy, and problem-solving. I bet that impressed them. Lucas: It did. She got the offer. The key was she didn't avoid the negative — she turned it into an opportunity. Luna: And honestly, if today's episode helped you think through your own answer, that's exactly the kind of practical takeaway we hope you get from this show. Lucas: Yeah. And if it was worth a coffee to you, you can find us at buy me a coffee dot com slash fexingo. That support is what keeps these episodes ad-free and focused on real advice. Luna: Exactly. It's a small gesture that goes a long way for us. Lucas: Alright, back to the structure. One common mistake I see is that people prepare their answer in isolation, but they forget to tailor it to the specific interviewer. Luna: What do you mean by that? Lucas: If you're talking to a technical hiring manager, your answer should emphasize technical challenges and solutions. If it's a recruiter, focus on cultural fit and growth potential. The same three-part structure, but you emphasize different parts. I've seen candidates give a perfect answer but to the wrong audience. Luna: So you need to listen to the questions they ask earlier in the interview to gauge what they care about. Lucas: Exactly. If the first few questions were all about team collaboration, your 'why here' answer should include a line about how you collaborate. Mirror their priorities. Luna: What about when the company is a startup and there's no public information? How do you research then? Lucas: You look at their product, their customer reviews, their LinkedIn posts, even their job descriptions. A startup's job post often reveals what they're struggling with — they'll say 'we need someone to build our sales process from scratch' or 'you'll be responsible for creating our content strategy.' That's a direct clue to their pain point. Luna: So you can use their own words against them — in a good way. Lucas: Exactly. Another tactic: talk to current or former employees. A quick informational interview can give you insight that no press release will. Then in the interview you can say something like: 'I spoke with Sarah on your engineering team, and she mentioned that scaling the database is a current priority.' Luna: That shows serious initiative. I think a lot of candidates underestimate how much that stands out. Lucas: It does. And it also helps you avoid the second biggest trap: being generic. I've heard so many 'I want to work here because of the company culture' answers that I've lost count. If you can replace the company name with any other company and the answer still works, it's not good enough. Luna: So if your answer could apply to Google, Amazon, and a local bakery, scrap it. Lucas: Right. Your answer should be so specific that the hiring manager thinks: 'This person clearly wants this job at this company, not just any job.' Luna: And that's what separates the candidates who get offers from those who don't. Lucas: So to wrap up: research one specific challenge, connect it to your past success, and outline a concrete action plan. That's the formula. And practice it out loud. It sounds different in your head than it does spoken. Luna: Great advice. Next time someone asks you 'why here,' you'll have a real answer.