Why should we hire you?

What the interviewer is actually asking

The question sounds like an invitation to boast. It works as a sorting question. By the time it arrives, the panel has heard similar claims from several people and needs one reason to move a name forward.

MIT’s career office lists it among its sample interview questions as “Why should I hire you?”, alongside the questions employers use to check whether you understand the role you applied for. That framing is useful. The answer is a short argument about fit, aimed at the problems named in the job advert, rather than a tour of your history.

There is also a reason it usually comes near the end. It hands you the last word. Whatever you say here is roughly what the interviewers will repeat to each other when they compare notes, so it should be the one sentence you most want remembered. Say it on purpose.

How to answer: claim, evidence, offer

A reliable answer has three moves.

First the claim. One sentence that names the two or three things the role needs most and states that you have them. Keep it concrete, in the employer’s own terms: “You need someone who can run the monthly close without supervision and bring two new starters up to speed, and that is the job I have been doing for three years.”

Then the evidence. For each thing you claimed, give one short proof: a result, a number, a piece of scope, a decision you made. This is where most answers dissolve into adjectives. “I’m a hard worker” proves nothing. “I covered the close on my own for four months while my manager was on parental leave” proves a great deal, and it cannot be copied by the next candidate.

Last the offer. Say what you would do with the job in your first weeks. It shifts the answer from your past to their future and shows you have pictured the work, not the title.

Sixty to ninety seconds covers all three comfortably. If you are running past two minutes, your evidence has turned into a story; trim it to one line per claim and save the full story for a behavioral question.

Build the answer from the job description

You cannot write this answer without the advert in front of you. Print it, then mark every requirement and sort the list into three piles: must-have, nice-to-have, and vague. The vague ones (“team player”, “fast-paced environment”) describe a culture rather than a skill, so they belong in your questions for the interviewer, not in your evidence.

Take the top three must-haves and write one line of proof under each from your own record. If a requirement shows up twice, once in the opening summary and again in the responsibilities, treat it as the thing the hiring manager worries about most, and lead with it.

Then do a little work on the company side. The National Careers Service suggests looking at an employer’s about us pages to find out more about their products, services and values. MIT’s interview primer puts it even more plainly: review their website, see what they are recently in the news for, or talk with current or former employees. One specific detail from that reading, attached to something you would contribute, is what separates your answer from the five interchangeable ones before it.

Keep this research light for now. You need one hook, not a dossier.

Sample answers by experience level

Adapt the shape, never the words. A borrowed answer sounds borrowed.

First job, little paid experience

You need someone who can take the first line of tenant queries and keep the records straight. Those are the two things I did every day last year, in a different setting.

I ran the front desk at my university sports centre for three terms, which meant around forty bookings and complaints a shift, plus a weekly reconciliation of the cash and card totals. Nobody had written the reconciliation down, so I documented it and trained the two students who replaced me.

In my first month I would learn your case system properly and then look at which queries come back twice, because repeat queries are usually a wording problem rather than a people problem.

Changing industry

The posting asks for someone who can turn messy operational data into something a manager will act on, and that has been my actual job for six years. The sector is new to me; the problem is not.

In clinical research I rebuilt a weekly recruitment report that three site managers had stopped opening. I sat with each of them, cut it from nine pages to one, and added the two figures they were calculating by hand. All three used it within a fortnight, and it became the standard report across eleven sites.

I would expect my first eight weeks here to be mostly listening: learning your product vocabulary, sitting with the account team, and holding off on changing any report until I understand who depends on it.

Experienced hire

You are hiring for two things at once: someone who can own the platform migration, and someone the engineers will actually follow. I have done both together, which is the harder part.

I led the move of a payments service off a shared database while the team kept shipping. We ran it in four slices over five months, with a rollback for each, and finished with no unplanned downtime. Two of my engineers have since been promoted, which I count as part of the result.

If you hire me, my first thirty days would go on a written migration plan with explicit risks, agreed with your security lead before any code moves.

Customer service

You want someone who keeps a calm queue on a bad day and leaves good notes behind. That is the habit I have built over four years on a support desk.

Our team handled a product recall with the phone queue at triple its normal depth. I drafted the three answers we kept repeating, shared them on the team channel, and took the escalations myself so the newer agents could keep the basic calls moving. Our complaint rate for the week came in below the previous recall.

Here, I would spend the first weeks learning your refund rules properly, because confident answers on the phone come from knowing exactly where the limits sit.

Answers that fall flat

The flattest answer is pure self-description: passionate, hard-working, detail-oriented, a people person. Every candidate says it, so it carries no information. If a sentence in your answer would be true of the person interviewed before you, cut it or add the proof that makes it yours.

The second is the needs-based answer. “Because I really need this job” and “it would be a great opportunity for me” both put your interests where the employer’s should be. Want for the role, not from it.

The third is the oversell: claiming you are the best candidate they will see. You have no idea who else applied, and the claim invites a test you cannot pass. State what you can do and let the comparison happen on its own.

The fourth is length. An answer that runs four minutes reads as nerves, and the strong opening line gets buried. Stop talking and let them follow up; the follow-up is usually where the offer is won.

Variations you may hear

The same question arrives in several costumes. “Why should we employ you?”, “What makes you the right person for this role?”, “Why you and not the other candidates?” and “Give me three reasons to hire you” all take the claim, evidence, offer answer with no real change.

“Why should we pick you over someone with more experience?” is the comparison version. Answer it by naming what you do have that the job needs, then the one thing you would do to close the gap faster, such as a certification already in progress or a specific tool you learned in your own time.

Some interviewers invert it: “Why should we not hire you?” or “Who would be a better fit than you?” Keep it honest and short. Name a genuine limit of your profile, say how you manage it, and stop. The invitation is to show self-awareness, not to argue yourself out of the job, and the same restraint applies to the standard weaknesses question.

If the interviewer instead asks why you want the job, the focus moves from your evidence to their organisation, which is a different answer; that one is covered on the page about why you want to work here.

When you do not meet every requirement

Almost nobody matches a long advert in full, and hiring managers know it. What they are listening for is whether you know which requirements you miss and whether you are straight about it.

Pick the gap that matters most, name it once, and move immediately to the nearest thing you have done. Two years of reporting in a related tool, a course you finished last spring, a project where you picked up an unfamiliar system in a fortnight: all of it counts as evidence that you close gaps.

Do not volunteer three gaps. One honest acknowledgement reads as confidence; a list reads as a withdrawal. And never guess at a tool you have never opened, because the question after that one is always more specific.