Why This Company & Why This Role

This question separates candidates who applied everywhere from those who genuinely want THIS job. Interviewers use it to gauge motivation, culture fit, and whether you did your homework — a generic answer signals you'll leave at the first better offer.

The 3-lever answer

Blend three sources so the answer is specific and two-way:

Lever	What to reference
Company	A product, value, tech stack, or recent news you genuinely admire
Role	The specific responsibilities that match your skills/goals
Fit	What you bring AND what you'll grow — make it mutual

Structure: "I admire [specific thing about company] → the role lets me [do X I'm good at] → and I'll grow in [Y]."

Exam Tricks & Tips

• 🎯 Name something specific and recent — a feature they shipped, a funding round, an engineering blog post. Generic praise ("great culture") sounds copy-pasted.
• 🎯 Connect the role to your evidence — link a JD responsibility to a project you've done.
• 🎯 Research the tech stack and mention it if it overlaps your skills.
• 🎯 Make it mutual — say what you give and what you gain; pure "I want to learn" reads as one-sided.
• 🎯 Avoid money/location as the reason even if true — lead with growth and product.
• ❌ Common mistake: praise that fits any company ("You're a market leader with great people") — it proves zero research.

Expected pattern: "Why us?", "Why this role?", "What do you know about our company?" — often back-to-back.

Quick recap: One specific company hook + role-to-skill link + mutual fit. Research beats flattery.

Cover the answer, recall, then check. 11 cards on "Why this company / role."

Q1. What three levers should this answer blend?
A1. Company (specific thing you admire) + Role (responsibilities matching your skills) + Fit (mutual give-and-grow).

Q2. Why is a generic answer dangerous here?
A2. It signals you applied everywhere and will leave for the next offer — poor motivation/fit.

Q3. What makes the "company" part credible?
A3. Naming something specific and recent: a shipped feature, funding, a tech-blog post, a value.

Q4. How do you tie the role to yourself?
A4. Link a specific JD responsibility to a project or skill you can point to as evidence.

Q5. Why should the answer be "mutual"?
A5. Pure "I want to learn" is one-sided; state what you give AND what you gain.

Q6. What reasons should you NOT lead with?
A6. Salary or location — even if true, lead with product and growth.

Q7. What phrase pattern works well?
A7. "I admire [specific X] → the role lets me [do Y I'm good at] → and I'll grow in [Z]."

Q8. What does this question really measure?
A8. Motivation, culture fit, and whether you researched the company.

Q9. Why avoid "great culture / market leader"?
A9. It fits any company and proves you did no real research.

Q10. How can the tech stack help your answer?
A10. Mentioning an overlapping stack shows genuine interest and readiness to contribute.

Q11. Common rephrasings of this question?
A11. "Why us?", "Why this role?", "What do you know about our company?"

"Why do you want to work here?" and "Why this role?" separate candidates who did their homework from those spraying the same application everywhere. A generic answer ("great company, good learning") signals you'd take any offer. A specific answer signals genuine interest — and interviewers push much harder for candidates who clearly want this job.

What this covers / why it matters: how to research a company fast, how to connect its needs to your goals, and a model answer. This question is a near-certainty in HR rounds and a common closer in technical ones.

The approach

Beginner — the three research buckets

Fifteen minutes of prep beats any amount of charm. Gather one concrete point from each:

• The product / tech — what do they build, and what stack or problem excites you? (Check their engineering blog, careers page, app.)
• The company — a recent launch, funding round, mission, or value that resonates.
• The role — what does this specific role do, and which of your skills or interests map onto it?

Intermediate — the fit equation

Structure the answer as What they do + why it excites me + what I bring. The third part is what candidates forget: don't only say why they're great, say why you two fit. "You're scaling payments across Southeast Asia — I've worked on reconciliation systems and want to solve exactly those correctness-at-scale problems."

Advanced — mirror their language and priorities

Read the job description and the company's own words, then echo their vocabulary and priorities back. If they stress "ownership" and "customer obsession", reference a time you owned something end-to-end for a customer. You are demonstrating that you already think like they do.

Worked example

"Two things pulled me toward this role. First, the product — I've been using your app for a year, and when I read your engineering blog post on how you handle offline-first sync, I realised you're solving problems I find genuinely interesting rather than routine CRUD. Second, the role itself is backend-heavy with real scale, which is where I want to grow — my internship was backend but small-scale, and I want the challenge of systems serving millions. And I think I bring something useful: I've built reconciliation and data-consistency features, which maps directly to the payments work this team does. So it's less 'a job' and more 'the specific problems I want to be working on'."

Specific product reference, honest growth motive, and a concrete skill match.

What interviewers look for

• Genuine research — did you learn something real about them?
• Two-way fit — not just "you're great" but "we match".
• Alignment — do your goals point the same way as the role for the next couple of years?
• Enthusiasm that's specific, not flattery.

Do's and don'ts

• Do name one concrete thing about the product, tech, or mission.
• Do connect the role to your own trajectory.
• Don't talk only about what you'll get (salary, brand, learning) — show what you'll give.
• Don't give an answer that would work for any company.
• Mnemonic: PEP — Product, Excitement, my Part.

Worked Example

Problem/Question: "Why do you want to work here, and why this role?"
Solution/Model answer: Show you did your homework and that there's a genuine fit — link their mission/product to your skills and goals.
Why the company (specific, researched): "I've followed your open-source contributions to the Kafka ecosystem, and your engineering blog on handling 10x traffic during sales convinced me you take reliability seriously — that's the kind of engineering culture I want to learn in."
Why the role (fit both ways): "This backend role focuses on distributed data pipelines, which is exactly where I've been building my skills — I wrote a small stream-processing project last semester. I can contribute my SQL-optimisation and API experience now, while growing toward large-scale systems."
Avoid: generic praise ("you're a great company"), or making it only about what you get.
Answer/Takeaway: Answer with researched specifics about the company (a product, blog, value) tied to concrete reasons the role fits you — demonstrating two-way fit (what you'll contribute and what you'll grow into), not generic flattery.