A strong answer to "why do you want to work here" connects three specific things: the company's actual work, a proven capability of yours, and a plausible future contribution. It signals genuine research and realistic self-awareness rather than flattery. Interviewers use the question to predict whether you will stay, perform, and fit, so vague enthusiasm ranks below specific, evidence-backed interest.
The hiring signal behind the question
The question is a prediction instrument. Interviewers are estimating tenure, motivation, and fit under uncertainty, and they weight specific, verifiable statements more heavily than emotional ones. Research on structured interviews consistently finds that past behavior and concrete job-relevant detail predict performance better than general impressions (Schmidt and Hunter, 1998, Psychological Bulletin).
Mechanically, a specific answer works because it is costly to fake. Naming a real product decision, a published metric, or a team structure requires preparation, which itself signals motivation. It also gives the interviewer something to probe, and probes produce the behavioral evidence they actually score. Vague praise ("great culture") gives them nothing to verify and nothing to record.
The underlying psychology is signaling under information asymmetry. You know your motives; the interviewer does not. Specific claims are credible signals because low-motivation candidates rarely invest the effort to produce them.
What a top-decile answer contains
Strong answers share a repeatable structure rather than a script. The most reliable frame is three moves: a specific observation about the company, a matched capability of yours, and a forward-looking contribution. Each move takes one or two sentences, and the whole answer runs roughly 60 to 90 seconds.
The observation proves research and must be current and checkable. The capability maps your experience onto a named need, ideally with one quantified result. The contribution shows you understand the role's near-term priorities.
A named product, service, or market position, not generic praise One capability matched to a specific need, with a result attached A forward-looking contribution tied to the team's near-term goals A reason this role specifically, distinguished from the company generally A realistic tenure signal, such as growth you intend to pursue here
Red flags to avoid in your own draft: praising only perks or salary, claiming to be "passionate" with no evidence, reciting facts anyone could copy from the homepage, and describing a career plan that exits the company in two years.
Comparative answer structures
Different framings fit different roles, and each has a distinct risk profile. The table maps the common alternatives.
| Structure | Core move | Best for | Primary risk |
|---|---|---|---|
| Company-first | Lead with their market or mission, then your fit | Large, well-known employers | Sounds like research without self-interest |
| Role-first | Lead with the work, then why this team | Specialist and technical roles | Neglects the "why us" half |
| Mission-aligned | Link your values to their stated purpose | Nonprofits and public sector | Can read as generic idealism |
| Product-user | You use and understand the product | Consumer tech and services | Weak if you are not a real user |
| Growth-path | Tie your development to their trajectory | Early-career candidates | Risks sounding transactional |
| Referral-informed | Use insider context you verified | Networked applications | Fails if details are wrong |
The company-first and role-first structures dominate professional hiring because they balance both halves of the question. The others are supplements, not substitutes.
Edge cases and interviewer intent
The question shifts meaning by context, and misreading it costs you. A recruiter screen weights retention and salary alignment, while a hiring manager weights task fit and ramp speed. A panel interview may use it to test research depth and communication under mild pressure.
Seniority changes the expected answer. Early-career candidates are scored mainly on motivation and learnability, so mission and growth carry more weight. Senior candidates are scored on judgment, so the answer should show you understand the company's strategic problems and where you would attack them.
Some interviewers are testing whether you did basic diligence cheaper than reading the website. A counterintuitive detail helps here: the strongest answers often include a mild, informed reservation or a genuine question, which signals independent judgment. Blind enthusiasm reads as either naive or insincere to experienced interviewers.
Timeline: preparing the answer
Preparation is a sequence, and the timing matters more than the total hours. The table shows a workable course for a single interview.
| When | Action | Output |
|---|---|---|
| 7+ days out | Read the last two quarterly updates or annual report | Three candidate observations |
| 5 days out | Study the product or service firsthand | One concrete user or customer insight |
| 3 days out | Map your three strongest results to their needs | Capability-to-need matches |
| 2 days out | Read recent leadership statements and press | Current strategic priority |
| 1 day out | Draft and time the answer aloud | 60-90 second version |
| Morning of | Rehearse one honest reservation or question | Independent-judgment signal |
| In interview | Deliver, then invite a follow-up | Probed, verifiable detail |
Practical actions and thresholds
Concrete steps outperform intentions here. Use these thresholds to calibrate effort.
Draft two versions, 45 and 90 seconds, and choose by interviewer seniority. Cite at least two specific, checkable facts; three is the practical ceiling before it sounds recited. Attach one number to your matched capability, such as a percentage, time saved, or scale handled. Name the role specifically in at least one sentence to distinguish it from the company. Practice aloud until the answer lands between 60 and 90 seconds; over two minutes signals poor calibration. Prepare one informed question that follows from your answer, since interviewers often probe it.
If you cannot find two verifiable facts, you have not done enough research, and the answer will read as generic regardless of delivery.
Limitations and honest caveats
This is inference from interview and personnel-selection research, not a guarantee of outcomes. Interviewers vary widely in training and consistency, and unstructured interviews in particular have modest predictive validity. A perfect answer cannot offset a skills mismatch, and a mediocre one rarely sinks an otherwise strong candidate.
Cultural and industry norms also shift the expected tone, from restrained in some sectors to expressive in others, so calibrate delivery to the setting. Treat the answer as one signal among many, and let it do its job: prove you did the work and can connect it to theirs.