How to Answer "Why Should We Hire You?" With a Job Interview Preparation Plan That Actually Works

You have the interview. Now your brain has gone blank.

You open a browser, type "common interview questions," and land on a list of 47. You read them. You nod. You close the tab. You still have no idea what you would actually say out loud at 10:00 a.m. on Tuesday.

Here is what I tell the people I work with: the problem is almost never that you lack talent. It is that you have no job interview preparation plan. You are preparing by worrying, and worrying feels like work. It is not.

This guide gives you the plan. It will take you about four hours of focused effort spread across roughly a week, and it ends with one thing: you walking in able to answer "Why should we hire you?" without flinching, because you built that answer on purpose instead of hoping it shows up.

The real reason interview prep goes wrong

Most people prepare backward. They start with what they want to say about themselves, then try to fit it into whatever the interviewer asks.

That is why answers come out generic. The interviewer hears "I am a hard worker who learns quickly" for the ninth time that day, and your face starts to fade.

Preparation works forward instead. Start with the job, work out what the hiring manager is quietly afraid of, then go find the evidence in your own story that says: I am the person who makes that fear go away.

I call this the Target, Gap, Proof approach. Three steps, in order. You will use it again and again in this guide.

• Target: What does this specific role need from the person who gets it?
• Gap: What is currently going wrong, missing, or under pressure in this team or business right now?
• Proof: Which of your real, specific experiences shows you have solved something like that before?

Every strong interview answer is a small version of that structure. Once you see it, you cannot unsee it.

Step 1: Read the job post like a detective

Give this 30 minutes. Not five.

Open the job description and a document side by side. Read the post three times, each time hunting for something different.

Pass one: the actual problems

Ignore the buzzwords. Look for language that reveals pain. Phrases like "we need someone who can hit the ground running," "our processes are not yet formalized," "this is a newly created role," or "you will help us build" tell you this team is under pressure or starting from scratch. Mark those with a highlighter.

Pass two: the recurring requirements

Count how often certain words appear. If "stakeholders" shows up four times, stakeholder management is not a nice to have. It is the job. If "reporting" appears in three bullets, someone there is tired of chasing reports.

Pass three: the gap

Now write one sentence, in plain language, describing what this person is hired to fix or protect. Here is an example from a past client I will call Jordan, who was applying for a junior marketing coordinator role at a small software company:

"They have a product people like but a messy content calendar, and they need someone who will keep things on track without being told twice."

That single sentence is worth more than an hour of reading interview tips. It tells Jordan exactly which stories to tell.

Step 2: Build a proof bank before you build answers

You do not invent good interview stories on the day. You collect them, on paper, ahead of time. Set aside 45 minutes for this step.

A proof bank is a short list of eight to ten real experiences, written in bullet form, that you could pull into almost any answer. Include school projects, part time jobs, volunteer work, side projects, and family responsibilities. Do not filter by whether you think it is impressive. Filter by whether it is yours.

For each entry, write four lines:

1. Situation: What was going on, in one sentence.
2. Action: What you specifically did, not what the team did.
3. Result: What changed. Use a number if you have one. If you do not, describe the change plainly: fewer complaints, delivered on time, no errors in the final report.
4. What it proves: One phrase, like "handles pressure," "good with difficult customers," or "learns fast."

Jordan's proof bank included a genuinely ordinary fact: during a summer retail job, they started logging customer complaints in a shared spreadsheet because the front of store and back of store kept blaming each other. Within a month, the two teams were sorting real issues instead of arguing. Result: fewer repeat complaints, no formal authority required.

That story ended up answering four different interview questions, including "Tell me about a time you worked with a difficult teammate." Nothing about it was glamorous. It was specific, and specific is what people remember.

Interviewers are not grading how impressive your life is. They are checking whether your evidence matches their problem.

Step 3: Build your answer to "Why should we hire you?"

This is the question you asked about, so let us build it properly. Do not memorize a paragraph. Build a two minute answer with three movements.

Movement one: show you understand the job (20 seconds)

Say the gap back to them in your own words.

"From what I read and from what you have described, the person in this role needs to keep content moving on schedule while a lot is still being figured out internally."

Movement two: give two pieces of proof (60 to 80 seconds)

Two stories, not five. One from work or school, one from anywhere else that is real. Use situation, action, result, briefly.

"At my retail job, our two teams were blaming each other for the same customer problems. I started tracking complaints in one shared sheet and pushed for a short weekly review. We stopped repeating the same fixes. Separately, in a school project, I had to rebuild our timeline twice when the scope changed and still delivered on time, which taught me to build slack into a plan rather than wish for it."

Movement three: name the benefit clearly (20 seconds)

Do not trail off. Say the thing.

"So if you hire me, you are getting someone who will keep the schedule honest and raise problems early rather than late. That is the part of this role I am actually excited about."

Notice what is missing: no "I am very passionate," no "I am a people person." Proof, then a plain sentence about what it buys them.

Step 4: Practice out loud, not in your head

This is the step almost everyone skips, and it is the one that makes the difference. Reading answers silently builds recognition. Speaking builds recall.

Here is a practice schedule that fits around work, school, or a job search. Total is about two hours of live practice across the week, and it fits in twenty minute blocks.

Two rules for practice. First, never practice the same answer more than three times in a row. You will start sounding scripted, and scripted reads as nervous. Second, practice in the clothes and posture you will use on the day. Small physical details quietly reduce the panic.

Step 5: Prepare the questions you will ask

Your questions are not a formality. They are the second half of the interview, and they are where you get to check whether this job is worth taking.

Bring four, written down. Two about the work, one about how success is measured, one about the team. For example: "What does a strong first three months look like in this role?" or "Where does this team lose the most time right now?"

That second question is deliberately a little bold. It signals you are thinking like a person who fixes things, and it gives you real information about what you are walking into.

Step 6: Handle the three questions that undo people

Give this step 30 minutes. These are the ones where preparation pays for itself.

"What is your greatest weakness?"

Name a real one that is not central to the job, say what you have done about it, and show the current state. Example: "I used to over prepare and then run long in meetings. I now time my own agenda items and cut anything that is not decision relevant. I still like to be thorough, but I do not let it eat other people's time."

Do not use the fake weakness trick. Interviewers have heard "I care too much" a thousand times.

"Tell me about a time you failed."

Pick a real failure with a real consequence, then spend most of your answer on what you changed afterward. The failure can be small. The lesson must be specific.

"Why are you looking for a new role?" or "Why did you leave?"

Keep it forward facing and short. One sentence on the honest reason, one sentence on what you are moving toward. Never criticize a former manager or employer, even if the criticism is deserved.

Step 7: The day before and the hour before

The day before is not for cramming. Do these five things and stop.

1. Confirm the time, format, platform or address, and the interviewer's name and title.
2. Read your Target, Gap, Proof sentence once. Just once.
3. Choose your clothes and lay them out.
4. Prepare your notes, ID, and a pen and paper. If it is a video interview, check your lighting and audio.
5. Close the laptop and do something that has nothing to do with jobs.

The hour before, do a single out loud run of your "Why should we hire you?" answer, then a box breath or a short walk. Arrive or log in five minutes early. Not thirty. Thirty minutes early is its own kind of stress.

Step 8: Close the interview on purpose

Most people end with "that sounds great, thanks." You are going to end with a sentence that makes their decision easier.

"Thank you for the detail on the reporting side of the role. Based on what we talked about, I am confident I could take the scheduling work off your plate quickly. What are the next steps, and is there anything else I can send you that would help?"

Then send a short thank you note within 24 hours. Two or three sentences. Reference one specific thing from the conversation. Do not write an essay.

What to do in the 48 hours after

Write down every question you were asked while it is fresh. Mark the three you answered worst. Those three go straight into your next preparation round.

This is the habit that compounds. Each interview makes the next one better because you are collecting real data instead of guessing. If you are interviewing in several places at once, keep one document with a section per company, and update it the same day. Do not trust your memory two weeks later.

The honest part

A good plan does not guarantee an offer from any single interview. Nobody can promise that, and anyone who does is selling you something.

What a plan does guarantee is this: you will stop walking in underprepared and hoping personality carries you. You will know your evidence, you will know their problem, and you will be able to say plainly why you are worth hiring. That changes how you sit in the chair. Interviewers notice that before you finish your first sentence.

If you want to work through this with structure and someone holding you accountable, that is exactly what I do. We build your proof bank, sharpen your answers, and rehearse until the room feels smaller. Start with a free intro call, or bring this guide to a workshop and do the work with other people in the same position. Either way, do not read this and then close the tab.

Pick step one. Set a timer for 30 minutes. Open the job post and start reading for the gap.