Why Do You Want to Work Here Answer: Interview Guide

The interviewer is not asking you to admire the company. They are asking whether you understand the role and made a deliberate choice to apply. That is good news, because a weak answer to this question is usually not a sincerity problem — it is a specificity problem. A vague answer sounds insincere even when it is completely honest. A specific answer sounds genuine because it is checkable.

This guide gives you a short research routine, a three-part structure you can reuse for any employer, a worked example, and a checklist to run before the interview. It is a practical approach to the why do you want to work here answer rather than a script to memorise, and it works the same whether you are applying for your first role or your fifth.

What the interviewer is actually listening for

When someone asks "Why do you want to work here?", they are testing three things at once:

Do you know what the organisation does? Not the slogan — the actual work, the people it serves, the products or services it runs.
Do you know what the job involves? The day-to-day responsibilities, not just the job title.
Do your reasons connect to your own direction? Why this step, now, for you.

Generic praise gives the interviewer nothing to evaluate. "You're an industry leader with a great culture" could be said about hundreds of employers, so it tells them nothing about your judgement. It also invites the follow-up question you cannot answer: which part of the culture?

Honesty matters here for a practical reason. Any claim in this answer is likely to be probed. If you say you have followed the company's work for years, expect "What did you think of the announcement last month?" An answer you cannot back up in follow-up questions falls apart, and it takes your credibility on other answers with it.

The three-part structure for a why do you want to work here answer

You need three beats, in this order.

Part one: one specific reason

Pick a single reason tied to this organisation or this role — not to the sector, not to the industry, not to "companies like yours". One reason. If you list four, the interviewer remembers none.

Part two: the evidence behind it

Say where the reason comes from, so it does not sound like a guess. One sentence is enough: what you read, what you noticed, what you heard from someone who works there, what you used as a customer.

Part three: the link to you

Connect the reason to what you want to do next in your career. This is the beat most candidates skip, and it is the one that turns a compliment into an argument for hiring you.

Keep the whole answer to roughly 30 to 60 seconds. A concise interview response is easier to follow, easier for the interviewer to build questions on, and easier for you to remember under pressure.

Here is the structure filled in for a customer support role:

"I applied because your support team publishes its response-time targets and its escalation policy publicly, and I've worked in a support desk where we had to build that from scratch. Reading how you've structured tiers and handoffs, I could see the problem I like solving — making a queue predictable for both customers and the people working it. That's the part of support I want to keep getting better at, and it's why I'm applying here rather than to a general support role elsewhere."

Reason: the published targets and escalation policy. Evidence: you have done this work before and read their material. Link: predictable queues are the problem you want to keep working on.

Do the 20-minute research that makes the answer specific

You do not need to become an expert on the company. You need one concrete detail you can name. Twenty focused minutes is usually enough.

Read the job description twice. Highlight the two or three responsibilities that appear first or repeat. Those are the ones the hiring manager cares about most.
Look at the organisation's own materials. What does it say it does? Who does it say it serves? What has it said recently — a launch, a change, a priority it has stated?
Find one concrete detail you can name. A product, a service, a stated priority, a way of working. Concrete beats impressive.
Check how the role fits into the team or wider organisation. Your reason should be about the job, not just the brand.
Write your findings as three short notes, not an essay. You are preparing to speak, not to read.

If you are also working on your opening answer, the same research feeds it; the approach in Portfolio Interview Questions: Walk Through Your Work pairs well with this one.

Adapting the answer when your reason is practical

Not every honest reason is a mission statement, and it does not have to be.

Career changers

Connect the move to a skill or problem you want to work on, and say plainly why this role is the next step. "I've spent six years in operations and I want to work on the tooling side of it; this role sits between the two, which is exactly the move I'm making."

Returning to work or changing industries

Name what you bring and what you are deliberately choosing. Do not apologise for a gap. A gap is a fact; apologising for it is a choice, and it is a bad one in an interview.

When the reason is stability, location or schedule

If the honest reason includes stability, location or schedule, say it briefly and then add the part about the work itself. "The location matters to me — I'm settled here long term. What drew me to the role itself is the mix of account management and troubleshooting, which is where I do my best work." Practical reasons are normal. They only become a problem when they are the entire answer.

What not to do

Do not invent a passion for the mission. Do not criticise a current or former employer. Both are easy to spot and expensive to recover from.

If you applied on impulse

If you applied quickly and know little about the organisation yet, say so without dressing it up, then show what you did find: "I came across the role through a job board and applied the same day, so I'll be honest that I'm early in learning about the company. What made me apply was the line about owning the onboarding process end to end — that's the part of my last role I liked most." Then ask a genuine question about the area you have not researched.

Common traps and how to fix them

Trap: the answer could be pasted into an application to any company

Fix: name one detail only this organisation has — a specific product, a specific stated priority, or a specific way of working. If you could swap in another employer's name and the sentence still works, it is not specific enough yet.

Trap: talking only about what you want to get

Fix: add one sentence about what the role needs and how you match it. The answer should contain something for them, not just for you.

Trap: rambling past a minute

Fix: practise out loud and cut the third example, not the first. Your first reason is the strongest one; the third is usually padding. If you are still over time, tighten the evidence sentence rather than dropping the link to your direction.

Trap: over-rehearsing until it sounds recited

Fix: memorise the three beats, not the sentences. Know your reason, your evidence and your link, then let the wording vary each time. If it starts to sound flat, change the order of your notes and say it again without looking at them.

Trap: claiming knowledge you do not have

Fix: say what you found interesting and ask a genuine question instead. "I noticed you've moved to a subscription model recently — I'd be curious how that's changed the support workload." Curiosity reads as engagement; bluffing reads as bluffing.

Practising out loud before the interview

Written fluency and spoken fluency are different skills. An answer that reads well on paper can collapse the first time you say it.

Say the answer aloud at least five times.
Record yourself once and listen for filler words, hedging and length.
Practise the likely follow-ups: "What do you know about us?", "Why this role rather than a similar one elsewhere?", "What would you change?"
Prepare two questions of your own so the conversation continues naturally.
If you want structured repetition between practice sessions, rehearse and review your answer aloud; the preparation itself is what moves the answer forward.

For more practice material and related question breakdowns, the Blog is a good place to work through one question at a time, and if something in your setup is not working the way you expect, Support is the place to ask.

A short worked example, start to finish

Here is a weak version, then the same candidate's improved version.

Weak version:

"I've always admired your company. You're a market leader with a great culture and lots of opportunities for growth, and I think I'd be a great fit for the team."

Why it fails: it could be sent to any employer. It names no product, no priority, no team. It says nothing about the job. It asks the interviewer to take "great culture" on trust, which they cannot evaluate, and it gives them no follow-up question worth asking.

Improved version:

"I applied because your onboarding team rebuilt the first-week experience around a single checklist, and I read the write-up about it. (reason) I ran a similar project at my last company — we cut the number of tools a new client had to learn from six to two — so I know how much of that work is deciding what to leave out. (evidence) I want to keep doing that kind of process work, and this role owns it end to end. (link to you)"

Annotated: the first sentence is the reason, the second is the evidence, the third is the link to your direction. Spoken aloud, it runs about 35 seconds. The detail that makes it un-copyable is the rebuilt first-week checklist — that belongs to this employer and no other.

A checklist you can reuse for any employer

Before you walk in, check that your answer contains:

One specific detail about the organisation or the role.
One sentence linking that detail to your own direction.
One sentence on what you would bring to the work.
Under 60 seconds spoken.
Nothing you would be uncomfortable being asked to explain in detail.
Two follow-up questions ready.

If any line fails the checklist, fix that line rather than rewriting the whole answer. Most weak answers need one concrete detail and one sentence about direction — not a new script.

Run the checklist against the role you are preparing for now, say the answer out loud once, and note where you hesitate. That hesitation is usually the line worth rewriting.

Frequently asked questions

How long should the answer to "Why do you want to work here?" be?

Aim for roughly 30 to 60 seconds. That is long enough for a reason, the evidence behind it and a link to your own direction, and short enough that the interviewer can follow it and build their next question on it. If you are running past a minute, you are usually repeating a point rather than adding one.

What if I genuinely don't know much about the company yet?

Say so plainly rather than dressing it up, then show what you did find. Name the one detail that made you apply — a responsibility in the job description, a product, a stated priority — and ask a genuine question about the area you have not researched. Twenty minutes of reading the job description and the organisation's own materials is usually enough to have one concrete detail ready.

Is it okay to say I need a job or that the location suits me?

Practical reasons are normal and you do not need to hide them. Say the practical part briefly, then add the part about the work itself. A practical reason only becomes a problem when it is the entire answer, because then the interviewer has nothing to evaluate about your fit for the role.

How is this different from "Why are you leaving your current job?"

"Why do you want to work here?" looks forward: it is about your reasons for choosing this employer and this role. "Why are you leaving?" looks backward: it is about your reasons for moving on. Keep them separate. Do not criticise a current or former employer in either answer, and do not let the forward-looking answer turn into a list of what was wrong with your last job.

Should I mention salary or benefits in this answer?

No. This question is about your reasons for choosing the role and the organisation. Compensation and benefits belong in a separate conversation, usually later in the process or when the employer raises them. Raising them here shifts the focus away from fit, which is what you are being assessed on.

What if the interviewer follows up and I don't know the answer?

Say that you do not know, then say what you do know or how you would find out. "I don't know how that team is structured — I'd want to understand that. What I did notice was that the role sits between two functions, which is the part that interests me." Guessing is riskier than admitting the gap, because a wrong detail undermines the accurate parts of your answer.

Rehearse and review your answer with AI Interview assistant