How to Answer 'Why Do You Want to Work Here?' Well

Why This Question Catches So Many Candidates Out

'Why do you want to work here?' sounds simple, which is exactly why it trips people up. Most candidates default to vague compliments — 'You're a market leader,' 'I love your culture,' 'It's a great opportunity for growth' — and interviewers hear these phrases dozens of times a day. They land as filler, not evidence.

What the interviewer is actually testing is threefold: whether you've done serious research, whether your motivations are genuinely aligned with what this role and organisation offer, and whether you can articulate a coherent reason that connects your past to their future. A strong answer signals that you chose them deliberately, not that you're applying everywhere and hoping something sticks.

The Three Ingredients of a Specific Answer

A genuinely specific answer weaves together three threads: something real about the organisation, something real about the role, and something real about you. Strip out any one of those threads and the answer collapses into generality.

Think of it as a triangle. The organisation thread might be a strategic direction, a product decision, a recent piece of work, or a stated value that you can tie to observable evidence. The role thread means naming actual responsibilities or challenges the job involves. The 'you' thread is the experience or conviction that makes this particular combination meaningful to you — not just desirable, but logical.

• Organisation thread: a specific initiative, product, mission statement, or business decision you can point to
• Role thread: a concrete responsibility, skill area, or challenge mentioned in the job description
• You thread: a past experience, skill, or value that connects directly to the above two

Research That Goes Beyond the Homepage

Surfacing specifics requires research that goes deeper than the 'About Us' page. That page tells you what the company wants you to think about them. You want evidence of what they actually do.

Use this checklist before drafting your answer.

• Read their last two or three press releases or news items — look for strategy shifts, product launches, or market expansions
• Check their LinkedIn company page for recent posts and the profiles of people in similar roles to understand day-to-day realities
• Search for interviews with senior leaders (podcasts, trade press, conference talks) to hear how they describe their challenges
• Review Glassdoor or similar sites not for gossip, but to understand how the company describes its own culture internally
• Re-read the job description line by line and note the verbs — 'lead', 'build', 'transform', 'scale' — these reveal what they actually need
• If you know anyone who works there, a ten-minute conversation is worth hours of website reading

Building Your Answer: A Practical Framework

You don't need STAR (Situation, Task, Action, Result) in its full form here, but the underlying logic — ground your claim in evidence, then show impact — is exactly right. Structure your answer in three moves: anchor, connect, forward.

Anchor: name something specific you've observed about the organisation. Connect: link it to an experience or conviction of your own. Forward: state what you want to contribute or learn as a result. Keep the whole answer to around 90 seconds when spoken aloud — roughly three to four sentences per move.

Example Answer: Before and After

Here is the kind of answer that sounds fine but scores poorly:

'I want to work here because you're a leading company in the sector and I think there are great opportunities to develop my career. I've always admired your culture and I believe my skills would be a good fit.'

Now here is the same candidate — a mid-level marketing manager applying to a B2B SaaS company — after applying the framework:

'I've been following your move into the mid-market segment closely — particularly the rebrand of your enterprise tier last autumn and the case studies you've published since. That shift from volume to value-led growth is exactly the challenge I spent two years working on at my current employer, where I led the repositioning of our product for larger accounts and reduced churn in that segment by around a third. I want to bring that specific experience to a team that's actively navigating the same transition, and I'm genuinely curious about how you're thinking about content as a retention tool at that tier, which your recent blog series suggests is a live question for you.'

Notice what the second answer does: it names a specific business decision (the mid-market move), references observable evidence (the rebrand, the case studies, the blog series), connects to a directly relevant past experience using a concrete result, and closes with a question that shows ongoing intellectual engagement. Nothing in it could be said to any other company.

Common Mistakes and How to Avoid Them

Even well-prepared candidates fall into a few predictable traps when answering this question under pressure.

• DON'T mention salary, location, or benefits — even if they're real reasons, they signal you're optimising for yourself, not for the fit
• DON'T lead with 'I've always wanted to work for a company like yours' — this is praise-seeking, not reasoning
• DON'T recite their mission statement back at them verbatim without analysis — it shows you read the website, not that you thought about it
• DO be honest if you're changing industries or roles — frame it as a deliberate decision with evidence, not an apology
• DO include one forward-facing element — what you hope to contribute, not just what you hope to receive
• DO practise saying the answer aloud before the interview; specificity that reads well can still sound stilted if you haven't rehearsed the rhythm

Practising Under Real Interview Conditions

Reading a good answer is not the same as delivering one. In a live or recorded interview, pressure compresses your memory and you default to the phrases you've rehearsed most — which, for most people, are the vague ones. The only reliable fix is deliberate practice on camera, under time pressure, until the specific version is more automatic than the generic one.

ScreenReady is designed precisely for this: you record a timed video answer, and the AI feedback flags exactly the kind of vague, generic phrasing this question punishes. Running your 'Why do you want to work here?' answer through a few recorded takes before the real thing is one of the highest-return uses of preparation time you can make.