Why Do You Want to Work Here? 6 Answers That Prove Fit, Not Love

When an interviewer asks "why do you want to work here?", they aren't asking you to declare love for the company. They want proof you did the homework and won't quit in eight months. The winning answer is researched specificity, not displayed enthusiasm: one concrete thing you noticed about this company or role, tied to one concrete thing about you. You can pass it cleanly even when the real reason is that you need a paycheck.

The formula: "I noticed [one specific, recent thing about this team, product or role]. It lines up with [one specific thing you've done, or want to do next]. That's why this role, here, over the others I could take."

Slot	What goes in it	What doesn't
The observation	A launch, a hire, a priority in the job post, how the team works	The mission statement, "industry leader"
The connection	A result you've produced or a skill you're building	"I'm passionate," "I've always admired you"
The close	Why this role beats your other options	"I'd love to be part of the team"

Here's what most people get wrong. They hear the question as a request to perform passion, so they reach for adjectives: innovative, mission-driven, exciting. The managers who run these interviews tell a different story. When the staffing firm Accountemps asked more than 1,000 senior managers in 2011 for the most common interview mistake, 38% named "little or no knowledge of the company," while just 9% picked "limited enthusiasm". The survey is old, but the gap is wide: lack of knowledge was nearly double the next answer. You're not graded on how much you gush. You're graded on whether you know what you're walking into.

What is the interviewer actually screening for?

Two things, and neither is love: will you be effective here specifically, and will you stay long enough to be worth hiring? The question is a fit test and a flight-risk filter dressed up as a softball. The five-year question runs the same stay-or-bolt test from another angle.

Both halves have data behind them. Kristof-Brown and colleagues' 2005 meta-analysis of 172 studies with 836 effect sizes found that fit with the job correlated at −.46 with intent to quit, and fit with the organization at −.35. The same review found that perceived fit was strongly tied to an organization's intent to hire (.67 for job fit, .61 for organizational fit). Fit is what interviewers are hunting for, and it's what predicts who wants out. A 2026 study of 1,071 employees in Poland found the same direction again: person-organization fit predicted lower turnover intention (b = −0.26, p < 0.001).

The interviewer also knows how mobile people are. US Bureau of Labor Statistics data show median tenure with the current employer was 4.1 years in January 2026, and just 3.0 years for workers aged 25 to 34. And an early exit is expensive: Gallup estimates replacing an employee costs one-half to two times their annual salary. When your reasons are specific to this role, you read as someone who chose it on purpose. When they're generic, you read as someone who'll choose the next thing just as easily.

What are good example answers to "why do you want to work here?"

Good answers change with your situation, but every one follows the formula: an observation only a researcher would make, then a link to you. The six below are hypothetical; swap in real facts from your own research.

Same field, different company: "Your support team just added a dedicated tier for enterprise accounts, and the job post leans hard on cutting escalations. I spent two years reducing escalations by building self-serve docs, so this is the exact problem I'd want to own next."

New graduate: "Your analyst program rotates people through pricing and supply chain in the first year. My capstone was a pricing model for a regional grocer, and I want to see how the same questions work at your scale before I specialize."

Career changer: "You're hiring product people who've worked in classrooms, because your users are teachers. I taught for six years and spent the last one running our school's rollout of your competitor's tool, so I know where that adoption breaks."

Startup: "The team is twelve people, and this role owns analytics end to end. At my current company I own one dashboard in a team of forty. I want the whole problem, including the parts that go wrong."

Large company: "This team just moved its reporting onto a single data platform, which is the migration I ran at a smaller firm last year. I want to do it again with the kind of scale and review process a company your size has."

You mainly need the job: "Honestly, the schedule and the commute fit my life, which matters for staying somewhere. And the role is mostly reconciliation work, which I'm good at and want to get faster at. I'd rather be excellent at this than average at something flashier."

Notice that none of them uses "love," "passion" or "dream company." They don't need to. Faking these answers would require doing the research, and once you've done the research, the interest is real enough.

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

Because everyone says it, nobody can check it, and it signals nothing about fit. It tells the interviewer you found the About page and stopped there.

It also collides with what the interviewer knows about the market. In a Monster survey of 1,006 US job seekers, 48% said they frequently apply to many roles quickly instead of focusing, and 25% 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. "I'm passionate about what you do" confirms that suspicion rather than easing it. It's the same dynamic behind the application-volume trap: volume reads as desperation, and desperation reads as flight risk.

Not knowing the company can end the interview outright. In a CareerBuilder survey run by The Harris Poll of 1,014 hiring managers and HR professionals, 45% called "candidate knows nothing about the job or company" an instant deal-breaker.

Picture Priya, a hypothetical marketing analyst interviewing at a meal-kit company.

Weak version: "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 version: "Your job post says the team is rebuilding retention reporting, and your last earnings note called out churn after the first box. I built a churn cohort model for a subscription app last year. That's the problem I want to work on next."

The weak version fits any company on earth. The strong version is impossible without having looked, and it hands the interviewer a picture of Priya already working on their problem.

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

Yes. For most people the honest reason is income, not calling, and 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.

Honesty isn't just the ethical choice here; it's the safe one. In the same CareerBuilder survey, 71% of hiring managers said a candidate caught lying is an instant deal-breaker, the top item on the list. A grand fake answer collapses at the first follow-up question. A modest true one holds.

The Monster data also show that the under-investment isn't incapacity. 51% of job seekers changed their search approach because employers weren't giving feedback, and 76% said they'd be more selective if companies kept them updated. People who "just need a job" can give a specific answer. The market just hasn't given them a reason to prepare one until the interview, and the interview is exactly where preparation pays.

So find the smallest true thing. The team is small enough that you'd own a whole function. They use a stack you want to go deeper on. The schedule, commute or growth path genuinely fits your life. All of those are specific and defensible, and none require pretending the company is your destiny.

How do you research a company fast enough to sound specific?

Fifteen minutes and three sources will put you ahead of most of the room, because the bar is "knows anything specific" and many candidates clear nothing.

Source	What to pull	Time
The job post, read closely	The problem the role exists to solve, and which duty keeps coming up	5 min
One recent, dated company fact	A launch, funding round, new leader, earnings note or press release	5 min
One inside view	The team's LinkedIn posts, an engineering or design blog, employee reviews	5 min

Read the job post with suspicion, because the job description is partly fiction and the real priority is sometimes buried in the third bullet. Then stitch one item from each row into two sentences. The interviewer who heard "I admire your mission" forty times this month will remember the one person who mentioned the escalation tier.

How is this different from the "why should we hire you" question?

"Why do you want to work here?" is about them: what you noticed and why it pulls you. "Why should we hire you" is about you: proof you can solve their named problem. Interviewers often ask both, so don't give the same answer twice.

Question	What it tests	Center of gravity
Tell me about yourself	Your story and direction	Your path
Why do you want to work here?	Fit and flight risk	Their company and role
Why should we hire you?	Ability to deliver	Your proof
Why are you leaving?	Judgment and honesty	Your reasons for moving

They should still sound like one person. Your tell me about yourself answer sets up a direction; this answer shows why the direction leads here; your answer on why you're leaving your current role explains why now. If the three contradict each other, the interviewer notices. (Asked to introduce yourself instead? These self introduction scripts set up the same direction.)

When doesn't this advice work?

First, researched specificity has a cost. If you're sending forty applications a week because a thin pipeline demands it, you cannot deep-research forty companies. So tier it: spend research time on the interviews you've actually landed, not the applications you're firing off. The question only gets asked once you're in the room.

Second, sometimes there's no specific fit to find, because there genuinely isn't one. Don't fabricate one. Lead with the smallest true reason, and accept that a thin answer is a pass, not a win.

Third, hold the research loosely. The fit correlations come from studies of attitudes and intentions, not a test of this exact interview question, and the manager figures come from vendor surveys (a staffing firm, a job board, a job site) of what people say they value, one of them from 2011. The direction is consistent across all of it; the precise percentages aren't gospel.

Finally, this question rarely decides an interview on its own. In a structured interview it may be one scored item among many. It's a screen you need to pass, not a stage you need to win.

What to do now

1. Pull three facts before each interview. The problem the role exists to solve, one recent dated company event, and one detail about how the work actually happens.
2. Write your answer with the formula. Observation, connection, close, in two or three sentences. Delete every "love," "passion," "excited" and "admire."
3. Find the smallest true reason if the real one is income. Team size, stack, schedule or growth path. Lead with that instead of faking a calling.
4. Check it against your other answers. Make sure it doesn't repeat your "why should we hire you" proof or contradict why you're leaving.
5. Read it aloud and run the swap test. Could a candidate who never researched this company say the same sentence? If yes, it's still generic.

Got an interview coming up and an answer that still sounds like it could be about any company? Send Praxy the job post and the company name on WhatsApp. I'll pull the specific facts worth mentioning, help you find the true reason this role fits, and rehearse the answer with you until it sounds like you, not a careers page.