How to Answer "Why Do You Want to Work Here?"

Answer "Why do you want to work here?" in three parts: name one specific thing about the company you genuinely respect (a product, a mission, a recent decision), connect it to a skill or experience you actually have, and finish with what you would contribute in this role. Keep it under 90 seconds, make it about their needs, and never lead with salary, commute, or "I need a job."

This question is a preparation test disguised as small talk. The interviewer already knows you want a job. What they don't know is whether you want this job, and the answer tells them in about a minute.

Three things are being checked at once. First, did you do any homework, because a candidate who researched the company will also research the customer, the codebase, or the client file. Second, will you stay, because hiring managers who have watched a new hire quit at month four ask this question defensively. Third, do you understand what the role actually is, because plenty of applicants apply to a title without reading past it.

A vague answer fails all three checks simultaneously. That's why this question, simple as it sounds, ends more interviews than the technical rounds do.

The most common failure is an answer that is entirely true and entirely about the candidate. These openers sink interviews every day:

Notice the pattern: each of these describes what the company can do for you. The interviewer is silently asking the opposite question. You don't have to lie about wanting stability or a paycheck. You have to answer the question they actually asked, which is about fit, and save your own priorities for the negotiation stage where they belong.

A strong answer has three moving parts, in this order: them, you, the match.

Part 1: one specific thing about the company. Not "your great culture." A named product, a market position, a recent launch, a mission you can state in their words. Specificity is the whole game here, because it's the only part of the answer a competitor's candidate can't copy.

Part 2: the skill or experience you bring that maps to it. One or two sentences from your real history. This is where your resume and your answer should tell the same story, in the same language.

Part 3: what you'd do in this role. Close by pointing forward. "That's exactly the kind of problem I want to spend the next few years on" lands better than trailing off after a compliment.

A working template: "I've followed [specific thing about the company], and it matters to me because [genuine reason]. In my current role I've [relevant experience], and this position would let me apply that directly to [specific challenge from the job posting]." Fill it with real details and it stops sounding like a template.

Twenty to thirty minutes of targeted research produces a better answer than an hour of aimless browsing. Work through these sources in order:

From all of that, extract exactly two things: one company-level fact for part 1 of your answer, and one role-level challenge for part 3. More than that and the answer bloats. Interviewers reward precision, not volume.

Here's the formula applied by a candidate interviewing for a program coordinator role at a healthcare nonprofit:

"What drew me to this posting is your focus on rural care access. I grew up in a town where the nearest specialist was two hours away, so the problem you're solving isn't abstract to me. In my current role I coordinate outreach programs across twelve county sites, and I've built the scheduling and volunteer systems that keep them running. This role would let me bring that operational experience to a mission I'd be proud to explain at a dinner table, and the expansion mentioned in the posting is exactly the kind of scaling work I do best."

Why it works: the personal connection is specific and verifiable, the experience maps directly to the job's requirements, and it closes on the company's stated challenge rather than the candidate's wish list. It runs about 40 seconds out loud, which is the right length.

For technical roles, genuine enthusiasm for the product or the stack is a legitimate and powerful answer, as long as it ends in contribution. A backend engineer interviewing at a payments company:

"Two things pulled me in. First, I've integrated your API on a previous project, and it was the cleanest payments documentation I've worked with, which tells me a lot about how the engineering team operates. Second, the posting mentions migrating core services to event-driven architecture, and that's the exact work I led at my current company, where I moved our order pipeline off a monolith over eighteen months. I want to do that kind of migration again, at your scale, on a product I already know from the outside."

The pattern is identical: specific admiration, matching experience, forward-looking close. Notice the candidate quotes the job posting's own priority ("event-driven architecture") back at the interviewer. That single move signals more preparation than ten minutes of company-history recitation.

Here's the part most interview guides miss: if you tailored your resume properly, the research for this question is already done.

When you duplicate your base resume for a job in Roleframe, the fit report reads the posting the way a recruiter does. It identifies the role archetype and seniority, maps every requirement against your actual experience, and shows which keywords the posting asks for that your resume covers or misses. That analysis is a ranked list of what this employer cares about most, which is exactly what "why do you want to work here" is probing for.

Use it directly. The top requirements in your fit report are part 3 of your answer, the challenge you speak to. The experience the report matched against those requirements is part 2, your evidence. And because your resume was edited around the same analysis, your interview answer and your resume tell one consistent story. Interviewers notice when the person in the room matches the document that got them there, and they notice even harder when it doesn't.

If you're still sending one generic resume everywhere, that consistency gap is worth fixing before your next interview. The case for keeping a base resume plus tailored versions per job is the same case for a tailored interview answer: employers respond to specificity.

An answer that reads well on paper can still collapse when spoken. The fix is rehearsal with feedback, not rehearsal alone.

Say it out loud three times, ideally recorded. You're listening for two failure modes: running past 90 seconds, and sounding memorized. If a sentence keeps tripping you, it's written language, not spoken language. Simplify it.

If you want a sparring partner, Remi, Roleframe's career copilot, runs interview practice built from your own resume and, on a tailored version, the job posting you attached. It asks one question at a time, you answer, and it scores each answer and flags what was thin, whether that's a missing specific, a claim your resume doesn't back up, or an answer that never got to the contribution part. It's practice against your own material, not a prediction of how a real interviewer will judge you, but it catches the gaps a mirror can't.

One final check before the interview: can you defend every sentence of your answer with a real example from your history? If yes, you're ready. If any line is aspirational padding, cut it now, because the follow-up question will find it.