You answer "why do you want to work here" by translating the employer's stated problem into a specific, verified connection between that problem, your demonstrated work, and what you would do in the role. The question is not a personality test; it is a fit-inference task in which interviewers compare your stated motive against evidence and against what the job actually requires. Strong answers name the role's real work, cite something concrete you verified about the team or product, and connect it to a result you produced before. Weak answers describe what the job can do for you.
The inference problem behind the question
An interviewer asks this question to predict fit under uncertainty, because interviews are noisy predictors of performance. The underlying mechanism is attribution: the interviewer wants to know whether your stated reason is stable and role-relevant or situational and self-serving. Stable reasons, such as the problem domain, the work's scope, or a step in your skill trajectory, predict that you will stay engaged when the job gets hard. Situational reasons, such as location, salary, or needing any job, predict that you will leave when a nearby alternative appears.
Your answer is treated as a claim, not a fact. Interviewers weigh it against your resume, your prior choices, and their knowledge of the role. That is why vague enthusiasm fails even when it is sincere. A claim that a specific project type matches work you have repeatedly chosen is verifiable; a claim that you have always admired the company is not. The practical consequence: your answer should contain at least one detail the interviewer could check against your history.
There is also a comparison mechanism. Interviewers often hear several candidates describe similar motives, so distinctiveness comes from evidence rather than intensity. The same structure that makes a scientific claim credible, a specific observation plus a specific prior result, makes a motive credible. This is why the strongest answers often include a small, accurate detail about a process, a product limitation, or a team structure that most candidates would not know.
What the question measures, in context
Interviewers typically weight this question as one data point among many, not a decisive test. Structured interviews, in which every candidate receives the same questions and the same rating scales, tend to outperform unstructured conversation for predicting job performance; that finding has been replicated across employment settings. The practical implication is that interviewers who use a fixed rubric are comparing your motive statement against predefined criteria, such as role knowledge and career direction, rather than judging how much they like you.
The costs of a mismatch are asymmetric. Hiring is expensive relative to the interview, and early turnover is costly in recruiting and training time. Interviewers therefore over-weight signs of persistence and role realism, even if the underlying question was intended to measure motivation. A candidate who says they want the job because it matches a documented skill trajectory reduces the interviewer's perceived risk. A candidate who says the job is convenient increases it.
The question also interacts with the follow-up. Most interviewers who ask it will probe with "what about that specifically" or "tell me about a time you worked on something similar." An answer with no concrete anchor collapses on the first follow-up. That is the functional test: can you supply a second, independent detail when pressed? Plan for at least one probe.
Three competing signals and how interviewers read them
The table summarizes the common interpretations an interviewer draws from three answer types. It is a comparison of alternatives, not a script.
| Answer type | What the interviewer hears | Typical follow-up | Fit inference |
|---|---|---|---|
| Mission or values statement | Familiar with the organization, possibly superficial | "What part of our mission do you disagree with or find hard?" | Variable; high if specific, low if generic |
| Role and problem match | Understands the actual work | "Describe the work you did that maps to this" | Strong if evidence follows |
| Skill-growth narrative | Self-aware, directionally consistent | "What would you do if this role stopped offering that growth?" | Moderate to strong; watch for volatility |
| Convenience or compensation | Transactional motivation | "What would make you stay three years?" | Weak |
| Admiration without detail | Enthusiastic but unverified | "What specifically would you change here?" | Weak |
| Critiqued alternative | Analytical, evidence-based | "What did you learn from that tradeoff?" | Strong if respectful |
The critiqued-alternative category deserves explanation. A candidate who says they chose this kind of role because a previous project exposed a limitation in a different approach demonstrates judgment rather than enthusiasm. That signal is harder to fake and predicts problem-solving style. The constraint is tone: the critique must be aimed at approaches or products, not at people or former employers.
Why generic enthusiasm fails the mechanism test
The failure mode is a mechanism failure, not a politeness failure. A generic answer supplies a conclusion without a causal chain. The interviewer cannot infer from "I am passionate about technology" what you will do on a Tuesday morning, so the claim carries no predictive weight. Specificity works because it lets the interviewer run the same causal inference you did.
Three misconceptions are common here. First, candidates believe the answer must be flattering; in practice, informed honesty rates better, because interviewers discount flattery and reward role realism. Second, candidates believe one answer serves all employers; reusing an answer is detectable through the mismatch between your stated trait and the job's described work. Third, candidates believe passion is a substitute for competence evidence; it is not, and interviewers interpret unanchored passion as a risk marker rather than a strength. Professional caveat: some interviewers, particularly in sales-adjacent roles, do value visible enthusiasm, so calibrate intensity to the role while keeping the evidence anchor.
Red-flag patterns that sink otherwise successful interviews:
A motive that duplicates the job description without adding personal history. Resentment toward a current or former employer as the primary reason. A reason that would apply to any employer, such as "I want to grow." A compensation-first or schedule-first answer with no second reason. Visible enthusiasm paired with zero knowledge of the product or role. Vagueness that forces the interviewer to construct your motive for you.
Building the answer: a four-part structure with a one-week preparation plan
The practical mechanism is pre-writing three candidate answers, then selecting based on what you learn about the role. Each answer has four parts: the role's real problem, your verified anchor, the connection, and your first contribution. Keep the whole answer to 45 to 90 seconds spoken; beyond roughly two minutes, interviewers begin editing what they remember.
Concrete steps, in order:
Extract the three most repeated responsibilities from the job posting and any public team material. For each, write one sentence describing the problem the team is trying to solve, not the task. List two prior results of yours that map to that problem, with a number or artifact you can describe. Verify two facts about the product, the process, or the team's stated priorities using public sources. Draft a 60-second answer per role theme, then rehearse aloud twice and cut anything you cannot defend on a follow-up. Prepare one honest limitation sentence each, since interviewers rate self-awareness as a fit signal.
The timeline below shows the standard conversation in which the answer lands, and where preparation should attach.
| Stage | Typical duration | What is being assessed | Preparation to do |
|---|---|---|---|
| Recruiter screen | 15-30 minutes | Basic role clarity and logistics | One-sentence motive with role name |
| Hiring-manager interview | 30-60 minutes | Fit, direction, problem understanding | The full four-part answer plus two anchors |
| Peer or technical interview | 45-90 minutes | Credibility of your claims | A one-paragraph description of your mapped prior work |
| Second-round or panel | 60-120 minutes | Consistency across interviewers | Rework the answer once for this specific team |
| Reference or final conversation | 15-30 minutes | Verification and retention risk | One sentence on what would keep you in the role |
Across all stages, the recurring threshold is the same: at least one checkable detail and one map from prior work to the role's problem. If you cannot supply both, the answer is underbuilt.
Where this advice stops being valid
The mechanism assumes an interviewer who is genuinely comparing candidates on role fit. When the hiring process is primarily a credential filter, or when the interviewer has already decided based on internal referral, the question carries less weight. Cross-cultural differences also matter: in some hiring cultures, direct critique of past approaches reads as disloyalty, and the evidence-based answer should be softened accordingly.
Finally, no structure guarantees an outcome. The question is one data point in a noisy process, and interviewers differ in how they weight it. Read the answer as a method for reducing the risk of being misread, not as a lever you control. General educational information only.
If you need to prepare an answer to this question, start by writing one sentence that names the role's problem and one that names your evidence. That single sentence pair is the part interviewers remember.