Artiluca™
← All interview questions

How to Answer “Why Do You Want to Work Here?” (Structure + Example)

The question is really “did you choose us, or would anyone do?” — and the answer is won or lost on one specific detail.

6 min read

The short answer

Name one specific, true thing about this company that genuinely draws you — the product, the problem they're working on, the stage they're at, how they visibly do the work — then connect it to what you want more of in your own work, and close with one line on what you bring to that overlap. Them, then you, then the fit.

The test for every sentence: could a candidate say it about any employer? “I'm impressed by your culture and growth” fails — it's a compliment addressed to nobody. “You're the only team I've seen publish its post-incident reviews, and that's how I want to work” passes, because it could only be said to them, and it proves you looked.

What is the interviewer actually asking?

Two things: did you do any homework, and will your motivation survive contact with the job. The first is a proxy for how you'll treat real work — someone who arrives at an interview unprepared arrives at client meetings unprepared. The second matters because motivation built on nothing specific evaporates in month three, and the interviewer has watched that happen before.

It's also a fairness check you can use on yourself. If you honestly can't name one thing about this company you'd miss at an identical job across the street, that's worth knowing before you accept an offer — not just before you answer a question.

What structure works best?

Them, you, fit — in that order. Open with the specific thing about the company (one or two sentences, concrete enough that it could only describe them). Then the honest connection to you: why that specific thing matches the work you want more of, said in terms of your own trajectory rather than flattery of theirs. Close with a single line of fit — what you bring to exactly that overlap.

Starting with them isn't a courtesy, it's positioning: it makes the whole answer evidence that you chose this company on purpose. Candidates who start with themselves (“I'm looking for a role where I can grow…”) describe a want any employer could satisfy — which is precisely the impression this question exists to catch.

Thirty to forty-five seconds is plenty. One specific done well beats three done thinly; a list of reasons reads as research notes, a single reason with roots reads as a decision.

How do you find the specific thing fast?

Use the product if you possibly can — twenty minutes inside it produces more genuine material than an hour on the About page. What surprised you, what's clearly hard about what they've built, what would you improve? Any of those, stated plainly, instantly separates you from every candidate who only read the careers page.

If the product isn't usable from outside, look at how they work in public: engineering or product write-ups, how leadership talks about decisions, what the job posting itself emphasizes and what it doesn't. The stage of the company is also a legitimate specific — “small enough that support still talks to the people building the product” is a real, checkable reason, not a compliment.

What should you avoid?

Reasons that are really about logistics: the commute, the salary, the hybrid policy, “I need a job.” All may be true; none answers what was asked, and each one tells the interviewer the honest answer is “nothing about you in particular.” Save compensation for the conversation where it belongs — it has one, and this isn't it.

Also avoid recited flattery — mission-statement quotes, “your amazing culture,” praise assembled from their own website. It's the homework equivalent of reading the back cover aloud. And never lead with what the company can do for you (“great name on a resume,” “strong training programme”) — even when true, it frames the hire as your stepping stone, which is a reason to choose you last.

A full example answer

“The honest starting point: I've used your scheduling product at my current job for about a year, and it's the only tool we've rolled out where the support team stopped getting complaints within a month. Somebody there is making unglamorous reliability decisions, and that's visible from the outside.

That's the kind of work I want more of. In my current support role the part I'm best at — and the part I volunteer for — is the unglamorous end: reproducing the weird bug, writing the workaround doc, closing the loop with the customer who found it.

So the fit, as I see it: you're hiring for exactly the temperament I already work in, and I'd be doing it on a product I already believe holds up.”

Written for a support candidate at a small software company — swap the specifics for yours. The shape: one concrete observation that could only be about them (a year of actually using the product), an honest match to the work the candidate already prefers, and a one-line fit. About 40 seconds spoken.

Common mistakes

  • Reasons that are really logistics — commute, salary, hybrid policy, “I need a job”
  • Mission-statement flattery assembled from their own website
  • Leading with what the company does for your resume
  • A list of three thin reasons instead of one with roots
  • A reason that fits any employer — the exact thing the question exists to catch

Frequently asked

What if it honestly is just a job I need?

Then find the true overlap, because it exists: something about this job — the product, the customers, the team size, the craft — that you'd pick over an otherwise identical job elsewhere. That preference is your honest answer. Needing a job explains why you're interviewing; it can't explain why you're interviewing here, and only the second question was asked.

How is this different from “why do you want this role”?

“This role” asks about the work — your skills against the day-to-day. “Work here” asks about the employer — why this company for that work. Interviews often blur them, so the safe structure covers both: the company specific first, the role fit in the close.

Is it okay to mention salary or benefits at all?

Not as your reason for wanting the company — it reframes the whole answer as “highest bidder.” Compensation is a legitimate conversation with its own moment, usually once mutual interest is established. Here, it displaces the only thing being tested: whether anything about them, specifically, drew you.

How long should the answer be?

Thirty to forty-five seconds: the specific about them, the honest link to you, one line of fit. If you're still talking at a minute, you've moved from a decision to a defence.

Now practise it — and get scored

The free practice set gives you five coached interview exercises — say your why-this-company answer out loud or write it, and get scored on the full rubric. Free account, no card.

Practise your answer free

Scored on a published rubric — see how scoring works. Never your accent.