Why does "why should we hire you" get follow-up questions?
The why should we hire you answer makes two claims at once: what the employer needs and what you have done about it before. Follow-up questions test both claims. Saint Mary's University of Minnesota calls "Why should we hire you?" a traditional question and says behavioral interviewing "is much more probing and works very differently" (Saint Mary's University of Minnesota).
Many interviewers now bring that probing to the traditional question. The U.S. Office of Personnel Management defines a probe as "a question asked by the interviewer to help clarify a candidate's response or ensure the candidate has provided enough information" (OPM interview guide). A pitch for yourself rarely carries enough information on its own, so the probes arrive fast.
This page assumes you have the first answer. The guide to answering why should we hire you covers the structure (their problem, your evidence, the gap you close) and two follow-ups: what the strongest other candidate would have, and the example behind any adjective you use. The six below come after those.
Which follow-ups does a why-should-we-hire-you answer invite?
A why-should-we-hire-you answer invites follow-ups on your reading of the role, your share of the result you cited, how that result was measured, whether it would transfer, what you would need to learn and what could go wrong. The table pairs each with what it tests and the reply that usually falls short.
| Follow-up | What it tests | The reply that falls short |
|---|---|---|
| "How do you know that's what we need?" | Where your reading of the role came from | A guess from the job title |
| "Which part of that result was yours?" | Your share of a team result | "We" in every sentence |
| "How was that number measured?" | Whether the figure has a baseline and a source | A number nobody tracked |
| "Would that work here?" | Whether you see how this setting differs | An answer that treats both places as the same |
| "What would you need to learn first?" | Whether you know your gaps for this job | "Nothing, I'd be ready on day one" |
| "What's the risk in hiring you?" | Whether you can name a real downside | A strength presented as a risk |
The list comes from probes that OPM and Canada's Public Service Commission publish for interviewers, applied to this one question. No survey of interviews sits behind it, and the order says nothing about frequency.
What does "how do you know that's what we need" check?
Asking how you know what the team needs tests where your reading of the role came from. Microsoft tells candidates to "review the job description to identify the skills most relevant to the role" (Microsoft Careers). An interviewer who hears you name their problem wants the source: the posting, a past round or their product.
A reading built on the job title alone falls apart here. Point to the evidence and say how sure you are. If your guess was wrong, the interviewer will often correct it, and that correction is useful for the rest of the interview.
Example reply to "How do you know that's what we need?": Two things. The posting lists month-end close three times, and in the first round your controller said close takes nine working days. I may be wrong about the cause, so tell me if it's something else.
What does "which part of that result was yours" check?
Asking which part of a result was yours separates your work from the team's. Canada's Public Service Commission lists "What was your role?" among the sample probes it gives hiring boards (Public Service Commission of Canada). A why-should-we-hire-you answer usually cites one result, and this probe asks for your slice of it.
The reply falls short when "we" carries every sentence. Name the decision you made, the work you did with your own hands and the parts other people owned. A smaller share stated plainly is worth more than a whole result you can't account for.
Example reply to "Which part was yours?": The reconciliation template was mine, and I trained the two clerks on it. The controller made the call to move close to a fixed calendar. The cut from nine days to six came from both changes together.
How do you answer "how was that number measured"?
Answering how a number was measured means giving the baseline, the end point and who tracked it. Google's re:Work guide says follow-up questions "help elicit a high level of detail from the candidate" (Google re:Work). A figure in your pitch is the detail most likely to draw that kind of question.
The reply falls short when the figure has no starting point or no source. "We cut errors by half" invites the question "half of what?" Give both numbers, the period they cover and where the data lived. If the figure is your own estimate, say so before the interviewer asks.
Example reply to "How was that measured?": We counted invoices sent back by clients for errors. It was 42 in the first quarter of 2025 and 19 in the first quarter of 2026. The count came from our ticket system, and I pulled it myself for the quarterly review.
What does "would that work here" check?
Asking whether your result would work here tests whether you can see how this employer differs from your last one. OPM's sample situational probes include "What factors would affect your course of action?" (OPM interview guide). Size, tools, regulation and who signs off are the usual factors that change the answer.
The reply falls short when it treats both workplaces as the same. Name one thing that would carry over and one thing you would expect to change. Then say how you'd find out in your first weeks, such as which person you'd ask or which report you'd read.
Example reply to "Would that work here?": The fixed close calendar would carry over. The template probably wouldn't as is, because you run three entities and we ran one. I'd want to sit with whoever runs the intercompany entries before changing anything.
What does "what would you need to learn first" check?
Asking what you would need to learn first tests whether you know your gaps for this particular job. Microsoft tells candidates "We don't expect you to know everything" (Microsoft Careers), and Amazon's Learn and Be Curious principle says leaders "are never done learning and always seek to improve themselves" (Amazon).
The reply falls short at "nothing." Every new job has a system, a product or a rule set you haven't used. Name the gap, say how big it is and say what you've done about it already. A gap with a plan reads as self-awareness.
Example reply to "What would you need to learn first?": Your ERP. I've used two others but never this one. I've done the vendor's free introductory course, and I'd expect to need about a month of close cycles before I'm as quick as I was.
How do you answer "what's the risk in hiring you"?
Answering what the risk is in hiring you means naming a real downside and what limits it. Amazon's Earn Trust principle says leaders "are vocally self-critical, even when doing so is awkward or embarrassing" (Amazon). This follow-up asks for that kind of self-criticism about your fit for the role.
The question differs from the strongest-other-candidate follow-up in the main guide. That one compares you with someone else, while this one asks about you alone. The reply falls short when the risk is a strength in disguise, like "I care too much," which is the same trap as in the greatest weakness follow-ups. Name the risk and the limit together.
Example reply to "What's the risk in hiring you?": I haven't managed anyone yet, and this role leads one analyst from month six. I've mentored two interns, which helps, but I'd want a check-in with you on that after the first quarter.
How do you prepare for the why-should-we-hire-you follow-ups?
Preparing for the why-should-we-hire-you follow-ups means writing six short notes before the interview. Note where your reading of the role came from, your share of the result, the baseline and end point of your number, one thing that transfers and one that doesn't, your main gap with its plan, and the risk in hiring you with its limit.
Check each note against your first answer, because a follow-up that contradicts the pitch costs more than a weak pitch. The free job match tool checks every requirement in a posting against your resume and gives a score out of 10, which shows where your gaps are. The interview questions tool lists likely questions for the round you pick.
The same approach covers other openers. See the follow-ups after why do you want to work here, after tell me about yourself and after where do you see yourself in 5 years. For the stories behind your evidence, the STAR method guide covers structure.
To say the pitch and its follow-ups out loud, the Prept Mock room asks questions on a clock and scores each answer out of 10 against your resume. It's part of the free plan.