This question tends to unsettle candidates more than it should, because it feels like it’s asking for a sales pitch, and most professionals aren’t comfortable selling themselves. But the discomfort usually comes from misunderstanding what the question is asking for. It isn’t asking you to be boastful or to claim superiority over unnamed other candidates. It’s asking you to do something much more specific: connect your actual, evidenced strengths directly to what this particular role needs, in a way you haven’t already done earlier in the conversation.
The candidates who answer this well aren’t more talented than the ones who fumble it. They’ve simply done the preparation work of identifying, in advance, exactly which two or three things about their background map most directly onto this specific job — and they have concrete evidence ready for each one. The ones who struggle are improvising in the moment, which almost always produces a vaguer, more generic answer than they’re capable of.
The real problem: treating this as a repeat of “tell me about yourself”
Candidates frequently give nearly identical answers to “tell me about yourself” and “why should we hire you,” just phrased slightly differently. This is a missed opportunity, because the two questions are asking for different things. The first establishes who you are broadly. The second asks you to make a direct, comparative case for this specific role — the differentiation the first question doesn’t require.
If your answer to “why should we hire you” could be given verbatim in response to “tell me about yourself,” it’s not doing the specific job this question is asking for. The fix is to treat this as its own distinct preparation task, built directly from the job description in front of you, not a recycled version of your general introduction.
The three-part structure that builds a real case
Identify the role’s top 2-3 requirements
- Re-read the job description and highlight the requirements mentioned most prominently or repeated across multiple sections.
- Distinguish between “nice to have” and “clearly critical” — your answer should focus on the critical ones.
- If the requirements are unclear from the posting, use anything said earlier in the interview about what the team actually needs.
Match each requirement to specific, provable evidence
- For each top requirement, identify one specific achievement or project that proves you can deliver on it.
- Quantify wherever possible — a number is more provable and more memorable than a description.
- Choose evidence you haven’t already used elsewhere in the interview, to avoid sounding repetitive.
Close with a forward-looking, role-specific statement
- End by connecting your fit to what you’d actually do in this role, not just what you’ve done previously.
- Reference something specific about the team, product, or challenge this role addresses, if you know it.
- Avoid closing with a generic line like “I’m a hard worker who would fit in well” — it undoes the specificity you just built.
A real example: a mid-career marketer competing against more experienced candidates
A marketing manager with six years of experience was applying for a senior role typically filled by candidates with eight-plus years. Her original answer to “why should we hire you” leaned heavily on enthusiasm — “I’m really passionate about this space and I’d bring a lot of energy to the team” — which gave the interviewer nothing concrete to weigh against more experienced candidates.
We rebuilt her answer around the job description’s top two stated priorities: driving a new product launch and building a small team from scratch. She had direct, quantified evidence for both — a product launch she’d led that hit 120% of its first-quarter target, and a two-person team she’d hired and onboarded within her current role. Her closing line connected both directly to the specific product line the new company was about to launch. She got the offer, and the hiring manager told her recruiter the specificity of her answer was what tipped the decision in her favor over a more senior but less prepared candidate.
What to avoid
Avoid comparing yourself to other candidates you know nothing about — “I’m probably more driven than most people you’ll interview” reads as presumptuous rather than confident. Avoid restating your resume chronologically, which is the exact trap this question is designed to move you past. And avoid a purely enthusiasm-based answer with no evidence — energy and passion are appreciated, but they don’t substitute for a specific, provable case.
Self-check before your next interview
Frequently Asked Questions
Tell me about yourself is an open invitation to establish who you are and what you’ve done; why should we hire you is a direct request to make the case for this specific role over every other candidate in the process. The first can be somewhat general and still land well. The second fails badly if it stays general, because the interviewer is explicitly asking you to differentiate yourself, not summarise your background again. Treat them as two different questions requiring two different structures, even though candidates often default to repeating the same content for both.
You don’t need to know your competition to answer this well — the goal isn’t to compare yourself to unknown candidates but to make the strongest, most specific case for your own fit that you can. Focus on matching your evidenced strengths directly to the role’s stated requirements rather than trying to guess what others might lack. A specific, well-evidenced answer about your own fit is inherently more differentiating than a vague one, regardless of who else is in the room. Competing on specifics beats competing on assumptions about others.
No — this question is about fit and value, not compensation, and bringing up salary here muddies an answer that should be entirely focused on why you’re the right choice for the role. Compensation conversations belong in their own dedicated discussion, usually later in the process or with a recruiter directly. Mixing the two signals a misread of what the question is actually asking. Keep this answer entirely about capability and fit.
No — this reads as unprofessional and shifts the focus away from your own strengths, which is the opposite of what this answer should accomplish. Comparing yourself favorably to unnamed others, or criticising the company’s existing team, comes across as insecure rather than confident. The strongest answers make a case entirely on your own merits and specific fit for the role, without needing to diminish anyone else. Confidence is demonstrated through specificity, not comparison.
Sixty to ninety seconds is the right range — long enough to make a specific, evidenced case, short enough to respect the interviewer’s time and keep the conversation moving. A rushed fifteen-second answer usually means you haven’t prepared enough specifics, while a three-minute answer usually means you’re repeating content from earlier in the interview. Aim for two to three specific points, each with brief evidence, delivered at a natural pace. Practice this out loud with a timer rather than guessing at the length.
