"Why do you want this job?" is not asking how badly you want a job. It is asking why you want this one — and "I'm passionate and it's a great opportunity" answers neither.
What the interviewer is actually checking
Three quiet questions sit under this one: Do you understand what this role actually does? Did you look at us specifically, or paste us into a template? And will you still be here in two years? A good answer settles all three without you ever naming them. A vague answer — "I love your mission, this is an amazing chance to grow" — settles none, because it would fit any company on earth. If your answer would work for a competitor with the name swapped in, it is not an answer yet.
"I'm really passionate about this field and I think this would be a great opportunity to grow my career with a company that's doing exciting things."
"Your team just moved support in-house, and this role owns that transition. I spent two years untangling exactly that at my last job, and I want to build the playbook this time instead of inheriting one."
The four-part answer
You do not need to be clever. You need to connect four dots, in roughly this order:
- The role — one specific thing this job does that genuinely interests you. Pull it straight from the posting.
- The company — one concrete reason it is this employer, not the category. A product you use, a recent move, how they work.
- Your skills — the bridge: a thing you have actually done that maps to what they need. Show impact, not just activity.
- Your growth — where this role takes you next, framed as something you will give as much as get.
Hit all four and you have answered "do you get the job, did you research us, and will you stay" in about forty seconds — without sounding like a checklist.
Do the homework that makes this easy
The reason this question feels hard is usually that the research is missing, not the words. Fifteen minutes before the interview:
- Re-read the posting and underline the one duty you would be happiest doing.
- Find one specific, recent thing about the company — a launch, a blog post, a value they actually practise. Not the homepage tagline.
- Pick the one accomplishment of yours that most resembles the underlined duty.
That is your whole answer, already assembled — you are just saying it out loud.
A model answer you can adapt
Here is the four-part shape with the blanks marked. Keep it tight; this should take 30–45 seconds, not two minutes.
"A few things lined up for me here. The role centres on [specific duty from the posting], which is the part of my work I actually look forward to — at [previous job] I [specific thing you did and the result, e.g. rebuilt the onboarding flow and cut drop-off from X% to Y%]. And it's specifically [Company] because [concrete, researched reason — a product, a recent move, how the team works]. What pulls it together is that I want to [next step you're growing toward] while bringing [the skill they need] from day one, and this role is set up for exactly that."
Notice what it never says: passionate, opportunity, exciting, dream job. The enthusiasm comes through in the specifics. Specifics are the only thing that sounds sincere, because they are the only thing you cannot fake from a template.
Two traps to skip
- Making it all about you. "This is a great step for my career" is true but one-sided. Pair every "what I get" with a "what I bring."
- Leading with money or logistics. Pay, location, and the commute are fair reasons — just not the answer to this question. Save them for the offer stage. If you want to sanity-check the range first, Canada's Job Bank lists typical wages by role and region.
Pick one job you actually want. Open the posting, underline the single duty you'd most enjoy, find one specific recent fact about the company, and write a role-specific answer using the four-part script above. Read it out loud once. If it would still make sense with a competitor's name swapped in, it isn't done — add the detail that only fits this job.
Useful: Government of Canada Job Bank — typical wages and duties by role and region, handy for grounding your research.
Comments