Most candidates treat this question as a warm-up. Interviewers treat it as a filter.
When someone asks why you want to work at their company, they are checking whether you did any homework, whether your goals match the role, and whether you are likely to stay. A vague answer ("great culture, strong reputation") tells them you would say the same thing to any employer.
The fix is not flattery. It is specificity.
Why this question matters more than it seems
Hiring is expensive, and a wrong hire is costly for both sides. Interviewers want evidence that you chose this role on purpose rather than because it was the next posting in your queue.
They are also testing your judgment. Can you find useful information, form an opinion, and connect it to your own work? That skill matters on the job, so the question doubles as a small work sample.
Do 25 minutes of targeted research
You do not need a week of preparation. You need the right sources and a clear goal: find two or three concrete details you can honestly connect to your experience.
Start with the job posting itself and underline the problems it hints at. A line like "build our first analytics function" tells you more than the company mission ever will. Then check the company's recent news, product updates, or blog for something that changed in the last six months.
Next, look at how leaders and employees talk publicly. Podcasts, conference talks, and LinkedIn posts often reveal priorities that never appear on a careers page. Finally, read a few customer reviews or forum threads. You will learn what people actually value about the product, and where it falls short.
Use a three-layer formula
A strong answer usually has three layers, and it should take about 60 to 90 seconds.
Layer one: the company. Name something specific that draws you in. It could be a product decision, a market they are entering, or a way the team works. Be precise: "You moved to usage-based pricing last year, and I have seen how that changes customer conversations" beats "I admire your innovation."
Layer two: the role. Explain why this particular job fits what you want to do. Connect it to the work itself, not the perks.
Layer three: you. Tie in a relevant strength or experience so the interviewer can see the match. This is where you move from admiring the company to being useful to it.
A sample answer
Here is how it might sound for a customer success manager applying to a software company:
"Two things stood out. First, your recent launch of the self-serve onboarding flow tells me the team cares about getting customers to value quickly, which is what I enjoy most about customer success. Second, this role owns renewals for mid-market accounts, and that is the segment where I have spent the last three years, bringing retention from 82 to 91 percent. I would like to work somewhere that treats onboarding as a product, not a checklist, and I think I could contribute a lot on the renewal side."
It is specific, it connects the company to the role, and it ends with what the candidate brings. Nothing in it could be copied to another employer.
Mistakes that make answers fall flat
Some patterns show up again and again.
Talking only about what you will gain is the first. "I want to grow my skills" is fair, but it should not be the whole story. Balance it with what you will contribute.
Reciting the mission statement is the second. Interviewers wrote or approved that language, and hearing it read back does not impress anyone.
Over-praising is the third. Excessive enthusiasm can sound insincere. Calm, precise interest is more believable than fireworks.
Finally, avoid negatives about your current employer. Even if you are leaving a bad situation, frame your answer around what draws you forward, not what pushes you out.
What if you are not sure you love the company?
This happens, especially early in a search. You do not need to invent passion, but you do need honest reasons.
Look for real points of alignment: the type of problem, the size of the team, the learning opportunity, the industry, or the manager you met. You can say, "I am drawn to the scope of this role and the chance to work on X." An honest, narrower answer beats an inflated one, and interviewers can usually tell the difference.
If you cannot find any real reason, that is useful information too. It may be a sign to reconsider the application.
Practice out loud
Write your three layers as short notes, not a script. Say the answer aloud, time it, and adjust until it lands under 90 seconds. Then try a second version for a different company. If you can swap in a new company by changing only a few sentences, your answer is still too generic.
CareerGraph's AI interview practice is a handy way to rehearse this. You can answer the question in your own words and get feedback on clarity and specificity before the real conversation.
The takeaway
"Why do you want to work here?" rewards candidates who do a little research and connect it to their own story. Pick two or three real details, tie them to the role, and finish with what you bring. Keep it short, keep it honest, and let the specifics do the persuading.
