"Why do you want to work here?" — how to answer

A complete answer touches all three, weighted toward the first two. Sixty to ninety seconds.

1. The role. What is in this job that you specifically want more of. Scope, problem type, stage of the work, the part of the function you would own.

2. The organisation. Something specific about them, connected to why it matters to you. Not their reputation — a situation, a programme, a market position, a technical problem, a stage of growth.

3. The timing. Why now, in your career. This is the shortest part and the one that makes the answer personal rather than generic.

Most candidates give level 2 only, in the form of compliments. Strong candidates lead with level 1, because that is the part the interviewer can actually verify against the job they wrote.

The employer's homepage is where every other candidate stopped. Spend twenty minutes past it.

Research checklist:

• [ ] Read the full job description again, including the parts you skimmed. What does it emphasise, and what is conspicuously absent?
• [ ] Look at how the role sits in the structure — who it reports to, what sits alongside it. That tells you what the job is for.
• [ ] Find two or three people currently in similar roles there on LinkedIn. Where did they come from? What does that say about what is valued?
• [ ] Look at what the organisation has announced in the last twelve months — a new facility, a new market, a restructure, a programme, a partnership
• [ ] If it is listed or government-linked, look at published strategy or annual reporting. The stated priorities are usually the real ones
• [ ] Look at their careers page as a whole. What are they hiring for right now, in volume? That reveals where they are investing
• [ ] Find one thing that is genuinely hard about their situation. Being able to name a challenge, without criticising, is the single strongest signal available in this answer
• [ ] If anyone in your network has worked there, ask what it is actually like

What you are looking for is one fact that changes your answer. Not five facts to recite. One thing you can connect to something you want.

Before building the answer, work out whether you have one. Ask these in order.

If you cannot get past question 2, the honest answer is that this is one of several applications. That is a normal position to be in. It does not mean you cannot answer well — it means your answer should be built on the role and the work rather than on manufactured enthusiasm for the organisation, which interviewers detect easily.

The role: Planning Manager at a logistics operator expanding into a second distribution hub.

"Two things, mainly.

The first is the scope. I run planning for a single site at the moment — three warehouses, but one network node. This role covers planning across two hubs with the second one being built, which is a different problem: you are designing the planning model before the demand pattern exists rather than optimising one that already does. I have wanted to work on that side of it for a while and there is no route to it where I am.

The second is that you are at the point in the expansion where the planning function either gets built properly or gets improvised and fixed later. From the outside it looks like you are trying to do the first one — the role exists before the hub opens, which is not the usual sequence. That is the part that interests me, and honestly it is also the part that looks hardest, because you will be planning against forecasts nobody can validate for the first six months.

On timing — I have been in my current role four years and I have done what I came to do there. I would rather move while the work is going well than wait until I have stopped learning."

Invented example. The employer, the role and the situation are not real.

What it does:

• Leads with the role, and defines the difference precisely: designing a model versus optimising one.
• Names a specific observation about the employer — the role existing before the hub opens — which no competitor's version would fit.
• Names the hard part without criticising. This is the line that separates a researched answer from a flattering one.
• Gives the timing in two sentences and does not make it about dissatisfaction.
• Says nothing about their reputation, their culture, or their values.

"Why this role?" Level 1 only, expanded. Go deeper into the work itself.

"What do you know about us?" A different question — a knowledge check, not a motivation one. Answer briefly and factually, then connect one fact to your interest rather than listing everything you found.

"Why are you leaving your current role?" The mirror question, and it has its own answer. Do not merge the two: this one is about moving toward something, that one about moving away.

Asked by a recruiter on a screening call. Shorter, thirty seconds, weighted toward the role rather than the organisation. The recruiter is checking you are not applying indiscriminately.

Asked again by the hiring manager later. Give the same substance. Add the detail you learned from the earlier conversation — that is genuinely impressive and almost nobody does it.

"I want to contribute to Vision 2030" is now a generic answer. It was distinctive several years ago and is not any more, because almost every candidate says it. If national or sector transformation is genuinely your reason, make it specific: which programme, which part of the change, and what you would actually work on. Otherwise leave it out.

Public and government-linked entities often have published strategy documents, and reading the actual priorities rather than the summary is unusually high-yield. Naming one stated objective and connecting it to the work of the role puts you ahead of most of the shortlist.

Family businesses and founder-led organisations respond differently to this question. What matters there is usually whether you understand the specific business rather than the sector, and whether you are likely to stay.

Avoid flattery of the leadership. It is common, it is easy, and it reads as a substitute for having researched the work.

What if the honest reason is money?

Money can be part of why you are moving; it is not an answer to "why here". Lead with the work and the fit. If compensation is the main driver, that will come out in the salary conversation where it belongs.

What if I applied to fifty companies?

Then build the answer on the role rather than the organisation, and make the role part genuinely strong. Do not manufacture attachment to an employer you selected from a list — that is the version interviewers see through.

What if I do not know much about them?

Then spend the twenty minutes. Arriving without having read past the homepage is the most avoidable failure in interviewing, and this question is where it becomes visible.

Can I mention someone who works there?

Yes, and it helps — "I spoke to [name] about how the function is set up" shows effort and gives you real material. Make sure it is accurate and that they would be comfortable being named.

Should I mention something negative I found?

Not as a criticism. Naming a challenge is different from naming a flaw. "The hardest part of this looks like X" is strong; "your reviews on Glassdoor are concerning" is not a conversation you want to have in an interview.

Do the research checklist before you write anything — the answer is made of what you find, and twenty minutes of reading produces more than an hour of drafting.

Then: why should we hire you, which is the other half of the same assessment, and the interview question hub for the rest.

If you have the material and cannot tell whether your answer sounds researched or rehearsed, that is what a mock interview is for — or work through it in the self-paced interview preparation course.