When an interviewer asks “why do you want this job?”, they're not fishing for compliments. They're checking three quiet risks: will you actually stay, will you care once the novelty wears off, and do you understand what the job really is? A vague answer doesn't just underwhelm — it reads as “applied to fifty places, remembers none of them.”
The three ingredients of a good answer
A strong answer braids three specific threads:
- The role: something about the actual work that fits where you're trying to grow.
- The company: one true, researched detail you couldn't have said about a competitor.
- The fit: why you're a sensible match for them, not just why they'd be good for you.
The role: this job is [specific responsibility], which is [why it fits your direction]. The company: I've been following [specific, true thing you researched], and [why it matters to you]. The fit: I'd be useful here because [the overlap between their need and your strength].
Do the research that makes it non-generic
You need one detail so specific it couldn't be swapped onto another company. Not “I love your mission” — everyone says that. Try: a recent launch you actually used, a product decision you have an opinion on, a priority hinted in the job description, something a founder said on a podcast. One real detail beats a paragraph of praise.
Making it entirely about you — “this role would help me grow / get to the next level / learn a lot.” Growth is fine as a thread, but if all three ingredients point at your benefit, you've answered “why do you want it” without a word on why they should want you there.
Sample answers by level
“I want a first role where I'll be stretched and actually mentored, and your engineering blog makes it obvious you take that seriously — the post on how you onboard grads sold me. The work is backend-heavy, which is the direction I've been teaching myself toward, so it's a place I could grow fast and contribute reasonably quickly.”
“I've spent three years on payments and I want to go deeper, not broader — this role is squarely reliability at scale, which is my favourite problem. I also noticed you just moved to event-driven infra, and that's exactly the shift I helped run at my last company, so I'd hit the ground with real context.”
“I'm at the point where I want scope over any single system, and your team is at the inflection where platform and people both need attention — that's the work I most want to do. Your public roadmap around self-serve tooling lines up with what I spent last year building, so I could shape it rather than just staff it.”
Tailoring, especially for career-switchers
- Technical roles: anchor to the actual stack or problem space, not perks. “You work on the exact latency problems I find satisfying” beats “great culture.”
- Non-technical roles: tie your interest to the market, customer, or product stage you want to work in.
- Career-switchers: this is your best question. Use it to make the switch feel intentional. “I've deliberately been moving from support into product because I kept wanting to fix the root cause, not the ticket — and your team owns the roadmap, not just the backlog.” Now the pivot reads as direction, not desperation.
Weak answer → better answer
Flattery + salary
“You're a really well-known company with a great reputation, the pay looks competitive, and it seems like a good opportunity for my career at this stage.”
Specific + mutual
“I've been using your API for a side project, and the developer experience is genuinely the best I've touched — I want to work on the thing I already admire. And you're scaling that platform now, which is exactly the reliability work I'm strongest at.”
Why it works: the better answer proves you've engaged with the actual product and connects it to what you'd contribute. The weak one — reputation and pay — describes something true of a hundred companies and signals you'd leave for the next one that pays slightly more.
Before the interview, write one sentence you could only truthfully say about this company. If you can't — if it would fit any employer — you haven't researched enough yet. Go find the detail, then say your full answer out loud.
What to do when you don't love the company
Sometimes the honest answer is “it's a solid role and I need the work.” You can't say that, but you don't have to fake a passion you don't feel either — that reads as false anyway. Find the true, smaller thread: a specific responsibility you'd genuinely enjoy, a skill you'd sharpen, a market you're curious about. Interviewers don't need you to be starstruck; they need to believe you'll show up engaged and stick around. A calm, specific, honest reason beats manufactured enthusiasm every time.
The same goes for a role that's a rung down or a slight sideways step. Frame it as a deliberate choice — “I want to go deep on X and this is where that work lives” — rather than something you're settling for. Ownership of the choice is what makes it convincing.
Where it fits in the loop
This question is the counterpart to “why should we hire you?” — together they show your pull toward them and your value to them line up. The research you do here also fuels the questions you ask the interviewer, since curiosity is the same signal from both sides of the table. And if you tend to freeze on open-ended questions like this, that's a going-blank problem worth practising against.
Test whether your reasons actually sound convincing
Run a realistic voice mock interview, get asked why you want the role, and hear how specific your answer really lands. Free to start — no credit card.
Start freeFrequently asked questions
How do you answer 'Why do you want to work here?'
Combine something specific about the role, a genuine detail about the company you could only know from research, and why you're a fit for them. Avoid empty flattery, salary, or making it only about your own growth.
How much company research do I need?
Enough to name one or two specific, true things — a recent launch, the product direction, a priority hinted in the job description. Depth beats breadth; one real detail outperforms generic praise.
Is it okay to mention salary or growth?
Career growth is fine as one thread, but don't make it the whole answer, and keep salary out of this question entirely — it belongs in the offer conversation, not the motivation one.