Late in a screen, after the product question and the follow-ups, I ask the one that sounds like a formality: why this company? It is the moment most candidates relax, and it is the moment they blur together. The answer I hear back is usually some arrangement of the same three ideas, admiration for the scale, respect for the culture, and a line about using the product. All true, all forgettable, and all of it would fit on any other company's application without changing a word.
The 'why this company' question in a PM interview is not small talk before the offer. It is a scored read of whether you did the work to understand this specific product, problem, and bet, or whether you are reciting prestige because the logo is impressive. A recruiter is estimating whether you will actually accept and stay. A hiring manager is deciding whether your motivation is specific enough to predict you will do the job well once the novelty wears off. 'I admire your mission' answers neither.
Why the question carries real weight
The question shows up earlier than candidates expect. It lands in the recruiter screen, where a non-PM is comparing your answer to the job description and gauging flight risk, and it comes back on the loop, where the people who would work with you are deciding whether your reasons hold up. Because it arrives early, it sets the lens the rest of the loop gets read through. A specific, grounded answer buys you the benefit of the doubt on a shaky follow-up later. A generic one makes every 'we' in your project stories a little easier to doubt.
There is a sibling question that gets confused with this one. 'Why product management' asks whether you understand and want the craft, which we cover in the answer that doesn't sound rehearsed. 'Why this company' asks something narrower: of all the places you could do that craft, why here, and why now. Answering the first when you were asked the second is one of the quiet ways candidates give away the point.
What the interviewer is actually scoring
Strip away the pleasantries and a strong answer is doing four things at once.
- Specificity you could not fake. You name an actual product surface, a problem the company is working on, or a bet it has placed, and you hold a point of view about it. Generic praise signals you read the careers page and stopped there.
- Genuine motivation over prestige. Wanting to work on a hard delivery-logistics problem is a reason. Wanting the brand on your resume is a reason too, and it is the one the interviewer is trying to rule out.
- Fit with what this role actually is. Your reason connects to the team, the surface, or the stage of the product you would own, and not to the company in the abstract.
- A forward connection to you. The reason ties to what you have built and what you want to do next, so it reads as a decision you made rather than a slot you are filling.
| What a candidate says | What the interviewer writes down | The stronger version |
|---|---|---|
| I really admire your culture and the scale you operate at. | Could be pasted into any application. No sign they looked at the product. | I have followed how your payments team handled X, and I think the next hard problem there is Y, which is what I want to work on. |
| I use the product every day and love it. | Reads as a fan with no product judgment attached yet. | I use it every day, and the first thing I would change is Z, because the current flow loses new users right when they X. |
| It is a great opportunity and a great next step for my career. | The company is a means to their end. Flight risk. | This is where the problem I care about is being worked on at real scale, and my last two roles were building toward exactly this. |
| Your mission really resonates with me. | Mission as a slogan, with no connection to the work. | Your mission showed up in decision X the team made last year, and I want to be in the room for the calls like that one. |
The fastest test I apply to a 'why this company' answer is whether it survives a find-and-replace. If I could swap in a competitor's name and the answer still works, it was never about this company. The answers that land name something specific enough that they would fall apart anywhere else.
Why 'why this team' beats 'why the logo'
Specificity has levels, and most candidates stop one or two rungs too high. The company is the vaguest level (scale, brand, mission). The product is better (a surface you have opinions about). The team and the problem are best (the actual work you would own and why it matters now). The closer you get to the team and the problem, the harder the answer is to fake, and the more it sounds like someone who chose this role on purpose. This is also why the hiring manager weighs 'why this team' so heavily, which we break down in the PM hiring manager interview.
I want to work here because you are one of the best companies in the world, the products reach billions of people, and I would learn a huge amount from people who are the best at what they do.
A weak answer (illustrative). Every clause is about the company's prestige and what the candidate would get, and none of it would fall apart if you named five other companies.
I spent two years on retention for a subscription product, and the churn problem I never fully cracked was winning people back after they cancel. Your team shipped the pause-instead-of-cancel flow last year, which is the most interesting take on that problem I have seen. I want to work on the next version of it.
A strong answer (illustrative). It names a specific bet the team made, ties it to a real problem the candidate has lived, and points forward. It would collapse if you swapped the company name.
Do the work the afternoon before. Read the product like a PM rather than a fan: try the core flow, find the recent launches, read what the company has said publicly about its strategy, and form one real opinion. A single specific, defended opinion about the product beats a paragraph of admiration.
How to build an answer that is only yours
You do not need a long answer. Sixty to ninety seconds, built in four moves:
- Name the specific thing. A product surface, a problem, or a bet the company has made that you genuinely have a view on.
- Say why it matters, and add your take. What is interesting or hard about it, and what you would do or watch closely. This is where your product judgment shows up.
- Connect it to you. Tie it to what you have built and what you want to do next, so the reason is grounded in your track record.
- Land it. One sentence on why this is the place you want to do that work now, and stop there. Do not pad it with culture praise.
A light structure is doing useful work here: it keeps the answer from wandering into a resume recap, and it leaves room for the substance, which is the specific product opinion you bring. Interviewers can tell a formed view from a fabricated one in about a sentence, which is the same reason borrowed answers to every round fall flat, a theme we cover in why every candidate sounds the same.
The mistakes that flatten the answer
- Prestige and scale. 'You are the biggest, the best, the most impressive.' It flatters the company and says nothing about you or the work.
- Perks and comp. Naming the salary, the office, or the brand value as the draw tells the interviewer the company is a means to your end.
- 'I use it every day' with no depth. Being a user is table stakes. Without a product opinion attached, it reads as a fan rather than a builder.
- Culture platitudes. 'Your values align with mine' with no example is a sentence the interviewer has heard a hundred times this quarter.
- Answering 'why product management' instead. Motivation for the craft is a different question, so do not spend your 'why this company' moment on it.
- The find-and-replace answer. If a competitor's name fits without changing a word, you have not answered the question.
None of this is about performing enthusiasm. It is about having a real reason and saying it plainly. The hard part is that the reason has to be built before the room, and most people assemble it for the first time while the interviewer is waiting. The fix is reps: say the answer out loud, hear where it goes generic, and tighten it. That is what practicing with a tool like Live Mock is for, a real-time mirror of your best self that runs the follow-ups a real panel would ('why not our competitor, then?'), so the vague version does not survive to the actual interview. It also pairs with the other unscripted moment of the loop, the questions you ask your interviewer, which get scored on the same axis of whether you did the work.
Practice your 'why this company' answer out loud Try it free →
Unlimited mock reps with real follow-ups, so the generic version never reaches the real room.- Is 'why this company' really scored in a PM interview, or is it just a warm-up?
- It is scored. It usually appears in the recruiter screen and again on the loop, and it sets the lens the rest of the interview is read through. Recruiters use it to gauge whether you will accept and stay; hiring managers use it to judge whether your motivation is specific enough to predict you will do the job well. A generic answer here makes the rest of your loop read as less genuine.
- How is 'why this company' different from 'why product management'?
- 'Why product management' asks whether you understand and want the craft. 'Why this company' asks why, of all the places you could do that craft, you chose this one and this moment. They are separate questions, and answering the first when you were asked the second is a common way to miss the point. The career-motivation question has its own guide.
- How long should the answer be?
- About sixty to ninety seconds. Name a specific product surface, problem, or bet you have a view on, say why it matters and what you would do, connect it to your own experience, and land on why here and now. Longer than that and it drifts into a resume recap or a fan letter.
- What if I do not have a strong personal reason to want this company?
- Find a real one before the interview by doing the work: use the product like a PM, read the recent launches and the stated strategy, and form one honest opinion about a problem the team is working on. A grounded professional reason, that this is where a problem you care about is being worked on at scale, is stronger than a manufactured emotional one, and far stronger than prestige.
- Is it bad to say I want to work here for the brand or the learning?
- Said as the main reason, yes. Brand and growth are things the company gives you, and the interviewer is specifically trying to rule out the candidate whose only draw is what they would get. Lead with a specific reason about the product or the problem, and the learning takes care of itself.