"Why should we hire you?" — how to build a strong answer

A shortlist is a set of trade-offs. Every candidate on it is strong somewhere and thin somewhere, and the interviewer is choosing which gap they are most willing to live with.

So the useful preparation is not "what am I good at?" It is what is the risk in this hire, and which version of that risk am I?

Read the job advert again and find the requirement that is repeated, listed first, or described in unusual detail. That is almost always the thing keeping the hiring manager awake. Then ask:

• Am I strong on that, while a typical candidate for this role is not? → Lead with it.
• Am I adequate on it but exceptional elsewhere? → Acknowledge it briefly, then move to what is genuinely differentiating.
• Am I weak on it? → Your answer is about how quickly you close it and what you bring that offsets it. Do not pretend.

Around sixty to ninety seconds.

1. The match, stated once. One sentence connecting your core capability to their central requirement. No list.

2. The evidence. One specific occasion, with a result. This is the body of the answer and where most candidates go abstract.

3. The differentiator. The combination that is actually rare. Rarely a single skill — usually an intersection: this function plus that sector, this technical depth plus that stakeholder exposure, this scale plus that stage of growth.

Then stop. A fourth point weakens the first three.

Most people answer this badly because they look for something they are best at. That is the wrong search. You are looking for a combination that is uncommon in the candidate pool for this specific role.

Ask yourself:

The intersection is normally the answer. "A finance background" is common. "A finance background and four years running the commercial relationship with the regulator" is not, and the second one is decisive if the role sits between those two worlds.

Row 7 is not said out loud. It exists so you know where not to overreach, because an inflated claim in this answer invites the follow-up that dismantles it.

Strong

"The thing this role seems to hinge on is getting the commercial and technical teams to agree a specification without a six-month delay, and that is most of what I have done for four years.

At my current company the product and engineering teams had stalled on a platform spec for nine months. I ran it as a structured trade-off exercise rather than a series of meetings — we agreed the three things we would not compromise on, then let everything else be decided by cost. Spec was signed in seven weeks.

What I think is less common is that I have worked as an engineer and I have carried a revenue target. Most people in this role have one side or the other. When the technical team says something is impossible and the commercial team says it is essential, I can usually tell which one is right."

Why it works: it names the employer's actual problem, proves the capability once with a number, and closes on an intersection rather than a superlative. It also does not claim to be the best candidate — it claims something specific and checkable.

Weak

"I believe I'm the best candidate because I'm hard-working, I learn quickly, and I'm very passionate about this industry. I've got five years of experience and I'm confident I'd be a great fit for the team. I always go the extra mile and I'm a strong team player."

Nothing here is false and none of it is usable. No requirement, no evidence, no differentiation, and five phrases that the other three candidates will also say.

Both examples are constructed. The company, the project and the figures are invented.

13–16: ready. 8–12: almost always criterion 5. Read your answer and ask which parts a competitor could also say, then cut them. Below 8: you are answering "am I suitable?" rather than "why me?" Rebuild from row 1 of the worksheet.

"Why are you the best candidate?" Do not accept the framing. You cannot know who else applied. Answer with what you specifically bring, not with a comparison you have no basis for.

"What makes you different from other applicants?" The same answer, and the framing is more honest.

"Sell yourself to me." Same answer, delivered without changing register. Candidates who hear "sell" often become louder rather than more specific, which makes the answer worse.

"Why should we hire you over someone already doing this job elsewhere?" Harder and increasingly common. The honest structure: what an internal-market hire brings, what you bring instead, and why the second matters more here. Do not disparage the hypothetical person.

Asked as the final question. Common, and it is your closing argument. Keep it to sixty seconds and end cleanly — do not trail off into a summary of the whole interview.

Comparative self-advocacy can feel immodest, and candidates often soften this answer until nothing is left of it. The way through is the same as elsewhere: describe the work and the combination, not your own excellence. "I have worked as an engineer and carried a revenue target" is a fact about a career. The interviewer draws the conclusion.

On a panel, the answer is usually being scored, sometimes against a written form. That rewards a clear structure — requirement, evidence, differentiator — over a warm and general answer. A scorer needs something to write in the box.

If the interview runs in your second language, this is a good answer to have rehearsed rather than improvised, because it depends on precision and precision is the first thing to go under pressure. English interviews for Arabic speakers covers what to do about that.

Is it arrogant to answer this directly?

No. They asked. A vague answer is not modest, it is unhelpful, and it makes the assessor's job harder.

What if I genuinely do not think I am the strongest candidate?

You do not have to believe that to answer well. Give them what you actually bring and let them decide. "I am not sure I am the strongest" is not humility — it is asking them to do your job.

What if I am changing fields?

Lead with the transferable capability and name the intersection, which is usually stronger for a career changer than for anyone else in the room. Career shift covers how to work out what transfers.

What if I am underqualified on paper?

Name what you are strong at, state the gap once in a clause, and say how you would close it. Do not spend the answer on the gap — you were shortlisted, which means they already decided it was survivable.

Should I mention salary flexibility here?

No. It converts a capability argument into a price argument and signals you have nothing better. Salary belongs in its own answer.

Do the worksheet, especially rows 2 and 5 — the risk they are carrying and your intersection. Those two are the answer; everything else is delivery.

Then: the interview question hub for the other question types, and "why do you want to work here", which is the mirror of this one and usually asked in the same interview.

If you can write a strong answer and cannot tell how it sounds, that is the gap a mock interview closes — or work through it in the self-paced interview preparation course.