The short answer
What they’re really asking
“Why do you want this job?” sounds casual, but the interviewer is quietly checking three things at once:
- Do you actually understand the job? A vague answer suggests you have not really read past the title.
- Does it genuinely fit you? If your reasons match what the role offers, you are more likely to be motivated and to stay.
- Did you bother to look into us? Specifics prove effort; generic praise proves the opposite.
Answer those three and you have answered the question — even though none of them was stated out loud.
The three ingredients
A strong answer weaves together the role, the company, and you. Miss one and it wobbles.
How to build your answer
- 1
Do fifteen minutes of real research.
The product, recent news, the team’s current focus, the company’s stated values. Find two or three specifics you can genuinely speak to. - 2
Name what draws you to the role.
Read the job description and find the part that actually excites you. Be honest — the real reason is more convincing than the impressive one. - 3
Connect it to your direction.
Why is this the right next step for you specifically? One sentence linking the role to where you are heading. - 4
Say it out loud and cut the flattery.
Remove anything that could be said to any company. What remains should be specific, true, and yours.
Worked examples
I’ve spent five years at large companies where the systems were already built and my job was to keep them running. What draws me here is the stage you’re at — the payments infrastructure is still being shaped, and I want to be one of the people shaping it rather than maintaining it. I’ve read about the reliability push you made last year, and that’s exactly the kind of problem I want to own next.
Honestly, I came to this indirectly — I used your product for two years in my last role and kept thinking about how it could be better. When I saw this opening, it connected the thing I’m good at with the thing I actually care about. I want to work on a product I already believe in, for the users I used to be one of.
“Why this company” vs “why this role”
Sometimes the question is pointed: “why us?” or “why this role?” They are close but not identical. “Why this company” wants your reasons for them over their competitors — mission, product, culture, the specific work they do. “Why this role” wants your reasons for this job over other jobs you could take — the scope, the growth, the kind of problem. If you are unsure which they mean, cover both briefly; a full answer usually touches each.
When the honest reason is “I need a job”
Sometimes that is the truth — but it is not the answer, because it says nothing about this role over any other, and that is exactly what they are testing. The good news is that there is almost always a real reason underneath, even a small one: the work is closer to what you enjoy, the company does something you respect, the role is a step toward where you want to be. Find that specific thing and lead with it. You are not lying about needing the job; you are answering the question they actually asked.
Common mistakes
Generic flattery.
Instead: “You’re a great company” could be said to anyone. Name something only this company would recognise.
Making it all about you.
Instead: “Great for my career” is a reason to take the job, not a reason they should give it to you. Balance what you want with what you bring.
Obvious lack of research.
Instead: If your answer would fit any company in the industry, do fifteen more minutes of homework.
Only talking about salary or perks.
Instead: Those may be real, but lead with the work. Compensation is for the offer stage.