Interview Sarthi
Home › Guides › Why should we hire you?
“Why should we hire you?”: evidence, not adjectives
The question sounds like it wants confidence. It actually wants proof. Here's the mapping method, with worked answers for freshers, experienced candidates and career switchers.
How to use these examples: These are our practice suggestions, not employer rules or guaranteed answers. Replace the situations, numbers and results with your own experience.
Most candidates hear “Why should we hire you?”, or “hum aapko kyun lein?”, as an invitation to describe themselves: hardworking, sincere, quick learner, team player. Every one of those words has been said in that chair a thousand times, and none of them can be checked. The interviewer isn't asking what you're like. They're asking a risk question: if we pick you, what's the evidence it works out?
The mapping method
Before the interview, open the job description and do this on paper:
- Pick the two or three requirements the role actually centres on. Not all ten bullet points, the two or three the team lives in daily. For a React role that's usually the framework, performance, and working with a backend team; the rest is filler.
- For each one, write your single best proof. A project, a number, a result, something that could survive a follow-up question. If you have no proof for a requirement, don't claim it; pick a different requirement.
- Close with one sentence of intent: why this role, now.
The shape of every good answer to this question: “The role needs X. I've done X, here's the number. It needs Y. Here's my Y. And I want this specific job because Z.” Requirement → proof, two or three times, then stop. You are making hiring you look like the low-risk choice, because that is what it decides.
Worked answers
Experienced (English)
“Three things the posting asks for are React, performance work, and coordinating with a backend team, and that's my current job, one size smaller. I own a dashboard used by 40,000 people, I took its load time from 3 seconds to 1.2 last quarter, and I've been the frontend voice in our API design meetings for two years. You need someone delivering from the first month. My track record is that I've shipped independently within 90 days at every company I've joined.”
Every claim has a number, and every number invites a follow-up on ground the candidate chose. No adjectives anywhere.
Experienced (Hinglish: if the interviewer switched first)
“Role mein jo teen cheezein likhi hain, React, performance, backend ke saath coordination, wahi main abhi daily karta hoon, bas chhote scale pe. 40k users ka dashboard mera hai, load time 3 se 1.2 second pe laaya pichle quarter. Aapko koi chahiye jo pehle mahine se deliver kare. Mera record hai ki har company mein 90 din ke andar independently ship kiya hai.”
Numbers and technical nouns in English, grammar in Hindi. The craft rules are in the Hinglish answer guide.
Fresher
“You're hiring for trajectory more than history at my level, so here's my evidence of it: my final-year project isn't a demo. My department actually runs it, 300 students use it daily, and I maintained it through two semesters of feature requests. That's the part of engineering no course teaches, keeping something alive after launch, and I've already done it once. Give me real tickets and I'll do it here.”
A fresher can't out-experience anyone, so the answer reframes what's being bought: learning speed and finishing power, with one verifiable exhibit. One finished thing beats ten listed skills.
Career switcher (e.g. support → testing, sales → product)
“Two reasons. The skills that transfer are the ones this role is short of. I've spent three years turning angry-customer tickets into exact reproduction steps, which is 80% of what good QA is. And the skills that don't transfer, I've been closing on my own time: 200+ hours of Selenium practice and a test suite on GitHub for a real open-source project. You get someone with the domain instincts of experience and the hunger of a fresher.”
Switchers win by naming the transfer honestly: what carries over, what didn't, and the proof they closed the gap themselves.
Three ways this answer dies
- The adjective list. “I'm hardworking and passionate” is unverifiable, so the interviewer discards it. If a claim has no number, project, or name attached, cut it.
- Answering with your whole resume. Two or three proofs, forty-five seconds. Picking your best evidence is the demonstration of judgment.
- Comparing yourself to other candidates. “I'm better than most people because…”, you don't know the other candidates, and it reads as insecurity. Sell your fit, not their shortfall.
One more thing: this question rarely arrives alone. It usually follows your self-introduction and precedes “why are you leaving?”, and the three answers must agree with each other. The introduction promises, this question proves, the leaving question explains the timing. Prepare them as one story, not three answers.
Practise these answers out loud
Prep Sarthi runs a voice AI mock interview from your CV and target role, asks follow-up questions and gives feedback on weak answers. Try a free 7-minute demo, with nothing to set up; a paid pass is ₹99 for 30 days.
Try a free AI mock interview
See how to practise from your resume. Still looking for a role? Apply Sarthi brings jobs from multiple sources together. For permitted assistance during a real call, see Live Sarthi.