Why Should We Hire You? A Three-Part Answer, With Five Worked Examples

When an interviewer asks "why should we hire you," answer in three moves: name the two or three problems the role exists to solve, match each one with a specific piece of evidence from your own work, and finish with what you would do in your first weeks. Keep it under two minutes and leave the adjectives out.

That is the whole method. The rest of this guide explains why it works, how to find those problems before you walk in, and what the answer sounds like when you are a new graduate, a career changer, an experienced hire, an internal candidate, or someone who knows they are a little short of the requirements.

What the interviewer is actually testing

The question sounds like an invitation to sell yourself, and most candidates treat it as one. The interviewer is usually checking something narrower: whether you understood what this job is for, whether you can back a claim with evidence, and whether you see your own fit accurately, including where it is thinner.

It helps to think about what the interviewer does after you leave. They write notes, and later they have to justify a decision to someone else: a hiring committee, their own manager, a recruiter asking for feedback. "Seemed motivated and hard-working" is a note that justifies nothing. "Has already run month-end close for a company our size, and spotted that our real problem is the handoff from sales" is a note that gets someone hired. Your answer is, in practice, the draft of that note.

Three things are being read at once:

• Fit to the stated needs. Did you listen to the posting and to the earlier conversations, or are you giving the answer you would give to any employer?
• Evidence. Can you attach a concrete example to each claim, with enough detail that it could be checked?
• Self-awareness. Do you know which parts of the role you are strong on and which you would need to grow into, and can you say so without either bragging or apologising?

Notice what is missing from that list: a ranking of your personality traits. Adjectives such as hard-working, passionate, detail-oriented and fast learner are claims every candidate makes and none can prove in a sentence. They cost you time and give the interviewer nothing to write down.

How this differs from two questions that sound similar

Three interview questions get confused so often that candidates end up giving one answer three times. They are "tell me about yourself," "why do you want to work here," and "why should we hire you." Each points in a different direction, and the difference is easiest to remember as past, them, and match.

"Tell me about yourself" is about your path: where you have been and how it leads to this room. We cover that in our guide to how to introduce yourself in an interview. "Why do you want to work here" is about your motivation for this specific employer, which is the subject of our guide to answering why you want to work here. "Why should we hire you" is about neither your history nor your wishes. It is about what the employer gets. If your answer contains the phrase "I've always wanted to," you have drifted into the second question.

The three-part structure

A good answer has a shape the interviewer can follow without effort. Three parts is enough: their problems, your evidence, your first moves. Spoken at a normal pace, that comes to somewhere between 60 and 120 seconds, which is long enough to make a case and short enough that the interviewer can still steer the conversation.

1. 1Restate the two or three problems the role exists to solve. One sentence. "From what I've heard, this role comes down to three things: X, Y and Z." This proves you were listening and frames everything that follows. Two problems is fine. Four is too many to hold in the air.
2. 2Match each problem with one specific piece of evidence. One example per problem, a sentence or two each, with a number or a named outcome where you honestly have one. Do not tell the full story; give the headline and let them ask for more.
3. 3Close with what you would do early on. One or two sentences about your first 30 to 90 days. This moves the interviewer from evaluating you to picturing you in the job, which is where you want their attention when you stop talking.

The evidence in part two should be the compressed version of stories you already have prepared. If you have built a story bank using the STAR method, each match is simply the result line of one of those stories with a few words of context. If the interviewer wants the situation, task and action, they will ask, and you will have them ready.

One optional addition: if you are the first to name a gap in your own profile, part two can include a single honest sentence about it. Used well, that sentence is the strongest signal of self-awareness in the whole answer. The under-qualified example below shows how.

How to find the problems the role exists to solve

Part one only works if the problems you name are the real ones. Guess wrong and the rest of your answer is well-organised evidence for the wrong job. There are two sources, and you should use both: the job posting, and everything that was said in earlier rounds of the process.

Reading the job posting

A posting is a list of duties, but behind most of those duties sits a reason the company is hiring. Read it looking for the reason rather than the tasks.

• Order. The first few responsibilities are often what the role spends most of its time on. Items near the bottom are more likely to be carried over from a template.
• Repetition. If "cross-functional" or "stakeholders" appears four times, coordination is probably a pain point, whatever the job title says.
• Verbs. "Build," "establish" and "launch" suggest something does not exist yet. "Improve," "streamline" and "reduce" suggest something exists and is not working. "Maintain" and "support" suggest they want stability.
• Required versus preferred. The required list tells you what the employer considers the minimum. The preferred list hints at where they hope the role will go.
• Context lines. Phrases such as "as we expand into" or "following our recent" explain why the role is open now.

Translate each cluster into a problem stated in the employer's terms. "Manage vendor relationships, negotiate contracts, track spend" becomes "they need someone to get supplier costs under control."

Listening in the earlier rounds

Interviewers tell you what worries them, usually without meaning to. Anything a recruiter or manager mentions twice, any question that gets asked in two different forms, and any sentence that starts with "the last person in this role" or "honestly, the challenge is" is a problem statement. Write these down straight after each conversation, in their words.

You can also ask directly. "What would a great first six months look like?" and "What is the hardest part of this job?" both produce a ready-made list. Our guide to questions to ask at the end of an interview has more of these, organised by who you are speaking to. By the later stages, as we explain in the piece on second interview questions, you are expected to have picked up this context and to use it. Quoting it back ("you mentioned last week that the onboarding backlog is the priority") is one of the simplest ways to sound like someone already on the team.

If the question arrives in a first screening call before you have heard anything, work from the posting alone and say so: "Based on the job description, it looks like the priorities are X and Y. Tell me if I've misread that."

Worked answers for five situations

The structure stays the same in every case, but what counts as evidence changes with your situation. The five answers below are written out in full so you can hear the rhythm. The roles and numbers are illustrative. Replace them with your own true details and never borrow a figure you cannot explain.

Entry-level, with little experience

With no job history, your evidence comes from coursework, part-time work, internships, volunteering and projects. The mistake is to apologise for that. The role was posted at entry level, so the interviewer is not expecting ten years. They want proof you can learn fast and be relied on.

From the posting and what you've described, this coordinator role needs three things: someone who keeps a lot of small details straight, who is comfortable talking to customers, and who can pick up your scheduling system quickly. On detail, I ran registration for a 300-person campus conference and we had no double bookings across two days. On customers, I worked the front desk at a busy gym for two years, which was mostly solving problems for people who were already annoyed. On learning systems, I taught myself the university's event software from the documentation and ended up training the next volunteer team. In my first month I'd want to shadow whoever handles the calendar now and take the routine bookings off their plate.

Career changer

A career changer has to do the translation work for the interviewer. Do not ask them to imagine how teaching or nursing or retail management might apply. Name their problem first, then show the same problem solved in your old setting, and state plainly what you have done to close the technical gap.

As I understand it, this customer success role is about three things: getting new accounts using the product quickly, spotting accounts that are going quiet before they cancel, and explaining technical things to non-technical people. I spent eight years teaching high school science, which is those three problems with a different audience. I onboarded about 150 new students every year, I tracked who was falling behind and stepped in early, and explaining hard ideas simply was the job. What I didn't have was the software side, so over the past year I completed a customer success certificate and I've been using your product's free tier for the last month. Early on I'd want to sit in on renewal calls to learn where accounts actually stall.

Experienced hire

With a long track record the risk is saying too much. Choose the two or three results that map most directly onto this employer's situation and leave the rest on the resume. Scale and similarity matter more than seniority: show you have solved this problem at roughly this size.

Two things have come up in every conversation I've had here: the close takes too long, and the finance team spends its time on reconciliation instead of analysis. At my current company, which is about your size, I led the project that took month-end close from twelve working days to six, mostly by fixing the handoff from sales operations rather than adding people. That freed two analysts to build the forecasting model the leadership team now uses each quarter. I'd spend my first few weeks mapping where your close actually loses time before proposing anything, because the bottleneck is rarely where people assume.

Internal candidate

Internal candidates can lose to outsiders by assuming their work is already known. Often it is not, at least not in the form a hiring panel needs. Make the case as fully as an external candidate would, and use the advantage only you have: a shorter ramp-up, existing relationships, and a view of what is actually broken.

I'd be making this case even if I were applying from outside. The team lead role needs someone who can keep delivery predictable, develop the newer analysts, and manage the relationship with the product group. For the past year I've run sprint planning informally and we've hit our committed dates in ten of the last twelve sprints. I've mentored two of the three most recent hires. And I already have a working relationship with the product managers, including the difficult conversations. What I'd add from the inside is that I know where our process loses time, and I could start on the handoff problem in the first week rather than the first quarter. The part that's new for me is formal performance management, and I'd want training and your guidance on that.

Slightly under-qualified

If you meet most of the requirements but not all, assume the interviewer has already noticed. Naming the gap yourself, briefly and once, is more convincing than hoping it goes unmentioned. State it, show the nearest evidence you have, explain how you are closing it, and move on. Do not linger.

The posting asks for five years of experience and people management, and I have three years and have led projects rather than a team, so I'll address that directly. What the role needs most, from what you've told me, is someone who can rebuild the reporting pipeline and get the regional teams to trust the numbers. I rebuilt ours last year, cut the weekly report from two days of manual work to about an hour, and ran the rollout across four regional offices, which meant coordinating six people who didn't report to me. On line management, I'd be learning, and I'd want to be honest about that rather than oversell it. In the first 60 days I'd focus on the pipeline, which is where I can deliver straight away.

How to sound confident without sounding arrogant or generic

Arrogance and blandness are opposite failures with the same cause: claims without evidence. "I'm the best person for this" and "I'm a hard worker" are both unsupported assertions. One overreaches and the other says nothing. The fix for both is to let specific facts carry the weight and keep your own commentary to a minimum.

A useful test is to ask whether a sentence could be said, word for word, by every other candidate. "I'm a hard worker who learns quickly" passes that test, which is why it fails the interview. "I taught myself SQL in six weeks so I could stop waiting on the data team" could only be said by you, and it demonstrates both qualities without naming either.

• Describe, don't rate. Say what you did and what happened. Leave words like "exceptional" and "proven" for the interviewer to supply.
• Credit the team where it is true. "I led the project and the team cut close time in half" is more believable than a version in which you did everything alone.
• Include one honest limit. A single sentence about what you would need to learn makes the other sentences easier to believe.
• Use their language. Framing your evidence around problems they named keeps the answer about them, which is the opposite of how arrogance sounds.
• Don't open with a disclaimer. "I know I'm probably not the most experienced, but" lowers the value of everything after it.

If you have a prepared pitch from networking, do not reuse it here unchanged. A pitch is written for someone who knows nothing about you; this answer is written for someone who has told you what they need. Our collection of elevator pitch examples covers that first-contact situation, and the two should be kept as separate tools.

Common mistakes

Most weak answers to this question fail in a handful of predictable ways, and nearly all of them come from treating it as a prompt for self-praise instead of a matching exercise. Check your draft against the list below before you rehearse it aloud, because several of these are hard to hear in your own answer.

• Comparing yourself to candidates you have not met. "I'm more qualified than anyone else you'll see" is a claim you cannot know to be true, and the interviewer knows that. Even when the question is phrased as "why you over the others," answer about the fit between you and the role.
• Reciting the resume. A chronological walk through your jobs answers a different question and leaves the interviewer to do the matching themselves. Select, don't summarise.
• Going over two minutes. Long answers bury the strongest point. Time yourself aloud; if you pass two minutes, cut an example rather than speeding up.
• Listing adjectives. Three traits with no evidence is an easy answer to give and an easy one to forget.
• Making it about what you want. "This would be a great step for my career" is a reason for you to accept an offer and gives them no reason to make one.
• Promising a transformation. "I'll double your sales in six months" is a guess about a business you have not seen from the inside. Describe what you would do first and leave the outcome unpromised.
• Memorising a script. A word-perfect recital sounds like one. Memorise the three problems and the three pieces of evidence, and let the sentences vary.

A related trap appears when the interviewer follows up about the longer term. Having just described what you would do in your first 90 days, be ready to extend the picture; our guide to answering where you see yourself in five years covers how to do that without overcommitting.

The written version: applications and cover letters

The same question turns up in writing, as an application form field ("Why are you a good fit for this role?"), a screening questionnaire, or the unstated purpose of a cover letter's middle paragraph. The structure carries over unchanged, but writing rewards tighter wording and exact figures, and the reader may give it only a quick scan.

For a form field, roughly 100 to 150 words is a sensible target unless a limit is given, and any stated character count should be respected exactly. Lead with the match, put your strongest piece of evidence first instead of building up to it, and use the posting's own terms for skills and tools, since the person screening is likely to be scanning for them. Drop the spoken connective phrases ("from what I've heard," "as I understand it") and state the needs directly.

This role calls for someone who can reduce supplier costs, tighten contract terms and report spend clearly to finance. In my current position I renegotiated our three largest vendor contracts, lowering annual spend by 11%, and introduced a monthly spend report that finance now uses in its forecast. I have worked with the same procurement platform listed in the posting for four years. In the first quarter I would start by reviewing the contracts due for renewal this year, where savings are usually quickest to find.

In a cover letter, this content belongs in the second paragraph, after a short opening that says which role you are applying for and why this employer. Do not paste the same paragraph into every application. The evidence can stay the same from one application to the next, but the problems named in the first sentence have to come from that employer's posting, and if they don't, a reader can tell within a line.

How to rehearse it

Prepare this answer as a small set of parts and not as a speech. Write the two or three problems on one line, one piece of evidence under each, and a single sentence about your first weeks. That is five or six lines, and it is all you need to carry into the room.

Say it aloud three or four times with a timer, changing the wording each time so that no phrasing sets hard. Record one run on your phone and listen for adjectives and for any stretch where you are narrating your resume. Then update the first line after every interview round, because each conversation will tell you something new about what the role is for. The answer you give in the final round should be noticeably more specific than the one you gave the recruiter.