“Why should we hire you?” is the question where qualified people talk themselves out of the offer. Not because they’re short on proof – because they try to show all of it at once.
So here’s the move: don’t prove everything. Pick the single thing this role needs most, then tell one specific story that shows you’ve already done it. One story, told well, beats a five-point list of everything you’ve ever touched.
Short answer to “why should we hire you”: name the one requirement that matters most for this role, then tell a single, specific story that proves you’ve already delivered it. Don’t recite your whole resume.
Why “Why Should We Hire You?” Trips Up Strong Candidates
Most people hear this question and treat it like a talent audition. So they dump every skill on the table, figuring that if they leave something out, they lose. But an interview isn’t an audition. It’s a risk decision.
The hiring manager isn’t hunting for the most impressive human in the pipeline. Instead, they’re hunting for the safest bet – the person who can do the actual job on day two without becoming their problem. A high ceiling with an unknown floor scares them. A proven floor gets the offer.
Here’s the thing: when you list ten strengths, you hand the interviewer a job. Now they have to figure out which of your ten things actually matters for their opening. Most won’t bother. So they remember the candidate who told them exactly why they were the safe choice, and they move that person forward. After coaching more than 250 mid-career tech professionals into their next role, I’ve watched this play out the same way every time – the candidate who picks beats the candidate who piles on. If you want the deeper version of this idea, it’s the whole point of becoming the obvious hire.
The Three Ways Candidates Blow the Answer
Nearly every weak answer to “why should we hire you” falls into one of three traps.
They prove everything. The pile-on: ten strengths, zero focus, and the interviewer’s attention gone by strength four.
The answer drifts to what you want, not what they need. “I want growth, I want a mission I believe in.” That’s why you want the job. It isn’t why they should hire you. You have to lead with their needs, not yours, which is exactly the reframe HBR recommends for this question.
Generic phrases fill the gap. “I’m a hard worker and a fast learner.” Think of the job description as the customer’s order. When you volunteer “fast learner,” you’re serving a dish they never asked for. They already handed you their order – it’s the posting – so answer it, and skip the phrases that quietly sink you.
How to Answer “Why Should We Hire You?” in Three Moves
Strong answers aren’t longer. They’re aimed. Here’s the three-move version.
Move one: find their number-one need. Read the job description like it’s their order, because it is. The first bullet, or the theme that repeats across the posting, is usually the thing they’re most afraid of getting wrong. That’s your target. If you can, confirm it early – ask what success looks like in the first six months, then aim there. Harvard’s own interview-prep guidance says the same thing: come in having researched exactly what the role and company need.
Move two: pick the one story that proves you’ve already done it. Not the story you’re proudest of. The one that maps to their top need. Because the whole point of this answer is to convince them you’ve already done this job somewhere else. So run the idiot check first: if they’d decide based only on this one story, is it the one you’d tell?
Move three: tell it so it sticks. Structure it as their-kind-of-problem, then what you did, then the result. Signpost the two or three moves you made so the interviewer can actually take notes, because what they write down is what they remember when they debrief. Then land on a number. It doesn’t have to be exact – it has to be directionally truthful and in the right ballpark. If your stories still feel thin, build them properly first.
What a Strong Answer Sounds Like
Say you’re a senior PM interviewing at a payments company, and the job description keeps circling one idea: bring order to a messy, over-promised roadmap.
Weak answer: “I’m a strategic product leader, I’m data-driven, I ship fast, I’m great with engineers, and I really care about the customer.”
Strong answer: “You’ve said the roadmap here has gotten hard to trust. In my last role, I inherited a roadmap with 40 committed features and a team that had missed three straight quarters. So I did two things. I killed the bottom half by outcome, not by who asked for it, and I rebuilt the top half around the one metric leadership actually cared about. Two quarters later we hit every date we set, and trust in the roadmap came back. That’s the problem you’re describing, and it’s the one I’ve already solved. What does the roadmap look like here right now?”
See the difference? The weak answer is a list. However, the strong answer names their fear, proves you’ve beaten it, and hands the conversation back with a question. That final move – the graceful handoff – tells them you’re finished and puts the ball back in their court.
Common Questions About Answering “Why Should We Hire You?”
What if several of my strengths fit the role? Pick the one tied to their biggest risk. Mention the others only if they ask. One clear reason to hire you beats five competing ones.
How long should the answer be? Sixty to ninety seconds. One story, signposted, with a number at the end. If you’re past two minutes, you’re circling the drain.
Isn’t betting on one story risky if I misread their top need? You’re not really guessing. The job description tells you, and you can confirm it by asking what success looks like early on. So aim at what they’ve told you they’re worried about.
What if I don’t have a perfect matching story? You don’t need a perfect match. Instead, you need enough overlap that they recognize the shape. Show the pieces you do share – the industry, the problem type, the scale – and let those carry it. Nobody’s a unicorn anyway. You just have to look enough like one.
What to do next
If you want a quick read on where your search is actually leaking – interviews, story, network, or offer – take the RHINO quiz. Five minutes, no email required.
If the storytelling piece is what you want to sharpen next, read Storytelling in Interviews: 7 Frameworks to Land the Job – it goes deep on structuring the story you just picked.
If you’d rather have someone map your actual interviews with you and tell you exactly what to fix first, book a free strategy call.