Why Should We Hire You?

What they are actually asking

They are not asking you to summarise your CV. They have read it. They are asking whether you understand what is broken well enough to say, specifically, what you would fix.

Almost every weak answer to this question is grammatically about the candidate. I am hardworking, I am a fast learner, I have five years of experience in this field. Every strong answer is grammatically about the employer. You are trying to do X, the hard part of X is Y, and I have done Y twice.

That flip is the whole thing. It is also why this question is harder than it looks, because answering it properly requires you to have worked out what the job is for, which the job description usually does not tell you.

The good news is that the interview itself hands you most of the material. By the time this question arrives, forty minutes have been spent describing the team, the problems and the things that have not worked. A candidate who has been listening can name their problem in the employer's own words, which is a much stronger opening than anything preparable in advance.

The structure

Three sentences, in this order. Sixty to ninety seconds total.

Their problem. What you think the role exists to solve, said plainly. You are hiring a second support lead because the queue has outgrown one person and the process was built for a smaller team.

Your evidence. The closest thing you have actually done, with a number. I took first response from eleven hours to three and a half at a company that had the same problem at the same size.

The gap you close. What specifically you bring that the alternative does not. This is where most people either overreach or go vague, and where being narrow is much stronger than being broad.

Narrow sounds like: I would rather spend the first month in the tickets than in a spreadsheet. Broad sounds like: I bring a unique combination of technical and interpersonal skills. The first is a claim somebody could disagree with, which is what makes it worth saying. The second cannot be disagreed with, which is why it carries no information.

Then stop. Do not add a closing line about being passionate.

Sample answer: experienced hire

From the conversation, the problem is that support has outgrown one person and the process was designed when the team was half this size. I have done exactly that transition once. At my last company I took first response from eleven hours to about three and a half, and most of that came from fixing routing rather than adding headcount, which I think is your constraint too. What I would bring that somebody more senior might not is that I am still close enough to the queue to see where it actually breaks, and I would rather spend the first month in the tickets than in a spreadsheet.

It names their problem first, offers one number, and the last sentence makes a genuine trade-off rather than claiming to be best at everything. Saying that somebody more senior might have something he does not is the line that makes the rest credible, because it demonstrates he has actually thought about the alternatives rather than about himself.

Sample answer: fresh graduate

You are hiring a graduate for this role rather than somebody with three years, which I read as wanting somebody who will learn your way of doing things rather than import someone else's. What I can point to is that I have done the learning-fast thing under pressure: I took over the events budget at my student union six weeks before our careers fair, with sixty employers booked and four thousand pounds I had to account for line by line. I would not claim experience I do not have. What I would claim is that I have been dropped into something unfamiliar with a deadline attached and it went fine.

Graduates lose this question by competing on experience they do not have. This one names the reason a graduate was wanted in the first place and answers that instead.

The refusal to overclaim is doing real work here. I would not claim experience I do not have is a sentence most candidates are afraid of, and it buys more credibility than any amount of enthusiasm, because it signals that the claims which follow are calibrated.

Sample answer: career changer

The obvious argument against me is that I have six years of teaching and eighteen months in instructional design, and you could hire somebody with six years in the field. What you would get instead is somebody who spent six years finding out in real time whether an explanation landed, in front of thirty people who showed it immediately. Most instructional design gets tested after it ships, if at all. I test explanations on people before they go out, and I do it because the alternative was unbearable for six years.

Naming the objection first is the strongest available move for a career changer. It removes the thing the interviewer was silently weighing and replaces it with your framing.

It also changes what the rest of the conversation is about. An unstated objection sits there for the whole interview and gets resolved in the write-up afterwards, where you cannot influence it. A stated one gets discussed in the room, and discussion is where you have an advantage, because you have thought about this trade-off far longer than they have.

What not to say

A list of adjectives. Hardworking, passionate, detail-oriented, quick learner. Every candidate says these, nobody is disbelieved, and nobody is distinguished. They cost you the sixty seconds you had.

Anything about how much you want it. Wanting the job is assumed by the fact that you applied. The question is what happens after you get it.

A summary of your CV. They have it in front of them. Repeating it signals you did not understand the question, which is a worse outcome than a mediocre answer.

Comparisons to named competitors for the role. You do not know who else applied, and speculating reads badly. Talk about dimensions rather than people.

Anything you cannot evidence in the next ninety seconds. If you say you are a fast learner, the interviewer is entitled to ask when. Have the example ready or drop the claim.

Where this answer breaks

The follow-up is almost always the same, and it is brutal in a useful way:

What would the strongest other candidate have that you do not?

An answer built on your own qualities has nowhere to go here, because it never considered anybody else. Candidates freeze, or they deflect with something about not being able to speak to other people's backgrounds, which reads as evasion.

An answer built on their problem handles it easily, because you already framed yourself as one option among several. More experience. Deeper domain knowledge. A track record at a bigger scale. Say the true thing, then say why the trade still favours you, or concede that it might not on that dimension and name the one where it does.

Conceding a dimension is safer than it feels. Interviewers are comparing real candidates against each other, so they already know what the alternatives look like, and a candidate who pretends there are no trade-offs is either unaware or performing. Naming the one you lose on costs you almost nothing and makes the one you win on believable.

The second break is subtler. If your answer contains a claim like I am a fast learner, expect the interviewer to ask for the example, and expect it to be the last thing they take from the conversation if you cannot produce one. Every adjective in this answer is a promissory note. Do not write cheques you cannot cash in the following ninety seconds.

The fix for both is to build the answer out of one thing you did, rather than three things you are. A single specific example with a number survives interrogation. A list of qualities invites it.

There is a useful test before you walk in. Read your answer and ask whether a different candidate, with a different background, applying for a different job, could say the same sentences. If they could, you have written a reference for yourself rather than an argument for this role, and the interviewer will hear exactly that.

Related

The opener that sets this up is covered in tell me about yourself, and the evidence you draw on here comes from the same stories you prepare for behavioral interview questions. For structuring those stories, see the STAR method.