How to Answer Why Do You Want This Job

A convincing answer links three things specifically.

• The role: name what about the actual responsibilities excites you, drawn from the job description, not a title.
• The company: reference something concrete and true, a product, a mission, a recent move, or a way of working, so it is clear you chose them.
• You: connect it to your trajectory, showing how this role fits where you are going and what you can contribute.

The test is simple: if your answer could be pasted into an application for a rival company unchanged, it is too generic. Make it so specific that only this company and role would fit.

Strong version: "Three things pulled me to this role. First, it's a product analytics position that owns the full loop from question to experiment to decision, which is where I do my best work rather than just building dashboards. Second, your team publishes openly about how you run experimentation, and that culture of learning in public is rare and something I want to be part of. Third, I've spent two years in fintech and want to apply that in a consumer product at scale, which is exactly what this role offers. It's a genuine fit with where I want to grow."

This works because every clause is specific to the role, the company, and the candidate's path; none of it could be copied to another application.

Weak version: "I want this job because it's a great company with a good reputation, and it seems like a good opportunity for my career growth. I've heard good things and I think it would be a good place to work."

This fails because it is entirely interchangeable. "Good company, good opportunity, career growth" could describe any employer and reveals no research or genuine interest. The interviewer learns nothing about why you, specifically, chose them. The fix is to swap every generic phrase for a concrete detail about the actual role and company, and to tie it to your own direction.

Praising only prestige or pay: "you're a top company" flatters but signals you would leave for the next big name. Focus on the work.

No company specificity: if you cannot name anything concrete about them, do more research before the interview.

All about you: career growth alone sounds one-sided. Show what you give as well as gain.

Interchangeable phrasing: stress-test your answer against the paste test above.

Because this answer relies on sounding sincere, rehearse it aloud. InterviewPrep's free AI voice mock draws on the job description you provide, lets you practise this answer, and gives feedback on pace and filler words so it lands as authentic rather than recited.

The difference between a generic answer and a compelling one is almost entirely research done beforehand. You cannot sound genuinely interested in a company you know nothing about. Spend time gathering concrete, true details you can reference naturally.

• The product or service: use it if you can, or understand it well enough to speak about what you admire or would improve.
• The mission and values: find what the company says it stands for and connect it honestly to something you care about.
• Recent news: a launch, expansion, funding round, or initiative gives you a timely, specific hook.
• The team and role: understand what this specific team does and how the role contributes.

Then weave one or two of these details into your answer so it could only apply to this company. Avoid the trap of praising prestige or size alone, which signals you would leave for the next big name; focus on the actual work and fit. Finally, connect it to your own trajectory so the answer shows mutual benefit, not just what you want. Rehearsing it aloud helps you deliver the specifics smoothly, so your genuine interest comes across as sincere rather than a paragraph you memorised the night before the interview, because interviewers can usually tell the difference between genuine interest and a rehearsed recital.

When applying through LinkedIn Jobs India, spend an extra five minutes on each application to note one true, specific detail about the company you can reference here.