How to Answer "Why Do You Want This Job?" in a Job Interview (With Examples)

On paper, why do you want this job looks like small talk before the real interview begins. In practice, it's one of the more diagnostic questions an interviewer asks, and it's rarely as casual as it sounds.

The first thing interviewers are checking is whether you understand what the job actually involves. A candidate who answers with something that could apply to any role at any company — 'I'm looking for a new challenge' or 'I want to grow my career' — hasn't demonstrated that they read the job description closely enough to want this one specifically. That's a quiet red flag, since it suggests you might be applying broadly rather than deliberately.

The second thing they're checking is retention risk. Recruiting, onboarding, and training a new hire takes real time and money, and hiring managers know that candidates who take a job mainly because it was available — rather than because it fits their goals — tend to leave sooner. An answer that shows genuine alignment between your career direction and this specific role signals you're likely to stay past the first rough patch.

The third thing interviewers are listening for is whether your interest is about the role itself or about what the role gets you. There's a real difference between 'I want this job because it pays more than my current one' and 'I want this job because the account management responsibilities let me do the client strategy work I've been moving toward for two years.' Both might be true. Only one of them makes a compelling case to the person deciding whether to hire you.

None of this means you need a dramatic origin story about why this particular company changed your life. Most hiring managers have heard enough of those to be skeptical of them. What they're actually looking for is evidence that you've thought specifically about this role, this team, or this problem — and that your interest holds up under a natural follow-up question. Knowing what's actually being evaluated is the first step toward giving an answer that does more than fill silence.

These two questions get confused constantly, and answering one as if it were the other is a common reason candidates underperform on both.

What motivates you is about your internal drivers — the kind of work, environment, or recognition that generally keeps you engaged, regardless of employer. It's a question about your working style, and a good answer can be somewhat portable across similar roles.

Why do you want this job is narrower and more specific. It's asking why this particular position, at this particular company, right now. A generic answer about loving fast-paced environments or wanting to make an impact might technically be true, but it doesn't explain why you applied to this job rather than the dozen similar ones posted the same week.

The two questions do connect. Your underlying motivations should show up as part of your answer to why you want this job — but they need to be tied to something concrete about this role. Compare:

**Answering as if it were 'what motivates you':** 'I'm motivated by solving complex problems and working with smart people.'

**Answering 'why do you want this job':** 'This role's core challenge — rebuilding a support process across three time zones — is exactly the kind of complex, cross-functional problem I've been drawn to in my last two roles, and it's rare to find a team this size still building that infrastructure from scratch.'

The second version uses the same underlying motivation but grounds it in a specific detail from the job posting or the conversation. That grounding is what interviewers are listening for. If you're also preparing for the broader motivation question, it's worth reading up on how to answer what motivates you separately, since the two answers should reinforce each other without becoming interchangeable.

Most weak answers to why do you want this job share the same structural problem: they describe the candidate's needs instead of the fit between the candidate and the role.

**Generic:** 'This job seems like a great opportunity, and I've always been impressed by your company's reputation in the industry.'

**Specific:** 'The job description mentions rebuilding the onboarding funnel from the ground up. I did exactly that at my last company — cut time-to-first-value from nine days to two — and this is one of the few postings I've seen recently where that specific experience is the actual priority, not a secondary skill.'

The generic version could be copy-pasted into a cover letter for almost any employer. The specific version could only be said by someone who read the posting closely and has a real reason to want this exact problem to solve.

This is where how to answer why do you want this job stops being about finding the right words and starts being about doing the groundwork before the interview. Three things separate a specific answer from a generic one:

**It references something exact from the role or company.** Not 'your mission,' but a specific product decision, team structure, technical challenge, or market position mentioned in the posting or during the interview itself.

**It connects to your actual trajectory.** Explain how this role fits into where your career has been heading, not just where you'd like to end up eventually in the abstract.

**It's falsifiable.** A good answer should be specific enough that if someone checked it against your resume, it would hold up. Vague enthusiasm can't be checked against anything, which is exactly why it doesn't build trust.

You can't give a specific answer to why do you want this job without doing specific research first. Trying to improvise this answer from general enthusiasm is the most common reason candidates fall back on vague language.

**Read the job description like a brief, not a formality.** Identify the two or three responsibilities listed first or repeated most — these usually indicate what the hiring manager cares about most. Your answer should connect to at least one of them directly.

**Look at what the company has shipped, published, or announced recently.** A product launch, a leadership change, an expansion into a new market, or a public statement about company direction gives you something concrete to reference that most candidates won't mention.

**Check how the role fits into the team's structure**, if that information is available through the posting, the company's site, or LinkedIn. Understanding whether this is a newly created role, a replacement, or part of a team that's scaling changes what 'wanting this job' should sound like.

**Notice what's unusual about this specific opportunity.** Is there a technical challenge, a stage-of-company factor, or a responsibility that isn't common in similar roles elsewhere? That's often the most convincing material for your answer, because it can't be reused for a different application.

**Revisit your own resume with this role in mind.** Before the interview, identify which one or two experiences most directly connect to what this job actually needs. This becomes the evidence that turns your interest from a claim into a case.

Ten minutes of this kind of research produces more usable material for this question than an hour spent trying to think of the right adjectives to describe your enthusiasm.

A reliable structure for how to answer why do you want this job has three parts, deliverable in about 45 to 75 seconds.

**Step 1: Name something specific about the role or company (1-2 sentences)**

Reference a detail from the job description, a company decision, or a challenge discussed earlier in the interview.

'What stood out to me in the posting is that this role owns the full customer lifecycle, from onboarding through renewal, rather than splitting that across two teams.'

**Step 2: Connect it to your background (2-3 sentences)**

Explain why that specific detail matters to you, using a concrete experience.

'I've worked in structures where onboarding and renewal were handled by separate teams, and I saw firsthand how that split created blind spots — customers who churned because no one owned the full relationship. I've been looking for a role where I can own that end-to-end, and build the kind of continuity that structure makes possible.'

**Step 3: Close with why now, specifically (1 sentence)**

Tie the timing or trajectory together without overselling.

'This feels like the right next step for me, and it's a problem I'm genuinely interested in solving.'

Total: roughly 100 to 150 words, or about a minute of natural speech. This structure works because each part does distinct work — the first shows research, the second shows evidence, and the third shows genuine interest without sliding into desperation. Skipping the first step is the most common shortcut, and it's the one that makes an otherwise decent answer sound like it could apply to any job at any company.

**Talking about what the job gives you, not what you bring.** 'This role would be a great next step for my career' focuses entirely on your benefit. Reframe it around what you'd contribute to this specific problem, not just what you'd get from the position.

**Praising the company in generic terms.** 'I've always admired your brand' or 'You're a leader in the industry' is filler that every candidate can say and most interviewers have heard hundreds of times. If you're going to compliment the company, be specific enough that it couldn't apply to a competitor.

**Bringing up compensation, benefits, or logistics.** Salary, remote flexibility, and better hours might be entirely legitimate reasons you applied. They are not, however, a persuasive answer to why do you want this job, because they say nothing about fit or value to the employer. Save those conversations for the appropriate stage of the process.

**Criticizing your current or former employer.** 'I want this job because my current company is disorganized and my manager doesn't listen to me' shifts the focus to a complaint rather than an interest. Even when true, this reads as a risk signal rather than a selling point.

**Reciting the job description back at the interviewer.** 'I want this job because it involves managing a team, developing strategy, and working cross-functionally' repeats information they already have without adding your perspective. The interviewer wrote the posting; they don't need it summarized back to them.

**Answering with no research behind it.** An answer built entirely on general enthusiasm — 'this just really excites me' — without a specific reason attached collapses the moment an interviewer asks a natural follow-up like 'what specifically excites you about it?'

Preparation for how to answer why do you want this job works best as spoken rehearsal, not silent thinking or written notes you plan to half-memorize.

**Step 1: Do the role-specific research** outlined earlier, and write down the one or two details from the job or company that you genuinely find most relevant to your own background.

**Step 2: Draft your answer using the three-part structure** — specific detail, personal connection, forward-looking close. Keep the written draft to about 100-150 words as a starting point.

**Step 3: Say it out loud, not just read it silently.** Reading an answer in your head almost always feels more polished than it sounds spoken aloud. Filler words, run-on sentences, and awkward transitions tend to surface only once you're actually talking.

**Step 4: Record yourself and listen back.** Does the opening line sound specific to this company, or could it apply to five other job postings? Does the personal connection sound like a real example or a vague claim?

**Step 5: Prepare for the natural follow-up.** Interviewers who hear a strong answer to why do you want this job often ask a follow-up question, like what specifically about the role stands out, or how you'd approach the first 90 days. Practice answering that follow-up too, not just the opening statement.

**Step 6: Adjust for each interview**, if you're applying to multiple companies at once. The structure can stay the same, but the specific details in step one need to change for every employer — reusing the same answer word-for-word across applications is usually what makes it sound rehearsed rather than genuine.

SayNow AI lets you rehearse this exact question in a realistic spoken interview simulation, complete with natural follow-up questions and feedback on pacing, specificity, and whether your answer actually sounds like it's about this job rather than any job. Running through it out loud a few times before the real interview is what turns a question that trips up most candidates into one you've already handled.