“Why should we hire you” pe kya bolun, bina over-smart lage?
How to answer “Why should we hire you?”
This question feels like a trap. Say too little and you sound unsure of yourself. Say too much and you sound arrogant. Most candidates land on a safe, forgettable middle: “Because I am hardworking and a quick learner.”
There is a better way. Treat it as a short summary of the match between what they need and what you bring. You are not boasting. You are helping them make the decision.
Practise it now: 15 seconds to think, 60 to speak →
Try it now
Pick one. You get a prompt and a timer.
Talk to a random prompt. 15 seconds to think, 60 to speak.
Why interviewers ask it
Interviewers ask this near the end, when they are already forming a view. They want to hear whether you understand the role, and whether you can make a clear case for yourself without being pushed.
It is also a communication test. In most jobs you will need to argue for an idea, a budget or a deadline. If you cannot argue for yourself for sixty seconds, that is a signal.
Finally, it reveals whether you listened. The best answers pick up something the interviewer said earlier in the conversation, such as “you mentioned the team is moving to automation”, and connect it to your experience.
A simple structure: Match, Proof, Promise
Match
Name the one or two things this role needs most. Use words from the job description or from what the interviewer told you.
Proof
One short example that shows you already do those things. Specific and, if possible, with a result.
Promise
What you will do in the first few months. Keep it realistic and tied to their needs.
Do not compare yourself to other candidates. You have not met them, and it sounds insecure.
Sample answers for freshers
“From what you described, this role needs someone who can work with field sales teams and turn what they see into reports the leadership team can act on. During my MBA summer internship at an FMCG company, I travelled with sales reps across twelve towns in Madhya Pradesh and built a simple weekly dashboard of stock-outs that the regional manager started using in his reviews. So I have done a small version of this job already, and I enjoyed it. In the first three months I would want to spend as much time in the field as possible, so that the reports I build are based on how things really work.”
Why it works: Uses the interviewer’s own description, then one concrete piece of proof.
“This role is about fixing problems for customers who are often frustrated and not technical. I have two things that fit. First, I’ve been the unofficial IT support for my whole college hostel for three years, from Wi-Fi issues to laptops that wouldn’t boot, so I’m used to explaining technical things simply to stressed people. Second, I completed the Google IT Support certificate last year, so I have the basics covered properly. I learn fast when I’m solving real problems, and I’d expect to handle most common tickets on my own within the first month.”
Why it works: Turns informal experience into credible proof, and the promise is measurable.
Sample answer for experienced professionals
“You told me the biggest problem right now is renewals: customers sign up, but too many don’t come back after year one. That’s exactly what I’ve worked on for the last three years. At my current company I took over a portfolio of sixty mid-size accounts with a renewal rate that was falling, and by setting up quarterly business reviews and a simple health score, we brought it back up over eighteen months. I’d bring that same approach here. In the first ninety days I would talk to your ten biggest accounts and build an early warning list, so we see churn coming instead of hearing about it at renewal time.”
Why it works: Starts from their problem, not from the candidate’s CV.
Use these for the shape, not the words. An answer in your own words, about your own work, always beats a memorised one.
5 common mistakes
Generic adjectives
“Hardworking, honest, dedicated.” They cannot check any of it. One example beats ten adjectives.
Talking only about what you want
“This role will help me grow” is a reason for you to join, not for them to hire you.
Being too humble
“I’m not sure, but I’ll try my best” sounds like you don’t believe in yourself, so why should they?
Overclaiming
“I am the best candidate you will meet.” You don’t know that, and neither do they. Stay with the facts.
Ignoring the job description
If your answer could be given for any job at any company, it is too general. Mention something specific to this one.
Follow-up questions to expect
- “What makes you different from other candidates?”
- “What would you do in your first 90 days?”
- “What if you don’t get this role?”
- “Is there anything you are not good at that this role needs?”
How to practise this answer
- Before each interview, write down the two things the job description repeats most. Build your Match around those words.
- Practise the answer with the proof first and the claim second, then the other way round. Use whichever sounds more natural to you.
- Say it once in under 30 seconds. A short, sharp version is useful when the interviewer is running out of time.
Reading about an answer is not the same as saying it. Use the timer above, or come and do it in front of real people.
Questions people ask
How do I answer “Why should we hire you?” as a fresher with no experience?
Use projects, internships, college responsibilities or part-time work as proof. What matters is that you show you understand the role and have done something similar, even on a small scale.
Is it okay to say I am a fast learner?
Only with proof. Say what you learned quickly and how: “I picked up SQL in three weeks for my internship project and used it to clean their sales data.”
How long should my answer be?
About 45 to 75 seconds. Long enough for one piece of proof, short enough that it still feels like a confident summary.