What the interviewer is really asking
This question tests three things:
- Effort: did you research this company, or send the same application to fifty?
- Fit: do your goals match what the company can offer?
- Commitment: will you stay, or is this a backup option?
A specific answer signals all three. A generic one (“It is a reputed company with a good work culture”) signals none.
It also tells the interviewer whether you understand what the company actually does day to day. Many candidates talk about the brand, the logo or the size of the company. Very few talk about its customers, its products or the problems its teams work on. Doing that alone puts you ahead of most of the people interviewing that day.
Treat it as a short pitch, not a speech.
Where to find specific reasons
- The job description: the tools, clients and responsibilities named there.
- The company website: products, services, clients, case studies, recent news and awards.
- People who work there: professional profiles, talks and articles by team members.
- Your own experience: have you used their product, visited their store or been treated at their hospital?
Write down three facts. You will use two in the answer and keep one in reserve for follow-ups.
Check that your facts are current. Mentioning a product that was discontinued or a leader who has left shows shallow research. A quick look at recent news or the company’s own announcements before the interview avoids that.
Also note anything you personally like about how they work, such as how they treat customers or share knowledge in public talks. Personal observations make the answer sound genuine.
A simple structure
- Reason one + link: “Your firm handles statutory audits for manufacturing companies, and I spent my articleship on exactly that.”
- Reason two + link: “I also noticed you train juniors on data analytics for audits, which is a skill I want to build.”
- Contribution: “So I can add value from day one on audit work while growing into analytics.”
This answer overlaps with why should we hire you, but the focus is different: here, lead with the company; there, lead with yourself.
Say it in your own words. A researched answer delivered naturally beats a perfect script recited from memory.
If you have used the company’s product or service yourself, mention it briefly. First-hand experience is one of the most convincing reasons you can give, as long as you connect it to the work you would do.
How to adapt by situation
- Big, well-known company: go beyond the brand. Talk about the specific team, product or project.
- Startup: talk about the problem they are solving, the stage they are at and the ownership you want.
- Hospital, school or public service: talk about the people served, the specialities or programmes, and the kind of practice you want.
- Agency or consultancy: talk about their clients, industries and the variety of work.
- Moving industries: explain why this industry, then why this company in it.
In every case, the test is the same: could you say this answer to a competitor? If yes, add one more specific detail.
For smaller or lesser-known employers, the people you would work with and the variety of the work are often the strongest reasons.
Tailor your application to match
Your resume and cover letter should tell the same story. Use the tailor resume to job tool to align your resume with the post, and the cover letter generator to put your reasons in writing before the interview, so saying them aloud feels natural.
Before the interview, say your answer aloud a few times, ideally to someone who will tell you if it sounds generic. Replace any phrase that could describe any company, such as “good growth opportunities”, with a concrete detail such as the name of a programme, a product or a client segment. Then practise it once more in the interview practice tool.
Aim for about forty-five seconds, then stop and let them respond. A short, specific answer invites a good follow-up question.
Example answers
Sample people — keep the structure, then use your own facts and numbers.
-
Fresher (campus hire)
I have two reasons. First, your company builds billing software for small retailers, and I spent my final-year project building a simple inventory app for my uncle’s kirana store, so I already understand the problems these shop owners face. Second, I read that new engineers here rotate through support and development in their first year. I want to learn how customers actually use the product before writing code for it. I think I can contribute quickly on the retail side while learning your stack properly.
-
Experienced (5 years)
I have followed your hospital’s work in paediatric cardiac surgery, especially the outreach camps you run in smaller towns. I have spent five years in a paediatric ward in a district hospital, and I have seen how many children arrive late for treatment. Working in a centre that treats these cases every day, and also goes out to find them, is exactly the kind of nursing I want to do. I can bring strong ward experience and fluency in Kannada and Telugu for your outreach teams.
-
Senior manager
Two things drew me here. First, you are moving from selling through distributors to selling directly to large institutions, and I have led exactly that shift at my current company, building a key accounts team from scratch. Second, your leadership talks openly about building processes before scaling, which matches how I work. I would not be learning the institutional sales model on the job; I can bring a playbook, hiring plan and pricing structure that have already worked, and adapt them to your products.
Common mistakes
- Giving generic praise like “reputed company” or “good work culture”.
- Talking only about what you will gain, such as salary, location or brand name.
- Getting basic facts about the company wrong.
- Reciting the “About us” page instead of linking it to yourself.
- Giving an answer you could use for any competitor.