Answer "why do you want to work here?" with specificity only research can produce: one concrete fact about the company that genuinely interests you, why it connects to your own trajectory, and what you'd contribute to it. The test is simple — if your answer works with the company name swapped out, it isn't an answer yet.
"I want to work somewhere with great culture and growth opportunities" survives having any company name substituted in, which means it says nothing about this one — and interviewers hear the generic version a dozen times a week. The question is a research check wearing a motivation costume: they're measuring whether you cared enough to learn anything true about them.
Real answers are built from particulars: the product decision they made that you'd have argued for, the engineering blog post that matched how you think, the market they're entering that you've worked in, the way their pricing model rejects the industry default. One genuine particular beats five compliments.
Part one, the researched fact: "You moved the whole product to usage-based pricing last year while everyone else sells seats." Part two, the personal pull: "I spent two years fighting seat-based pricing's incentives at my last company, so watching someone actually make the switch work got my attention." Part three, the contribution: "and this role owns the monetization roadmap, which is exactly the problem I want to keep working on."
Fact, pull, contribution — about 45 seconds. The pull is the part candidates skip and the part that makes it believable: a fact without a personal reason reads as flattery researched ten minutes before the call.
Never lead with what the company does for you — salary, brand on your resume, remote policy, "it seems like a great stepping stone." All may be true; none belong in this answer, because the question is scored as a proxy for how long you'll stay and how much you'll care while there.
Also avoid recited flattery — mission statements quoted back, "I've always admired this company" without a supporting specific, and superlatives you can't defend. If you genuinely struggle to produce one specific reason for this employer, treat that as information for you: interviews are sampling devices, and an answer you have to fake is data about the application itself.
Twenty minutes of research: the company's recent launches or announcements, an engineering or product blog post, the founders' stated positions, and the job description's priorities. Pick the one item that genuinely interests you and build fact-pull-contribution around it.
Not in this answer. Compensation is a legitimate factor discussed in its own conversation, but this question is scored as a proxy for engagement and retention. Answers centered on what the company gives you read as flight risk.
You still need one true particular per company — a product choice, a market, a technical approach. If twenty minutes of research produces nothing you genuinely find interesting, that's worth noticing before you invest interview loops there.
The same specificity should run through your resume — tailor it to the company's actual language and score it free to see how well it matches.
