Why This Company? The Question That Loses More Offers Than Any Other

Why this question is so badly answered

If you ask twenty interviewers what behavioral question they ask in every interview, "why do you want to work here" will be on most of the lists. If you ask the same twenty interviewers what answer they hear most often, the answer will be some variation of "I really admire your company, I think the mission is important, and I'd love to be part of the work you're doing."

That answer is wrong, and interviewers know it's wrong, and they score it accordingly. It's wrong because it could be said about literally any company. It demonstrates no research, no specificity, no actual connection to the candidate's interests. The interviewer hears it and thinks: this candidate is shotgunning applications. The interviewer is probably right.

The reason this question is so badly answered is that candidates feel awkward giving a real answer. A specific answer requires research, and research requires effort, and effort feels disproportionate when you're applying to ten companies and you don't know which one will respond. So candidates hedge with generic enthusiasm and hope the interviewer will fill in the blanks.

Interviewers don't fill in the blanks. They write down "generic answer" and move on. The question may not feel decisive — it's not a coding problem or a behavioral STAR — but it shapes the impression the interviewer carries through the rest of the interview, and the impression matters at debrief time.

This post is about how to answer it well.

The three-part answer

A strong "why this company" answer has three parts.

Part 1: A specific researched fact. Not the company's mission statement. Not a product everyone knows about. Something that demonstrates you've actually looked at the company recently — a recent product launch, a public engineering blog post, a strategic move you noticed, a customer story, an interview the CEO gave, a specific job description detail that caught your eye. The more specific and recent, the better.

Examples that work: - "I read your engineering blog post from last month about how you migrated your search infrastructure to..." - "I noticed in your last earnings call that you mentioned [specific strategic initiative]..." - "I was specifically interested in the [product] launch from Q1 because..."

Examples that don't work: - "I really admire your company's mission" (generic) - "I love your products" (generic and probably untrue) - "You're a leader in the industry" (generic and obvious)

Part 2: A personal connection. Why does that specific fact matter to you? This is where you make the answer personal — not just researched, but genuinely connected to your interests, your background, or your career direction.

Examples that work: - "...and that resonated with me because in my last role I worked on a similar migration and learned that the bottleneck was X, which is exactly the trade-off your post discussed" - "...and that's interesting to me because I've been thinking about [specific topic] for the last six months" - "...and that aligns with the kind of problem I want to be working on next, which is why I specifically reached out to [team]"

The personal connection prevents the answer from sounding like you read a press release. It makes the research feel motivated rather than obligatory.

Part 3: A forward statement. What specific contribution would you make if hired? Not "I'd work hard" or "I'd be a great team member." Something concrete — a skill you'd bring, a project type you'd want to work on, a specific way you'd add value.

Examples that work: - "...and given my experience with [X], I think I could specifically contribute to [Y]" - "...which is why I'd want to work on the [team] specifically — it's the team where my skills in [X] would matter most" - "...and I'd hope to bring the perspective I gained from [previous role] to the [specific challenge] you mentioned in the JD"

The forward statement closes the loop. It moves the answer from "why do you like us" to "why should we hire you," which is the question the interviewer is actually trying to answer.

• "I read your engineering blog post from last month about how you migrated your search infrastructure to..."
• "I noticed in your last earnings call that you mentioned [specific strategic initiative]..."
• "I was specifically interested in the [product] launch from Q1 because..."
• "I really admire your company's mission" (generic)
• "I love your products" (generic and probably untrue)
• "You're a leader in the industry" (generic and obvious)
• "...and that resonated with me because in my last role I worked on a similar migration and learned that the bottleneck was X, which is exactly the trade-off your post discussed"
• "...and that's interesting to me because I've been thinking about [specific topic] for the last six months"
• "...and that aligns with the kind of problem I want to be working on next, which is why I specifically reached out to [team]"
• "...and given my experience with [X], I think I could specifically contribute to [Y]"
• "...which is why I'd want to work on the [team] specifically — it's the team where my skills in [X] would matter most"
• "...and I'd hope to bring the perspective I gained from [previous role] to the [specific challenge] you mentioned in the JD"

A worked example

Question: "Why do you want to work at [company]?"

Generic answer (loses): "I really admire [company] and I've been following you for a while. I think the mission is important and the products are great. I'd love to be part of the team and contribute to what you're building."

Specific answer (wins): "I read your engineering blog post from March about how you migrated your real-time analytics pipeline from Kafka to your custom internal system, and I was specifically interested because in my last role I worked on a similar problem at smaller scale and ran into exactly the trade-offs your post described. I've been thinking a lot about that class of problem and I'd want to work on the analytics platform team specifically — I think the experience I have with high-throughput streaming systems would be relevant, and the problems your team is working on are the ones I want to be working on next."

The second answer is 100 words. It's not memorized; it's structured. It demonstrates specific research, specific personal connection, and a specific forward statement. The interviewer hears it and thinks: this candidate is here for real reasons, and they can articulate why.

What "research" actually means

The research that produces the specific answer takes about 30 minutes. Not hours.

10 minutes on the company's recent public output. Their engineering blog, their product blog, their recent press releases, their last earnings call (for public companies), a podcast interview with a leader. Read with a pen — note one or two specific things that catch your interest.

10 minutes on the team you're interviewing with. Who's on the team, what do they ship, what does the hiring manager's LinkedIn say about their priorities, what does the JD specifically emphasize. The JD often has hints about what the team actually cares about that generic prep guides miss.

10 minutes on the broader context. What's happening in the industry, who the competitors are, what strategic moves other companies have made recently that this company has either followed or rejected.

That's 30 minutes per company. Multiply by the number of companies you're actively interviewing with — usually three to five at any given time — and you're talking about a couple of hours of work that pays off across multiple interviews.

The candidates who skip this work are the ones giving generic answers and losing offers to candidates with worse resumes who did the research.

How to answer it under pressure

The "why this company" question often comes early in the interview, sometimes literally as the first question after introductions. This timing makes it especially likely to be answered badly — candidates haven't warmed up yet, the nervous-system arousal is at its peak, and the temptation to default to generic enthusiasm is highest.

The fix is to rehearse this answer verbatim. Not the entire answer — that produces scripted-sounding delivery — but the opening sentence. "I read your [specific thing] from [specific date] and I was specifically interested because..." Memorize the opening. Let the rest follow naturally. The opening sentence buys you ten seconds while your brain catches up to the moment, and by the time you get to the personal connection and forward statement, you're warmed up enough to deliver them naturally.

Cornerman recognizes the "why this company" question pattern and surfaces a cue with the rehearsed opening — "Why company — start with [specific researched fact]." It's a retrieval prompt, not a script. The opening sentence is yours; the cue just makes sure you don't blank on it under first-question pressure.