That's what 80% of candidates say, give or take a few nouns. And every interviewer who hears it thinks the same thing: this person spent 4 minutes on our About page and is telling me what they think I want to hear.
The question "Why do you want to work here?" is asked in nearly every interview. It's also the question with the widest gap between what candidates think the interviewer wants and what the interviewer actually wants. Closing that gap is worth more than any amount of LeetCode practice.
What the interviewer is actually asking
"Why do you want to work here?" sounds like it's about the company. It's not. It's about you. Specifically, the interviewer is trying to answer three hidden questions:
1. Have you done real research, or are you just spraying applications? In a market where people send 200 Easy Apply applications, interviewers are trying to separate the candidates who specifically chose their company from the ones who applied everywhere. The bar here is low — most candidates clear it by mentioning one specific thing about the company. But "one specific thing" means something you couldn't say about their three closest competitors.
2. Do you understand what this job actually involves? A surprising number of candidates can't describe the day-to-day work of the role they're interviewing for. "Why do you want to work here?" is a soft way of testing whether you understand what you'd be doing. If your answer is all about the company's mission and nothing about the actual work, that's a yellow flag.
3. Will you stay? Hiring is expensive. Onboarding takes months. Every interviewer is quietly calculating whether you'll still be here in 18 months. Your answer to "why here?" is one of the strongest signals they have. If your reasons are generic ("great culture," "exciting space"), they're reasons you could have for any company — which means you'll leave for any company too.
The framework: Specific + Selfish + Surprising
The best answers to "why here?" share three qualities. They're specific to this company, they're honestly selfish (they explain what you get out of it, not just what you'll contribute), and they include at least one detail that surprises the interviewer.
Here's the structure:
Sentence 1: The specific thing. One concrete, non-generic observation about the company that shows real research. Not "I love your mission" — something you noticed by actually using the product, reading their engineering blog, or talking to someone who works there.
Sentence 2: The selfish reason. Why this specific opportunity is good for your career. Not "I want to give back" — what you personally want to learn, build, or become. Interviewers trust selfish honesty more than altruistic performance.
Sentence 3: The connection. How your specific background makes you unusually suited for this specific role at this specific company. Not "I have 5 years of experience" — the particular thing about your history that makes this a non-obvious but compelling match.
Good answers vs. bad answers
Let me show you the difference with real examples.
Bad answer (generic)
"I'm excited about Stripe because you're a leader in payments infrastructure. I'm passionate about fintech and I think my experience in backend engineering would be a great fit for your team."
Why it fails: You could say this about any payments company. "Leader in payments infrastructure" is from their Wikipedia page. "Passionate about fintech" is meaningless. "Great fit" is the interviewer's job to decide, not yours.
Good answer (specific + selfish + surprising)
"I've been using Stripe's API for three years at my current company, and I've noticed something interesting — your documentation is better than most companies' actual products. I've read your engineering blog posts about how you do API versioning, and the approach to backwards compatibility is something I've been trying to implement at a much smaller scale. Honestly, I want to work here because I want to learn how to build APIs at that level of quality. My background is in building payment integrations for marketplaces — I've dealt with the edge cases of split payments and multi-party settlements — so I'd be coming in with real context on the problems your customers face."
Why it works: The interviewer now knows you've actually used the product, read their engineering blog, have a specific technical interest (API design), and have relevant domain experience. You've also been honestly selfish — "I want to learn" — which is more believable than "I want to contribute to your mission."
Bad answer (flattery)
"Your company culture seems amazing. I've read the Glassdoor reviews and everyone says the work-life balance is great. I'm looking for a place where I can grow and be supported."
Why it fails: This is about what the company gives you, with no indication of what you bring. Also, citing Glassdoor reviews in an interview is like citing Yelp reviews at a restaurant — it's not wrong, but it's not impressive.
Good answer (for a non-technical role)
"I spent last weekend going through your onboarding flow as a new user, and I got stuck at the team invitation step — the error message when you enter an invalid email just says 'invalid input' with no guidance. That's the kind of problem I love solving. At my last company, I redesigned the error messaging system for our signup flow and reduced support tickets by 40%. I want to work here because your product is genuinely good but the rough edges in the user experience are exactly the kind of problems I'm best at fixing."
Why it works: You demonstrated initiative (you actually used the product), identified a real problem (not a theoretical one), connected it to a measurable achievement, and explained why this specific opportunity excites you. The interviewer is now thinking "this person would start adding value on day one."
The research that actually matters
Most interview prep advice tells you to "research the company." But it doesn't tell you what kind of research actually helps. Here's a ranked list, from most to least useful:
1. Use the product. Nothing beats first-hand experience. Sign up, go through the onboarding, try the core features, hit the edges. If it's a B2B product you can't access, watch demo videos or read case studies from their customers.
2. Read their engineering or company blog. Not the marketing blog — the one where employees write about real problems they've solved. This gives you specific, technical talking points that show genuine interest.
3. Look at their recent job postings. What roles are they hiring for? If they're hiring 15 engineers and 0 designers, that tells you something about their priorities. If they just posted a Head of Sales role, they're probably about to push into enterprise. These patterns give you context that most candidates don't have.
4. Check their LinkedIn for recent hires. Who did they hire in the last 3 months? What backgrounds do those people have? This tells you what the company actually values, which might be different from what the job description says.
5. Talk to someone who works there. Even a 15-minute coffee chat with a current employee gives you more insight than hours of web research. And mentioning "I talked to Sarah on your data team" in an interview is the strongest possible signal of genuine interest.
The answer you should never give
There's one answer that's worse than a generic answer, and I hear it constantly: "I'm open to anything. I just want to learn and grow."
This sounds humble. It's actually a red flag. It tells the interviewer that you don't have a clear sense of what you want, which means you'll either be dissatisfied when the role doesn't match your unstated expectations, or you'll leave as soon as something shinier comes along.
Having a specific, honest reason for wanting a specific role at a specific company — even if that reason is "I want to learn your approach to X because it's the best in the industry" — is always better than open-ended flexibility. Specificity signals conviction. Conviction signals retention. And retention is what every interviewer is quietly optimizing for.
The next time someone asks you "Why do you want to work here?", don't tell them what you think they want to hear. Tell them something specific you noticed, something honest you want, and something about your background that makes the match non-obvious. That's the answer that gets remembered.
