Answer "why should we hire you?" with two or three specific claims, each backed by evidence from your record, each mapped to something the job description actually asks for. The formula: "You need X. I've done X — here's the proof." Never answer with adjectives like hardworking or passionate; answer with receipts.
"I'm a hard worker and a fast learner" is not an answer — it's a set of unverifiable claims every other candidate is also making. The interviewer can't rank candidates on adjectives, so answers built on them read as noise. What ranks candidates is evidence: things you shipped, numbers you moved, problems you were specifically trusted with.
The working structure is claim, then proof, then relevance: "You need someone who can run payments integrations — I led two of them end to end at my last company, including the bank-side certification — and your JD says that's the first-quarter priority for this role." One sentence of claim, one of proof, one connecting it to their need. Two or three of those blocks is a complete answer.
The question is really "why should we hire you for this job", so the raw material is the job description, not your proudest achievement. Before the interview, pull the three requirements the JD repeats or lists first — those are the hiring manager's real anxieties — and prepare one evidence block for each.
If you can't cover all three, cover two honestly and address the gap head-on: "I haven't run a team of that size yet, but I've led projects across three squads, which is the same coordination problem without the title." A candidate who names their own gap and reframes it credibly reads as more senior than one who pretends the gap isn't there.
Keep the answer under a minute. Longer answers dilute the strong claims with weak ones, and interviewers remember the weakest thing you said. Say your two or three blocks, close with one summarizing sentence — "so the short version is: the two hardest parts of this job are things I've already done" — and stop talking.
Resist the urge to compare yourself to other candidates. You don't know who they are, and "I'm probably more experienced than most people you're seeing" gambles your credibility on a guess. The comparison the interviewer cares about is between your record and the job's needs — make that one, and only that one.
Answering with personality adjectives — hardworking, passionate, team player — instead of evidence. Every candidate says those words, so they carry no ranking signal. Specific shipped work mapped to the job's stated needs is what separates answers.
Two or three, each as a claim backed by proof and tied to a requirement in the job description. One reason feels thin; five feels unfocused and buries your best material. Close with a single summarizing sentence and stop.
Cover the requirements you genuinely meet with evidence, then name the gap yourself and reframe it with adjacent experience. Acknowledging a gap credibly reads as senior; pretending it doesn't exist reads as either unaware or evasive.
Your strongest evidence blocks should already be bullets on your resume — score it free to check the proof is visible before you say it out loud.
