"Why Do You Want to Work Here?" Is a Fit Test, Not a Love Test

The interviewer doesn't want to hear that you love the company. They want proof you did the homework and won't quit in eight months. That's the whole question. The winning answer is researched specificity, not displayed enthusiasm, and you can pass it cleanly even when the real reason is that you need a paycheck.

Most people get this backwards. They think "Why do you want to work here?" is asking them to perform passion, so they reach for adjectives: innovative, mission-driven, exciting. But the executives who actually run these interviews tell a different story. When asked to name the most common interview mistake, 47% of senior executives said "little or no knowledge of the company," far ahead of "limited enthusiasm" at just 9%. You're not being graded on how much you gush. You're being graded on whether you know what you're walking into.

What is the interviewer actually screening for?

Two things, neither of which is love. They want to know you'll be effective here specifically, and that you won't bolt the moment something better comes along. The question is a flight-risk filter dressed up as a softball.

That filter exists for a measurable reason. When researchers pooled 172 studies and 836 effect sizes, person-organization fit correlated with intent to quit at −.35 and person-job fit at −.46. Translated: the worse the fit, the faster people want out. A separate, independent meta-analysis of 21 studies found person-organization fit tied to intent to turnover at −.18 and to organizational commitment at .28, so the finding isn't a one-off. And a 2026 study confirmed it again, with person-organization fit predicting lower turnover intention directly (b = −0.26, p < 0.001).

A bad hire who leaves early is expensive. The interviewer is using your answer to predict whether you're that hire. When your reasons are specific to this role, you read as someone who chose them on purpose. When they're generic, you read as someone who'll choose the next thing just as easily.

Why does "I love your mission" fail so badly?

Because everyone says it, it's unfalsifiable, and it signals nothing about fit. Mission-worship is the verbal equivalent of a blank stare. It tells the interviewer you found the About page and nothing else.

It also collides with what the interviewer already knows about the market. Right now, 48% of job seekers say they frequently apply to many roles quickly instead of focusing, and 25% admit they apply "to any job that seems even remotely possible". The person across the table assumes, correctly, that most applicants have no specific connection to the role. So "I'm passionate about what you do" doesn't reassure them. It confirms their suspicion that you're spraying and praying. This is the same dynamic that makes the application-volume trap quietly sabotage candidates: volume reads as desperation, and desperation reads as flight risk.

Enthusiasm without evidence is the tell. The fix is to replace the feeling with a fact only someone who researched the company would know.

What does a researched answer actually look like?

It names something specific about the role, the team, or the company's situation, and connects it to something specific about you. The structure is: a concrete observation, then why that observation maps to your skills or trajectory. No adjectives doing the heavy lifting.

Weak (flattery, generic, unfalsifiable):

"I've always admired this company. You're a leader in the space, the mission really resonates with me, and I'd love to be part of such an innovative, fast-growing team."

Strong (specific observation, specific fit, no gush):

"You just opened a second support tier for enterprise accounts, and the job description leans hard on reducing escalations. I spent the last two years cutting escalation rates by building self-serve docs, so this is the exact problem I'd want to own next. The fact that it's still being figured out is the appeal."

The second version never says "love" or "passion." It doesn't need to. It proves fit by showing you understood the company's actual situation and matched it to your actual experience. That's what reads as genuine interest, because faking it would require doing the research, and if you did the research, the interest is real enough.

Answer ingredient	Generic version (fails)	Researched version (passes)
What you reference	The mission statement	A recent product, hire, or stated priority
Why you want it	"It's exciting / inspiring"	A named problem you've solved before
What it signals	You read the homepage	You understand the role's actual stakes
Maps to fit data	Triggers the flight-risk filter	Reads as P-O fit (−.35 quit intent)
Effort visible	Five minutes	A few hours of real work

Can you answer honestly when the real reason is "I need a job"?

Yes, and this is the part that actually matters, because for most people right now the honest reason is income, not calling. You don't have to manufacture a love story. You have to find the true, specific reasons this role beats the other roles you could take.

Here's the thing the spray-and-pray data also reveals. Among job seekers applying broadly, 51% changed their approach because they aren't hearing back, and 76% said they'd tailor their applications and be more selective if employers gave feedback. The under-investment isn't incapacity. People who "just need a job" are perfectly capable of a specific, honest answer. They've just been under-investing because the market gave them no reason to. The interview is exactly the moment to invest, because here it pays.

So do the work for this one role. Why this company over the others hiring for the same title? Maybe the team is small enough that you'd own a whole function. Maybe they use a stack you want to go deeper on. Maybe the commute, the schedule, or the growth trajectory genuinely fits your life better. All of those are true, specific, and defensible. None of them require pretending the company is your destiny. "This role lets me do more of the work I'm good at, on problems I find interesting, at a place that's growing the function I want to grow in" is both honest and exactly what the fit filter is looking for.

This is also why passion follows mastery rather than leading it: you don't need to walk in already in love. You need a real reason to think you'll get good here, and getting good is where the passion comes from.

How do you research fast enough to sound specific?

You don't need hours per company if you know where to look. Three sources, fifteen minutes, and you'll out-prepare 90% of the room, because the bar is "knows anything specific" and most candidates clear nothing.

Pull these before the interview:

• The job description, read closely. Which responsibility is listed first? What problem does the role exist to solve? The posting tells you what they're worried about, though remember the job description is partly fiction and the real priority is sometimes buried in the third bullet, not the first.
• One recent, dated fact. A funding round, a product launch, a new exec hire, an earnings note. Something that proves you looked past the homepage.
• One person's-eye-view detail. Glassdoor, the team's LinkedIn posts, an engineering blog. Something about how the work actually happens, not how marketing describes it.

Stitch one item from each into two sentences and you have an answer no generic applicant can match. The interviewer who heard "I admire your mission" forty times this month will remember the one person who mentioned the escalation tier.

What's the part nobody mentions about this question?

Researched specificity has a cost, and the advice to "just do the homework" leaves out who can't afford it. If you're sending forty applications a week because that's what a thin pipeline requires, you cannot deep-research forty companies. That's real, and pretending otherwise is the dishonesty Praxy refuses.

So tier it. Spend the research time on the interviews you actually have, not the applications you're firing off. The fit-filter question only gets asked once you've landed the conversation, so the specificity tax is owed at the interview stage, not the application stage. A handful of scheduled interviews is a manageable research load even for someone job-searching at volume.

The second honest caveat: sometimes the true answer is "this job pays better and I have rent due," and there's no specific fit to find because there genuinely isn't one. When that happens, don't fabricate one. Find the smallest true thing, the stack, the team size, the room to grow, and lead with that. A modest, specific, true reason beats a grand, generic, false one every time, because the interviewer is screening for honesty-of-fit, and a thin-but-real answer still clears that bar. A lavish fake one fails it the moment they ask a follow-up.

And know that this question rarely decides the interview alone. Likeability often outweighs raw competence in interviews, and how you frame why you're leaving your current role can move the needle as much as this one. "Why do you want to work here?" is a screen you need to pass, not a stage you need to win.

What to do now

1. Before each interview, pull three facts: the role's first listed responsibility, one recent dated company event, and one detail about how the work actually happens.
2. Write your two-sentence answer as observation-then-fit: name the specific thing you noticed, then the specific experience or goal it maps to. Delete every instance of "love," "passion," "excited," and "admire."
3. If the real reason is income, find the smallest true fit — team size, stack, schedule, growth — and lead with that instead of faking a calling.
4. Tier your research by stage: deep-prep only the interviews you've actually landed, not the applications you're sending.
5. Read your answer aloud and ask: could a candidate who never researched this company say the same sentence? If yes, it's still generic. Make it un-sayable by anyone who didn't do the work.

Want to pressure-test your "why do you want to work here?" answer for a real company before the interview — and find the true, specific reason even when the honest answer is "I need the job"? That's exactly what I do. Message me on WhatsApp, tell me the company and the role, and we'll build an answer that's specific, honest, and impossible to fake.