How to Answer "Why Do You Want to Work Here" Without Sounding Rehearsed

Most interviewers have already stopped listening by sentence three of your answer to this question. You spent twenty minutes reading the company's About page, found a quote from the CEO, wove in something about culture, and the recruiter's eyes went flat the moment you said "I've always been passionate about innovation."

The failure isn't lack of preparation. It's preparing the wrong thing.

The Failure Mode You're Probably Committing

The standard advice: research the company and show you've done your homework. So candidates go to the About page, the LinkedIn, maybe a recent press release — and then mirror that language back. "I'm really excited about your mission to democratize financial services." "I love how customer-centric your culture is."

Wrong way: Reciting the company's own messaging back to them as proof of enthusiasm.

Right way: Answering about the specific role at this specific company, not the company in general.

Why it works: Hiring managers can tell the difference between "I want to work for Stripe" and "I want to work on Stripe's developer experience team because I've spent three years on API infrastructure and want to work at the transaction scale Stripe handles." The former applies to fifty companies. The latter is actually answerable.

There's a common variant that sounds more sophisticated but fails the same test: leading with the company's growth stage. "You're Series C — I find that to be the most interesting inflection point for a business." That's generic too. Any of forty Series C companies gets the same statement. The other version: citing the company's Best Places to Work ranking or repeating a positive Glassdoor statistic back at them. That's not research — it's their own marketing material bounced back at the source.

The tell that you've prepared the wrong thing: if your answer works equally well for the company's main competitor, it's not an answer — it's a placeholder.

The Hidden Signal the Interviewer Is Actually Checking

This question isn't really about the company. It's about whether you'll stay.

Attrition is expensive. A new hire who quits after eight months costs companies between $25,000 and $50,000 in recruiting, ramp-up, and lost productivity — Google's people operations team has cited figures in this range for senior engineering roles. Interviewers are trying to predict whether you have genuine reasons to stick around, or whether you're using this role as a stop on the way to something else.

Wrong way: "I've been following your growth trajectory, and I think this is a great opportunity to grow."

Right way: "I've been working on API infrastructure at Twilio for three years. Stripe's combination of transaction volume — $817 billion processed in 2022 — and an API-first product constraint creates the kind of tradeoffs I want to spend the next few years on. I've also spoken with two engineers currently on your Payments Platform team, and what they described matches the public picture."

Why it works: You've named a specific technical problem, cited a real number, and mentioned due diligence most candidates skip entirely. The "I've spoken with two engineers" detail does real work — it signals commitment, it's specific, and almost no one does it.

One more thing the interviewer is checking: consistency. If your stated reason for wanting this role doesn't match the resume they're looking at, they notice. A candidate who spent eight years at large enterprises saying they want to join a 50-person startup "because of the agility" needs to explain what specifically changed. That's not disqualifying — but the generic version of that answer doesn't land.

How to Build a Real Answer in 20 Minutes

This doesn't require exhaustive research. It requires honest answers to three questions:

1. Why this role specifically — not the company, the role. What's the actual problem you'd be solving, and why is that problem interesting to you right now?
2. Why this company can't be swapped out — what does this company do that a direct competitor couldn't offer you equally?
3. Why now — what's changed in your situation or the company's trajectory that makes this timing make sense?

If you can't answer all three honestly, you're not ready to answer the question convincingly. Interviewers have heard thousands of versions of this answer and they register the absence of a real one.

The 20-minute prep routine:

1. Read the job description carefully — note the specific problems or team mandates listed. (5 min)
2. Read one engineering blog post, PM case study, or public technical decision from the company. (8 min)
3. Talk to one person who works or has worked there, or read at least five recent Glassdoor reviews from similar roles. (5 min)
4. Draft your answer in two sentences without notes. If you can't, repeat step 1. (2 min)

The research in steps 1–3 doesn't need to be exhaustive — it needs to be specific. One concrete detail from one good source beats ten surface-level facts. "I read your CTO's post from March about migrating to a service mesh" is more useful than "I know you use microservices."

Say it out loud before you go in — not silently, out loud. Your brain processes the coherence of spoken language differently than written language, and most problems in this answer surface only when you hear yourself say it.

What "Good" Actually Sounds Like

A senior software engineer interviewing for Notion's infrastructure team in 2024 was asked this question during her hiring manager screen. Instead of saying "I love the product" — the instinctive answer, given Notion's devoted user base — she said:

"I've been running backend infrastructure for a collaborative tool at Figma for two and a half years. The hardest problem in that space is real-time sync at scale under aggressive latency constraints. I've read Notion's technical posts about the block-based data model migration, and I want to work on the layer directly below that. What I can't get at Figma is a younger infrastructure team where I'd have more end-to-end ownership, combined with a document model that creates genuinely unusual database constraints."

That answer works because it names a specific technical problem, references a real Notion technical artifact, is honest about the career motivation, and makes no claim about being passionate about note-taking software. The recruiter moved her to the next round within two hours.

Here's the gap between her answer and a generic one:

The right column isn't longer — it's falsifiable. The interviewer can actually check whether Notion has a block-based model, whether it's around 300 engineers, whether two engineers said the on-call is manageable. Falsifiability is what makes it credible.

Practicing This Out Loud (Before It Counts)

Reading good examples doesn't prepare you to deliver one. Most candidates who know exactly what they should say still revert to the generic version when nervous, because under pressure the brain reaches for the rehearsed script — and the rehearsed script is usually the generic one they prepared first.

IntervYou runs AI-powered mock interviews where you practice this specific question with real-time feedback on whether your answer reads as generic or specific. The system flags vague language and scores answer concreteness — useful because most people can't identify their own vagueness without an outside observer.

The fix for reverting under pressure is repetition. Practice the answer fifteen times, not once. By the tenth run-through, you stop thinking about the words and start thinking about the content — which is when it stops sounding rehearsed.

Pre-interview checklist:

• Can I name one specific problem this role is hired to solve?
• Can I say what this company offers that a direct competitor doesn't equally?
• Have I spoken to or read reviews from at least one person in a similar role?
• Have I referenced one specific public artifact (blog post, product decision, technical paper)?
• Is my answer under 90 seconds when said out loud?
• Does my answer include at least one specific number (team size, scale metric, year)?
• Can I deliver this without notes?

Seven checks. If you hit all seven, your answer is in the top 10% for this question.

What to Do If You Genuinely Don't Have a Strong Reason

Sometimes the honest answer is: the compensation is better and you've been ready for a change. That's fine. Most experienced candidates are job-searching for a mix of reasons, not one inspirational one.

But you still need to construct a real answer for the interview. The approach: find the overlap between something true in your professional history and something specific about the role. Even if you're applying broadly, there's always one thing about this specific role that's at least marginally more true for you than the same role at a direct competitor.

A senior PM at Amazon was interviewing for a fintech product role at Lean Technologies in 2023 — applying to twelve companies simultaneously, no particular attachment to Lean specifically. She spent 15 minutes identifying what was genuinely distinctive about Lean's product problem: open banking API infrastructure for the MENA region, a regulatory and technical constraint she'd studied as part of Amazon's international expansion work. She mapped that to her background in payments. She didn't claim passion for Lean. She claimed interest in the specific problem, which was accurate.

This approach works because it anchors your answer in problem specificity rather than company preference. The interviewer isn't evaluating your enthusiasm for their brand — they're evaluating whether you've thought carefully about the work. Careful thinking about the work is a signal of competence, not just cultural fit.

The shift: stop answering "why this company" and start answering "why this specific problem at this company right now." That version you can always answer honestly, regardless of how many other companies are on your list.

The reason you sound rehearsed isn't that you practiced too much — it's that you practiced the wrong version. Generic answers feel safe because they're positive and expose no real reasoning. Specific answers feel riskier because they require committing to actual positions. That's exactly why interviewers trust them more. Practice the riskier version with IntervYou before the conversation that actually counts.

Start a free mock →