By the end of this guide you will have a 60-second answer to "Why should we hire you?" that is built from the job posting, backed by two or three results you can actually point to, and short enough to leave room for follow-up questions.
You will also get five worked examples — a new graduate, a step up, an industry switch, a career change and a return after a gap — plus the mistakes that make strong candidates sound generic.
Why interviewers ask it
Three competencies are on trial here, and none of them is likeability.
The first is judgement about the role: can you read a job description, work out which two or three requirements actually matter, and speak to those instead of everything you have ever done. The second is evidence and self-appraisal: whether you can support a claim about yourself with a specific piece of work, its scope and its outcome, rather than a list of adjectives. Indeed says employers ask the question to learn what differentiates you from other candidates and to see how you handle difficult situations (Indeed, 4 May 2026).
The third is fit and persuasion under mild pressure. The question is uncomfortable by design. Interviewers want to see whether you can advocate for yourself without inflating or apologising, and whether the way you describe your work sounds like the way their team works.
Other ways you'll hear it
"What makes you the strongest candidate for this role?"
"Why are you the right fit for this job?"
"What sets you apart from the other people we're seeing?"
"What would you bring to this team that we don't already have?"
"Give me three reasons we should offer you the job."
"Before we finish — is there anything else you want us to know before we decide?"
How to build your answer
Use the MATCH method. It gives you five building blocks and one rehearsal rule, and it maps onto the preparation Indeed recommends: study the job posting, research the company, tie your background to the posting, quantify your accomplishments and consider what sets you apart (Indeed, 4 May 2026).
Map the posting. Print or paste the job description and mark the requirements that appear first, appear twice, or are written in unusual detail. Those are the ones the hiring manager argued about internally. Aim for three. Everything else is noise for the purposes of this answer, and trying to cover it all is what makes people ramble.
Audit your evidence. Against each marked requirement, write one thing you have done: the setting, the size of it, what you changed and how you know. "Handled invoices" is not evidence. "Owned the supplier master file for three sites and rewrote the set-up rules" is. Quantify where you honestly can — Indeed's guidance treats measurable accomplishments as a feature of a strong answer — and where you cannot count something, describe scope instead.
Trim to two or three proof points. More than three and nothing sticks. Choose the pairs where your evidence is strongest and most recent, and make sure one of them is the thing that genuinely sets you apart from people with the same job title: a specialism, a system, a sector, a scale, a language, a mess you have cleaned up before.
Connect it to the company. Add one sentence that shows you know what they are dealing with — a stage of growth, a migration, a new site, a regulator, a service standard they publish. This is the sentence that stops your answer working equally well for their competitor.
Close and hand it back. Finish with a short forward-looking line and an invitation: which of these would be most useful to go into? That keeps you inside a minute and turns your answer into a conversation rather than a speech.
Rehearse the beats, not the wording. Say it out loud four or five times, changing the phrasing each time, so you remember the three points and not a paragraph. Indeed warns that memorising an answer word for word can make you come across as robotic or inauthentic in the interview (Indeed, 4 May 2026).
Example answers
New graduate
Amara, environmental science graduate, applying for a junior data analyst role at a regional water utility
Your posting puts sensor data cleaning and reporting to non-technical managers at the top, and that is most of what my final-year project was. I worked with a river trust on two years of logger data — roughly 40,000 readings — wrote the cleaning scripts myself, and rebuilt their monthly report so the trustees could read it without me in the room. They still use that template. Alongside my degree I spent 18 months as a part-time lab assistant, which taught me sample chain-of-custody and why a badly labelled bottle costs a week. So you would get someone who already knows what messy environmental data looks like and can explain it to people who care about the outcome, not the method. I will need support on your reporting stack. I picked up a new language in a fortnight for that project, so I am not worried about the tooling.
Step up in the same field
Dan, senior payroll administrator applying to lead a payroll team of six
Three reasons. First, I already do part of this job informally — I have been the escalation point for our two newest administrators for a year, I wrote their onboarding checklist, and neither has missed a run. Second, I know where this role goes wrong. Our last system transition slipped because nobody owned the parallel run calendar, so I would arrive with a week-one plan for that instead of discovering it in month three. Third, scope: I run a monthly payroll for just over 900 staff across three entities, including term-time-only contracts, which is the closest thing I have seen to your mix. What I have not done is take a formal review cycle end to end, and I would want your HR partner alongside me the first time. The statutory deadlines and the awkward conversations about underpayments I have handled for eight years.
Industry switch
Priya, shift supervisor moving from food distribution into a pharmaceutical warehouse
The obvious objection is that I have moved pallets of yoghurt, not medicines, so let me deal with it. My site was temperature-controlled and audited twice a year, and I owned the cold-chain deviation log for a 60-person shift: every excursion, who signed it off, what changed afterwards. Over two years we went from the worst deviation record in the network to the site our regional manager used as the example. I also ran the night handover, which is where our stock discrepancies used to appear, and cut them by about two-thirds by making the count physical instead of paper. Your documentation standard is stricter than mine and I expect to be retrained on it. What you will not have to teach me is why the paperwork matters when someone is tired at three in the morning and the freezer alarm goes off.
Career change
Joe, secondary school teacher applying for a learning and development coordinator role
Earlier you said the real problem is that new-starter training gets built, delivered once and then never updated. That is the part of teaching I have been doing for eleven years. I have rewritten the same scheme of work four times because the intake changed, and I have the assessment data that shows which version landed. Concretely: I designed and ran the department's literacy intervention for 120 students, trained six colleagues to deliver it, and wrote it so that a cover teacher could pick it up cold. That is course design, facilitation and train-the-trainer under different names. I am new to your authoring tool and to talking about training in cost terms — I have started an online course to close the first of those. What you get on day one is somebody who can stand in front of a sceptical room and hold it.
Returning after a gap
Ruth, returning to accounts payable after two years of caring for a parent
I will take the gap first: I stepped out for two years to care for my father, that has come to an end, and I am available full time from the start of next month. Before that I spent nine years in accounts payable, the last four as the person who cleaned up the supplier master file after two mergers — around 4,000 records, duplicates and all — and it stayed clean because I wrote the rules for adding a new supplier. You mentioned you are halfway through a similar consolidation. I have already made those mistakes once, and I would rather you did not repeat them. During the gap I kept my bookkeeping qualification current and did the books for my brother's two-van business, so I am not coming back cold on VAT returns or cloud systems. What I would want in week one is a walkthrough of your approval hierarchy.
Mistakes to avoid
Mistake
Fix
Walking through your CV in date order until the interviewer stops you
Pick the two or three requirements that matter most in the posting and give one piece of evidence for each
Listing adjectives — hard-working, passionate, a real team player — with nothing behind them
Attach every trait to a specific thing you did, with its scope and its result
Claiming you are better than the other candidates, whom you have never met
Talk about the requirements of the job, not about rivals you know nothing about
Making the answer about what the job would do for your career
Lead with what the employer gets; save your own motivation for "why do you want this role?"
Delivering a script you learned by heart, in a flat voice, and losing your place when interrupted
Rehearse three points out loud in different words each time — memorising word for word can make you sound robotic or inauthentic (Indeed, 4 May 2026)
Opening with a hedge: I know I don't have all the experience, but…
Name the single real gap once, in one sentence, with how you are closing it — then stop apologising
Talking for three minutes and drying up mid-sentence
End on a deliberate closing line and offer to expand on whichever point is most useful
Your answer checklist
Two or three proof points, each tied to a requirement in the posting — not a full career summary.
A measurable or scoped result in at least one of them — a number, a size, a before and after. Indeed's guidance treats measurable accomplishments as a feature of a strong answer (Indeed, 4 May 2026).
One differentiator — the specialism, sector, system or scale that people with your job title usually do not have.
One sentence that could only apply to this employer — their migration, their site, their service standard, the problem the interviewer named earlier.
A clean finish under about 90 seconds, ending with an offer to go deeper on any of it.
Frequently asked questions
When in the process will I be asked this?
Assume it could come at any point. Indeed notes that the question can be asked at any stage of the interview process, from the pre-screen call through to final-round interviews (Indeed, 4 May 2026). In practice it often appears in two places: early in a screening call, where a recruiter is checking you can summarise your fit in 30 seconds, and right at the end of a panel interview, where it functions as your closing statement. Prepare both lengths — a two-sentence version and a 60-to-90-second version — and decide in the moment which one the situation calls for.
How long should the answer be?
Aim for 45 to 90 seconds, which is roughly 120 to 180 words spoken at a normal pace. That is enough for two or three proof points and a closing line, and short enough that the interviewer can follow up. If you are on a phone screen, halve it. If you genuinely have more to say, say the short version and add: I can go into any of those in more detail — which would be most useful? Running past two minutes is the most common way a good answer stops working.
What follow-up questions usually come next?
Expect the interviewer to test the weakest part of what you just said. Common follow-ups: what would you do in your first 90 days; which of those results are you proudest of and what exactly was your part in it; where would you need the most support; and, if you mentioned a gap in your experience, how would you close it. Some interviewers will also push directly — what makes you a better fit than someone who has already done this job? Answer that with the requirement and your evidence, not with a comparison to candidates you have not met.
What if I'm asked at the very end and I've already covered everything?
Do not repeat the interview back to them. Treat it as a closing statement and do two things. First, pick the single most important reason and say it in one sentence. Second, address any doubt that surfaced during the conversation — if they queried your experience with a particular system or your lack of management responsibility, name it and say how you would handle it. Finish by confirming something practical, such as your availability or your interest in the next step. That is a stronger ending than a summary nobody needs.
Sources
IndeedInterview Q&A: "Why Should We Hire You?" (4 Sample Answers)2026-05-04