Guide · behavioral-prep
How to Answer 'Why This Company?' in an Interview
Skip the mission-statement recital. Cite something specific the company has shipped, written, or struggled with publicly — then connect it to a skill you bring or a problem you've solved before. The point is to prove you actually researched them, not to flatter them.
By Alex Chen, Founder, InterviewChamp.AI · Last updated
How do you answer "why this company?" in an interview?
Cite something specific the company has shipped, written, or struggled with publicly — then connect it to a skill you bring or a problem you've solved before. The structure is: specific thing about them → concrete connection to you → short question back. Skip the mission-statement recital and skip generic flattery. The point is to prove that you researched them.
The 3-part structure
A strong answer has three moving parts, all under 60 seconds.
Part 1 — Their specific thing (15-20 seconds). Name one concrete object: a product they shipped, an engineering blog post, a public talk, a problem they're actively working on. Example: "Your team published a deep-dive on [specific topic] in March. The way you handled [specific tradeoff] is the same problem I hit on my internship last summer."
Part 2 — Your specific connection (15-20 seconds). Tie that thing to a skill, project, or interest you actually bring. Concrete beats abstract. "I've spent the last six months working on [related thing]. I'd love to bring what I learned into a system at your scale."
Part 3 — A short question back (10-15 seconds). End with a question they'd enjoy answering. "Is the team still iterating on [thing], or has that work mostly settled?" Now it's a conversation, not an audition.
Where to find your specific thing
Three places, in order of payoff for time invested:
- The company's engineering blog or research page. Read the two most recent posts. One usually contains a tension, a tradeoff, or a problem statement you can quote.
- Their job description, read carefully. The "responsibilities" section often telegraphs the work the team actually does this quarter. Mirror its language.
- Public talks or podcasts from the team. Senior engineers and engineering leaders speak more than candidates assume. A 20-minute talk gives you three quotable lines and at least one good question to ask.
Per the Indeed Career Guide on company research, candidates who cite a specific recent product or blog post in their interview score measurably higher on "fit" signal than those who recite the company's official mission statement.
What to never say
Three answers that read as low effort even when the rest of the interview is strong:
- "I really admire your mission to [paraphrased mission statement]." Every candidate says this. The phrase has lost all signal value.
- "I want to work somewhere I can grow." Every candidate says this too. Growth is a default, not a differentiator. Say where, specifically, you want to grow.
- "I love your products." If you love them, prove it. Name the feature, the design decision, or the moment the product surprised you. Otherwise it sounds like LinkedIn boilerplate.
When you don't actually know much about them yet
Sometimes a recruiter throws you into a loop you didn't have a week to prep for. Be honest about it, then earn the answer:
"I'll be honest — when [recruiter] reached out, I didn't know your team well. I spent the last two days reading [specific thing] and what stood out to me was [specific takeaway]. That's the thing I want to dig into."
This answer is stronger than fabricated enthusiasm. According to research summarized by Harvard Business Review on authenticity in interviews, hiring managers consistently rank "honestly curious" higher than "performatively enthusiastic" — but only when the honesty is paired with evidence of follow-up effort.
The signal you're sending isn't "I love this company." It's "I take this seriously, and I do the work." That's what gets you to the next round.
About the author: Alex Chen is the founder of InterviewChamp.AI and writes about the modern tech interview from the inside — what changed, what works for new grads, and where the old playbook fails.
Frequently asked questions
- How specific should my 'why this company' answer be?
- Specific enough that the answer couldn't be reused for a competitor with a find-and-replace. Cite a product they shipped, a blog post they wrote, or a public problem they're working on — and connect it to a skill or interest you actually bring.
- Should I mention compensation or perks?
- No. Hiring managers want to hear about the work and the team. Comp comes up at the recruiter stage and during the offer conversation, not when a hiring manager asks 'why this company?' Save it.
- What if I'm interviewing at a company I don't actually love?
- Find the one thing that's interesting. Every company has at least one. Maybe it's the scale, the domain, the technical bet, or a person on the team whose work you respect. Lead with that single concrete thing and stop there.
- Is it okay to say 'I want to learn from your team'?
- Only if you can name what you want to learn and from whom. 'I want to learn from your distributed-systems team because they wrote X about Y' is a strong answer. 'I want to learn from senior engineers' alone is filler.
- How long should the answer be?
- 30-60 seconds. One specific reason, one connection to you, one short follow-up question for the interviewer. Anything longer turns into a pitch and signals that you're trying to convince yourself, not them.