"Why do you want to work here?" sounds like small talk. It isn't. It's one of the most revealing questions in the interview, because it separates the candidates who chose this company from the candidates who applied to two hundred and are hoping something sticks.

The trap is that a generic answer feels safe — "I'm looking for growth, and you're a great company" — while actually confirming the interviewer's worst suspicion: you don't know or care what makes this place different. Here's how to answer so it does the opposite.

What the interviewer is really asking

Underneath the question are three quieter ones:

Did you do your homework? Specific knowledge of the company signals genuine interest and basic diligence.
Will you actually take the offer? Hiring is expensive. They're screening out people likely to ghost or use them as a backup.
Do your motivations fit the role? Someone who wants deep technical ownership will burn out in a coordination-heavy job, and vice versa.

A strong answer quietly puts all three to rest.

The three-part structure

The most reliable answer weaves together three threads:

The company — something specific about this employer: its product, mission, market position, engineering culture, or a recent move you can point to.
The role — why this particular job fits what you're good at and want to do more of.
You — the honest personal thread that connects the two, so it sounds like you rather than a press release.

Miss the first and you sound generic. Miss the second and you sound like a fan, not a candidate. Miss the third and you sound rehearsed.

Do the research that makes this easy

You can't fake specificity, so gather raw material before the interview:

The product. Use it if you can. "I signed up and noticed…" beats anything abstract.
Recent news. A launch, funding round, expansion, or public roadmap gives you something current to reference.
The mission and values, but only if you can tie them to something concrete you've done. Reciting values back is worse than skipping them.
The role itself. Re-read the job description for the problems they want solved, not just the requirements.

Ten focused minutes here is the difference between a specific answer and a hollow one.

Example answers

For a product company (individual contributor):

"I've used your product for about a year, and the thing that stands out is how much care goes into the small interactions — that's rare, and it tells me the team values craft. This role is squarely on the part of the product I use most, and I'd rather go deep on something I actually understand as a user than start cold somewhere else. That combination — a team that sweats the details on a product I already like — is why I applied here specifically rather than broadly."

For a mission-driven organisation:

"I spent two years in adjacent work and kept running into the exact problem you're solving, so I know first-hand it's real and underserved. What convinced me to apply wasn't the mission on its own — plenty of companies claim one — it was that your last two launches were actually aimed at it rather than at easier revenue. I want my work to move that needle, and this role is where I can do it with the skills I already have."

For a career pivot:

"I'm moving from [previous field] into this one deliberately, and I looked for a team where the transition adds something rather than just costs you ramp-up time. Your customers are the people I spent five years serving, so I understand them in a way a typical hire wouldn't. This role lets me pair that domain knowledge with the new skills I've been building — that overlap is exactly why this company, and not a generic one, made sense."

Adapt the specifics; keep the structure.

Mistakes that sink the answer

Pure flattery. "You're the best in the industry" is unfalsifiable and forgettable.
All about you. "It's a great step for my career" answers why you want a job, not why you want this one.
Perks. Salary, remote work, and free lunch may be true, but leading with them signals the job is interchangeable.
Obvious blanks. "I love your commitment to innovation" about a company whose site you never opened is transparent, and interviewers have heard it a thousand times.

Practise it out loud

This is a question you can nail with rehearsal, because it's almost guaranteed to come up in some form. Draft your three threads, then say the answer aloud until it sounds like conversation, not recitation. An AI mock interview is useful here — it asks the question, lets you hear your own answer, and gives feedback on whether it's specific or generic. You can also pull the full set of likely questions for your role so this isn't the only one you've prepped.

Frequently asked questions

How long should the answer be? Around 60–90 seconds. Long enough to hit all three threads, short enough to stay a conversation opener rather than a monologue.

What if I'm applying mainly for the money or to leave a bad job? Be honest with yourself, then find the genuine secondary reason — the work, the product, the team — and lead with that. Everyone knows compensation matters; the question is whether anything else drew you here.

Is "Why do you want to work here?" different from "Why this role?" Related but not identical. "Here" leans on the company; "this role" leans on the job fit. A good answer to either touches both, just weighted differently.

How much company research is enough? Enough to say one specific, true thing the average applicant couldn't. The product, a recent launch, or a concrete detail from the job description usually does it.

Answered well, this question is a gift: it's the moment you get to prove you chose them on purpose. Candidates who prepare for it stand out precisely because so many don't.

How to Answer "Why Do You Want to Work Here?" (With Examples)