This question tests whether you've actually researched the company and can connect it to a genuine motivation. Generic answers ("great brand, good growth") fail. The structure: company specifics → why they matter to you → what you bring.

1. Company-specific reasons (do the research)

Pick 2–3 real, concrete things, e.g.:

• Problem domain: "Payments and financial infrastructure are hard, high-stakes problems — correctness, reliability, and latency genuinely matter. I want to work where the engineering bar has to be high because mistakes cost real money."
• Scale: "Razorpay processes payments for millions of businesses; building frontends that stay fast and reliable at that scale is exactly the kind of challenge I'm looking for."
• Product breadth: "It's not just a payment gateway anymore — RazorpayX, Capital, payroll. As a frontend engineer that means a real product surface and room to grow across domains."
• Engineering culture: reference something concrete — their engineering blog, open-source work, how they talk about their stack.

2. Why it matters to you

Tie it to your trajectory: "I've been building product UIs and want to go deeper on systems where correctness and performance are non-negotiable — fintech is that. I also want to work on products used by businesses daily, where UX quality directly affects whether someone gets paid."

3. What you bring

Briefly connect your strengths to their needs — performance work, design-system experience, ownership — without listing your whole résumé.

What to avoid

• Generic praise that could apply to any company.
• Making it only about you (comp, brand on the résumé, growth stage).
• Anything that signals you didn't research them.
• Overclaiming passion you can't back up — be genuine and specific instead.

The honest version

If you don't have a deep reason yet, find a real one before the interview: read their engineering blog, try their product, look at what they've shipped recently. A specific, true reason always beats a polished generic one.