How to answer "Why do you want to work here?" — specificity wins

This question has one failure mode and it's fatal: the generic answer. "You're a great company with a strong culture and I'd love to grow here" could be said to literally any employer — which tells the interviewer you haven't thought about them at all. The fix is specificity. A great answer proves you did your homework, connects the company to something real about you, and points at what you'd contribute. Here's the framework.

What they're actually checking

Three things at once: motivation (do you actually want this, or just any job?), fit (will you thrive in how they work?), and diligence (did you bother to research us?). A vague answer fails all three. A specific one passes all three in a single breath, because specificity can only come from having genuinely looked.

The framework: Company → You → Fit

1. Company. Something specific and true about them — a product decision, a value they act on, a problem they're tackling, the way they work. Not the boilerplate from their homepage; something that shows you looked past it.
2. You. Why that specific thing connects to what you care about or want to do. This is what makes it your answer and not a compliment anyone could give.
3. Fit. What you'd bring to it — a short bridge from their world to your contribution.

The whole answer lives or dies on the first beat being specific. "You're growing fast" is generic. "You just opened the reliability problem up to the whole eng org instead of siloing it, and that's exactly the environment I do my best work in" is specific — and impossible to fake without research.

A worked example

"A few things, but the specific one: I read that you rebuilt your onboarding around getting a user to their first real result in under five minutes, even at the cost of hiding advanced features early. That's a real point of view about product — most teams say 'simple' and then ship a settings maze. I care a lot about that kind of ruthless focus on the first-use moment; it's what I spent the last two years doing on my growth team. So this feels like a place where the way I already think about the work is the way the team thinks about it."

Company (a specific, true decision) → You (why it matters to you) → Fit (what you'd bring). No boilerplate, no flattery.

How to research it fast

You don't need hours. Read the company's recent blog posts or changelog, their careers/values page (read past the slogans to what they actually reward), recent news or a founder interview, and the job description itself for what they're emphasizing. Pick the one thing that genuinely resonates and build the answer around it. Doing this company research well is a skill in itself — it's also exactly what a good interview prep tool can accelerate, surfacing the specifics worth mentioning so you walk in with a real point of connection.

Common mistakes to avoid

• The generic answer. Anything you could say to any company ("great culture, room to grow") signals zero research.
• Making it all about you. Salary, commute, prestige, "it's a stepping stone" — these answer "why this job for me," not "why this company." Save them.
• Empty flattery. "You're the industry leader and I admire you so much" is a compliment, not a reason. Specifics over praise.
• Homepage boilerplate. Reciting their tagline back to them proves you skimmed, not that you understand them.
• No connection to you. A fact about the company with no tie to your own motivation is just trivia. The "You" beat is what makes it land.

The bottom line

"Why do you want to work here?" is a research test disguised as a motivation question. Name something specific and true about the company, connect it to what you genuinely care about, and bridge to what you'd contribute. One real specific beats a paragraph of praise — because it's the one thing a candidate who didn't do the work can't produce.

Related: Why should we hire you? · Tell me about yourself