"Why do you want to work here?" (PM interview)

Q: Why do you want to work here?

What interviewers actually score on this question, the failure modes that end candidacies, and a worked example answer you can adapt.

This question rarely makes a candidate look great. It does regularly end candidacies. At mission-driven companies (Anthropic, Stripe, Notion, Figma), a weak answer functions as a pass/fail gate regardless of how well you perform in every other round. Treat it as a warmup at your own risk.

What the interviewer is actually listening for

The surface question is “why here?” The actual signal is: does this candidate have a point of view on what we are building and why it matters right now? Interviewers are not scoring company knowledge. They are scoring whether you have thought about the problem this company is attacking, whether you understand why this company is positioned to solve it, and whether you can connect that to work you have actually done.

There is an asymmetry worth naming. Behavioral interviewers place this question at roughly 10 percent weight on formal rubrics. At companies with explicit mission filters, it operates as a binary screen before the rubric is applied at all. You can score in the top quartile on every subsequent question and be passed on because the hiring manager does not believe you actually want to be there.

The failure modes that disqualify otherwise strong candidates:

Emotional enthusiasm without analysis. “The mission really resonates with me” is approval-seeking, not a view. It names a real thing and attaches a feeling to it. That is not conviction.
Reciting homepage copy. Mentioning “growing the GDP of the internet” (Stripe) or “responsible AI development” (Anthropic) without a follow-on opinion signals 10 minutes of prep, not sustained engagement. Interviewers at senior levels can tell the difference between someone who has followed a company for months and someone who read the About page last night.
Three reasons without commitment. Listing culture, mission, and market opportunity without committing to a specific view on any of them reads as not knowing why. Pick one and make it real.
“I love AI” at an AI lab. At Anthropic, OpenAI, and DeepMind, general AI enthusiasm actively hurts. These companies use this question to screen for intellectual honesty about hard trade-offs. A candidate who names a specific tension the company faces (safety vs. capability, open vs. closed, agent autonomy vs. guardrails) and has an actual view on it outperforms a candidate who says AI is exciting.

The 2026 reframe

In 2026, almost anything can be built. Feasibility is not the constraint. What is hard: identifying problems that are genuinely viable (the market exists, people will pay, the business can sustain itself building for it), and building things that are genuinely lovable (meeting users where they already are, anticipating needs without being obnoxious, reducing friction at the right step rather than adding a new UI surface).

A strong “why here” answer in 2026 names the specific viable problem the company is attacking, explains why this company has a structural edge on that problem, and ideally connects to a moment where you saw the product working or failing in the world. For AI-native companies especially, you need to name a real tension and take a position. “I’m interested in AI” does not answer “why Anthropic.”

Calibration by seniority

An APM answer can lead with genuine user experience: “I’ve used this product for three years and I have strong opinions about where it should go.” That is credible for an early-career candidate. A staff PM answer should lead with market structure: why this problem, why this company’s position in the market, why now. Senior candidates who lead with personal enthusiasm read as undercooked on business judgment.

strong

"I've been following Stripe's approach to financial infrastructure for about three years, specifically how they've expanded from payments into tax, treasury, and embedded finance for platforms. The move that crystallized it for me was Stripe Tax: they took a problem that every internet business has but almost no one wants to own, and turned it into a distribution moat. That's the kind of product thinking I want to be around. My background is in developer-facing products where adoption happens through individual engineers before it reaches procurement, and I think Stripe is one of the few companies where that bottom-up motion is still the actual strategy, not a legacy. I'd be working on a problem that's genuinely hard: not hard to build, but hard to make people trust enough to run their compliance on. That's where I do my best work."

weak

"Stripe has always been a company I've admired. The culture of craft, the quality bar on documentation, and the mission of growing the GDP of the internet really resonate with me. I also think payments and financial infrastructure is a space with a lot of room to grow globally."

This answer names real things. It has no opinion on any of them. "Really resonates with me" is the tell: it is approval-seeking, not analysis. It could have been written by anyone who spent 10 minutes on the Stripe homepage. Three reasons are listed without committing to one, which reads as not knowing the actual reason. Nothing in this answer required sustained engagement with the company. The interviewer knows it.

The honest-answer problem

Some candidates genuinely want the job partly for compensation or career trajectory. Interviewers know this. Naming it is not disqualifying; leading with it is. “The comp is competitive and the brand opens doors” is a legitimate reason to take a job. It is not a reason to believe you will build good product there.

The frame that works: acknowledge the practical factors briefly if they come up, then pivot to the specific product problem you want to work on. Interviewers are not looking for saints. They are looking for candidates whose motivation has enough substance to sustain hard work when the practical factors stop mattering.

What specific looks like

The line between real research and generic research is not about quantity of facts. It is about having an opinion. A candidate who can name the last major product decision a company made and say “I think that was the right call because X” or “I think that was a mistake and here is what I would have done” is demonstrating genuine engagement. A candidate who names the same fact without an opinion is demonstrating they can search.

For AI-native companies (Anthropic, OpenAI, Perplexity, Cursor), the bar is that you engage with a real tension the company faces and take a position. Knowing that Anthropic cares about safety is not a view. Having a perspective on how their Constitutional AI approach trades off against capability at the frontier is a view. For more on what Anthropic specifically screens for, see Anthropic values required reading and how AI changed PM interviews.