Why Do You Want to Work Here? You're Framing It Wrong

You have your walkthrough ready. Examples queued for conflict, failure, team dynamics. You have a crisp answer about your biggest weakness that is technically true and completely safe. Then the interviewer leans back and asks, "So, why do you want to work here?"

Small pause. You haven't really thought about it. Not specifically. Not about this company.

This is the question most candidates answer last and practice least. Hiring managers weight it surprisingly high. Not because it is technically difficult, but because almost everyone answers it the same way, and that way is wrong.

Treat it as an invitation to share your feelings about the company and you have already lost. Something else is being tested here.

This Question Is a Retention Test

The common assumption is that "why do you want to work here?" is a warmup question. Something to ease into the conversation before the real probing begins.

It is not.

Hiring managers use it to evaluate flight risk. The company is about to spend forty to eighty thousand dollars finding, onboarding, and waiting for you to become productive. A misfit hire who leaves in six months costs most of that and restarts the process. So before any of that clock starts, they want one thing: evidence that you chose them on purpose.

Research on person-organization fit, going back to Amy Kristof-Brown's 2000 study in Personnel Psychology, shows that perceived alignment between a candidate's values and an organization's values is one of the strongest predictors of retention and job satisfaction. Interviewers are not formally running a P-O fit assessment. But they are doing exactly that, informally, in real time, while you think you are just making small talk.

Three things happen simultaneously when you answer this question:

They check whether you researched this company specifically, or whether it is one of fifty tabs you had open that week.
They evaluate whether your motivations are intrinsic (the problem space is interesting, the mission connects to something real) or extrinsic (salary, title, commute). Intrinsic motivators predict staying. Extrinsic motivators predict leaving the moment a better offer arrives.
They look for a forward signal. Given your background, will you contribute to a real problem this organization actually has?

Answer "I've always admired your culture and I think this would be a great fit for my goals" and you have failed all three tests at once. It reads as: I researched nothing, I want things from you, and I have no idea what I'd actually do here.

Interview questions: what they ask vs. what they really want to know

Every question has a subtext. This one just happens to be the entire exam.

Three Moves, Two Minutes Max

Strong answers are not long. Two to three minutes, maximum. But they reliably cover three distinct territory markers.

First: a specific company hook. Not "I've followed your company for years." That could mean you signed up for their newsletter once and forgot about it. A specific hook is a recent product launch, a post from their engineering blog, a design decision in a press release, something from the job description itself that reveals a real problem they are solving. This proves you made a deliberate choice to be in this room. You are not here because a recruiter cold-messaged you on LinkedIn and you said yes to everything.

Second: a skill bridge. Connect what you know about their problem to something you have actually done. Not "I have experience in distributed systems." That is a resume line. Something like: "The consistency tradeoff you described in your engineering post about the queue redesign is exactly the class of problem I spent most of the last year on." That is a bridge. It tells the interviewer your existing knowledge maps directly to a challenge they are already thinking about.

Third: a forward contribution signal. One sentence about what you expect to deliver, not what you expect to receive. This is the part candidates skip most often. It shifts the frame from "what I want from you" to "what I'll do for you," which is the only frame that actually scores points.

None of this requires forty hours of preparation. Ninety focused minutes before the interview is enough. Seriously. Set a timer.

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

Say you are interviewing for a backend engineering role at a developer tooling company.

Bad answer:

"I've always been passionate about developer tools, and I've heard great things about your team. I think this role would be a great fit for my career goals."

Every word of that applies to every developer tooling company in existence. It tells the interviewer nothing about you, nothing about them, and nothing about what happens if they hire you. You could have written it with your eyes closed in fifteen seconds, and they know that.

Good answer:

"I read your post from last quarter on namespace conflict resolution in the SDK. The approach you took with lazy resolution rather than compile-time validation is something I've thought about because I ran into a similar problem with our plugin system at my last job. We ended up doing something messier, and it cost us three months of debugging. I'm interested in working somewhere that thinks carefully about that class of problem. I think I can contribute quickly because I have a lot of scar tissue from the wrong approaches."

That answer shows specific research (the blog post). It bridges to a real skill (API design, plugin systems). It signals forward contribution ("contribute quickly"). And it does all of this without once mentioning salary, career trajectory, or brand prestige.

Notice that this structure does not map onto STAR. STAR is designed for past-behavior questions: "Tell me about a time you disagreed with your manager." This question is forward-facing. Your structure here is simpler: company signal, skill bridge, contribution intent. That is the full frame.

If you want to test how this sounds out loud before the real thing, SpaceComplexity runs voice-based mock interviews where you can hear how an answer like this lands with follow-up questions in the mix.

The Mistakes That Kill Good Candidates

Most candidates lose points on this question in one of a handful of predictable ways.

Leading with what you'll gain. "This role offers a fantastic opportunity to grow in distributed systems" is about you. "I can contribute to your consistency layer because I've built one before" is about them. Hiring managers are not running a career development service. They have problems to solve and headcount to justify. Show up as a solution, not a beneficiary.

The generic warmup. "I've always admired Google's engineering culture" works equally well as "I've always admired Meta's engineering culture." If you can swap the company name and the sentence survives unchanged, it is not specific enough. Record yourself answering for three different companies. If the answers sound interchangeable, start over.

Faking enthusiasm you don't have. Experienced interviewers feel it. You do not need to love the company. You do need a real reason for being in the room. If your honest motivation is a thirty-percent pay bump, that is not your answer. But there is almost always something true underneath: the problem space is interesting, the scale is something you have not worked at, the team has people whose work you respect. Start from what is actually true. The interviewer has done this hundreds of times and can tell the difference between genuine curiosity and a performance.

The technical interview vs the actual job - Godzilla and Kong fighting vs tiny stuffed animal dinosaurs

What you think this answer requires vs what actually scores points.

Overdoing it. You read everything, you have strong opinions, you want to demonstrate all of it. Five minutes later the interviewer is nodding politely and waiting for the next question. Two to three minutes is the target. The hook, the bridge, one sentence of intent. Cut anything that is not pulling weight.

Candidates who struggle most are thinking about what sounds impressive rather than what is true. The note-taker is looking for quotable specifics, not general enthusiasm. A useful reference: what interviewers actually write about you.

Where to Actually Look

Ninety minutes of research is enough to answer this question well. Here is where to spend them.

The job description. The most underused resource available. The bullets under "what you'll work on" describe real problems the team needs someone to solve. Reference one of them directly. It signals that you read the actual document, not just the title.

The engineering blog. If the company has one, this is the richest source of specific technical detail. Real decisions, real tradeoffs, written by real engineers. Reference one post and you immediately become memorable. Most candidates never find this page.

Recent news. A product launch, an acquisition, a major partnership, a public postmortem. Companies care deeply about recent milestones. Knowing about them signals you are paying attention to where the company is going, not just where it has been.

The interviewer's public profile. This is the one most candidates skip. If the person interviewing you gave a conference talk, wrote a blog post, or contributed to an open-source project, reading it before the interview matters. Referencing it specifically is not flattery. It shows you treated this conversation as worth your time, which is exactly what they are trying to gauge.

You don't need Glassdoor reviews or insider knowledge. Specificity about publicly available information is already more than most candidates bring. For a broader look at how clarifying and targeted questions signal preparation across interview contexts, the principle transfers directly here.

The Short Version

The question is a retention test, not an icebreaker. Interviewers are evaluating flight risk, motivation type, and forward contribution signal simultaneously.
Strong answers cover three things: a specific company hook, a skill bridge, and one sentence of contribution intent. That structure is complete.
STAR is for backward-looking behavioral questions. This question is forward-facing. The frame is company signal, skill bridge, contribution intent.
Fatal mistakes: generic praise that survives a company-name swap, leading with personal gain, faking enthusiasm, over-explaining.
Ninety minutes of research is enough. Job description, engineering blog, recent news, interviewer's public profile.
If you can swap the company name and the answer still works, it is not ready.