"Why do you want this job?" is the question that exposes the most about a candidate in the fewest seconds. It is asked in almost every interview, it sounds simple, and most candidates answer it badly because they treat it as a question about enthusiasm. It's not. It's a question about specificity.

A strong answer reveals you understand the role, you've thought about your career, and you can distinguish this company from the other six you're interviewing at. A weak answer reveals none of those things — and weak answers are the norm.

Why the question is actually being asked

The question maps to three checks the interviewer is running:

1. Did this person read the job description? A surprising number of candidates apply to roles they haven't really studied. The "why this job" answer is a fast way to detect that.
2. Does this role make sense for them? If your last three roles were B2C consumer and you're applying to enterprise infrastructure, the interviewer wants to know how you bridge that. A generic answer can't.
3. How likely are they to accept if we make an offer? Candidates who can articulate why this role specifically appeals to them have higher offer-acceptance rates. The interviewer cares because re-running the process is expensive.

Your answer needs to clear all three. None of them are about whether you're "passionate." They're about whether you've done the homework.

The three-part structure

The structure is short on purpose. The whole answer should land in 60-90 seconds. Past 2 minutes, you sound rehearsed. Under 45 seconds, you sound dismissive.

The first beat — what about the role — is the most important. It's where specificity lives. Naming a concrete element of the job description, the company's recent product, or the team's scope tells the interviewer you read past the title. It also gives them something to follow up on, which keeps the conversation flowing.

The second beat — why now — is where most candidates skip the work. Connecting the role to your career trajectory signals you have a trajectory at all. "I've been moving from X scope toward Y scope" is a sentence that puts you ahead of 80% of candidates who treat each job as standalone.

The third beat — why this company — is brief on purpose. It exists to confirm you didn't apply on autopilot. Don't try to flatter the company; don't recite their values. One specific reason this company is different from the others you're interviewing at, in one sentence.

A worked example

Suppose you're a senior engineer interviewing for a role on the platform team at a Series C developer-tools company. The bad answer:

"I'm really passionate about developer tools and I've heard great things about your culture. I think your product is solving an important problem, and I'd love to be part of a team that's making a real impact."

The good answer:

"What got me to apply was the JD specifically — you're building the platform team from scratch, and the first hire is going to set the technical direction for 3-5 years. I've owned a 0-to-1 internal developer platform before at [previous company], so I know what's load-bearing in that first six months.

In terms of where I am in my career, I've spent the last four years on feature teams that consume platforms. Moving to a team that builds platforms is the direction I've been pointing at, and this is one of the few roles I've seen where the platform is the product, not the support function.

On the company specifically — your customer base is developer-led teams, not enterprise procurement. That's a much narrower set of companies than people realize, and it's where I want to be."

Same candidate, same circumstances. The first answer is generic. The second answer makes the interviewer want to follow up.

What specificity sounds like

The compare table is a filter you can run your draft answer through. Anything in the "don't" column will be said by other candidates today. If your answer matches any of those phrases, the answer doesn't differentiate you.

The single highest-leverage phrase to delete is "I'm passionate about." It is the verbal equivalent of a stock photo. Every candidate uses it. It conveys no information. Replace it with the specific thing the passion is supposedly about — and you'll find that the specificity is what was actually convincing all along, with "passionate about" just being the wrapper.

How interviewers actually weigh the answer

The numbers above match what hiring managers report when surveyed about why-they-passed conversations. The "vague why this role answer" is consistently top-3 in the rejection reasons for candidates who looked strong on paper. It's also one of the easiest things to fix.

The 3x advancement multiplier for candidates who name a specific company-level detail is the most actionable finding. Companies want to know you've engaged with them as a specific entity, not as a generic destination. Reading the engineering blog, the most recent earnings call, a podcast appearance by the CEO — any one of these gives you the detail that makes the answer specific.

How to find specific details to mention

If you have a 45-minute interview prep window and need ammunition for the "why this role" answer:

1. Read the JD once carefully. Highlight three sentences that feel real — not generic. Use one in your answer.
2. Read one recent piece of company content. Engineering blog, founder essay, podcast appearance. Look for one concrete project or decision you can name.
3. Check the company's most recent funding announcement or earnings note. Companies always say what they want to build with the new money. Use that.
4. Look up your interviewer on LinkedIn. If they mention something specific in their profile that overlaps with your background, weave it into the answer.

Ten minutes of this work produces two or three specific details. Pick one. Use it in the first 25 seconds of your answer.

When the question is buried in another question

The question often comes in disguise: "What attracted you to this role?", "What made you apply?", "What's exciting to you about this opportunity?". Same question. Same structure works.

The disguised version that catches people off guard is "tell me what you know about us." This is the "why this company" portion asked first. Don't recite the Wikipedia entry. Instead: one sentence on what they do, one sentence on a recent specific move you noticed, one sentence on why that interests you. See interview-research-on-the-company for the broader research approach.

For the related question "tell me about yourself," see tell-me-about-yourself-90-seconds — the two questions bookend each other and the structures should feel consistent.

What this isn't

A few clarifications:

• It's not a flattery question. Praising the company is not the goal — being specific is. A candidate who says "I want to work here because of [specific reason]" lands better than one who says "I think this company is amazing."
• It's not a test of how excited you are. Enthusiasm without specificity reads as desperate, not engaged.
• It's not the same answer for every interviewer. Adjust the level of detail to your audience. A founder cares about market and vision. A line manager cares about scope and team. Pick the version that fits.

The short version: specificity wins. Three sentences each on the role, your trajectory, and the company-specific detail you noticed. Ten minutes of prep produces a 60-90 second answer that puts you ahead of most candidates who treat the question as filler.