🎯Why This Company
Generic answers get filtered. Specific answers tied to recent company moves win the room.
Every loop asks 'why us?' The candidates who research deeply and answer specifically come across as serious; those who don't seem like they're applying broadly without intention.
A great 'why this company' answer ties three things: (1) a specific company bet you find compelling, (2) why your background uniquely fits, (3) what you'd contribute. Generic answers ('I love your products') get filtered. Specific answers force the interviewer to take you seriously.
The structure (60-90 seconds)
1. Specific bet (20 sec). Name a specific company decision or direction you find compelling. "Your bet on AI agents in [product]..."
2. Why your background fits (30 sec). Connect your experience to that bet. "My last 18 months building AI features at [company] gives me direct experience with..."
3. What you'd contribute (20 sec). Specific. "I'd bring the eval discipline and agent-design framework I've been refining."
4. Why now (10 sec). Why this is the right time for you and them.
What separates A from B
- A: Reference a specific recent company move. "Your recent acquisition of X" or "your blog post on Y."
- B: Generic compliment. "I love your products."
- A: Connect to your unique fit. "My AI PM experience matches your bet on..."
- B: Generic enthusiasm. "I'd love to be part of the team."
- A: Specific contribution. "I'd bring frameworks for X."
- B: Vague. "I'd add value."
Sample (Stripe)
"Three things. First, Stripe's bet on Climate and embedded finance is one of the most interesting product expansions I've watched — turning a payments company into an infrastructure layer for the future of money. I want to work on bets at that level of ambition.
Second, the memo culture. The discipline of writing as the dominant artifact maps to how I work best — I've been the PM at my last two companies who pushes for written strategy docs, and at Stripe that's the default rather than the fight.
Third, the developer-first ethic. My engineering background means I'd be naturally drawn to the work; the bar Stripe holds on developer experience is higher than anywhere else I know.
Specifically the [role]: I'd bring [specific experience] that compounds with the team's current bets on [specific area]."
Research checklist before the interview
- Last 6 months of company blog posts
- Recent product launches and their narratives
- CEO/CPO public talks or interviews
- 10-K (if public)
- Twitter / LinkedIn of leadership team
- Competitive context — who they're competing with
20-30 min of research before each interview is non-negotiable.
Watch-outs
- Don't fake passion. Hiring managers smell it instantly.
- Don't compare unfavorably to other companies. Reads as 'I'd take any job.'
- Don't focus only on what you'd get. Emphasize what you'd give.
- Don't memorize. Have the structure, deliver naturally.
Real-world examples
Hiring managers report that 'why this company' is the single most-predictive answer of cultural fit. Candidates with specific, researched answers tend to also have specific, researched answers throughout the loop.
Go deeper — recommended reading
Interview questions (1)
Q1Why this company?behavioraljunior▼
Structure: specific bet + your unique fit + what you'd contribute.
Generic answers like 'I love your products' get filtered. Specific answers stand out.
Example for Stripe: "Stripe's bet on Climate and embedded finance — turning a payments company into infrastructure for the future of money — is the kind of ambitious roadmap I want to work on. My engineering background and the AI PM work I've been doing for the past 18 months map directly to where Stripe's headed. I'd bring [specific experience] that compounds with [specific team bet]."
Do 20-30 min of company research before each interview. Read recent blog posts, recent launches, CEO talks. The specificity is what separates serious candidates from broad applicants.