OfferDrill.

Interview questions

The hard ones

How to answer "why should we hire you" when you're tired and it's the last question.

This page gives you a simple, honest structure for the closing question, plus three sample answers you can adapt to your own facts. You'll walk in knowing the three things you want to say and when to stop talking.

Why they ask it

By the time this question comes, they already know your background. They're not asking you to repeat your resume. They're asking you to do the work of connecting the dots for them, because they're tired too, and the person who makes their decision easy is the one they remember at 5pm.

Underneath it, they want to know one thing: do you understand what this job actually needs? Plenty of candidates are qualified on paper. The one who can say "you told me the biggest problem here is [the thing they told you], and here's what I've done with that exact problem" has shown they were listening for the last forty minutes.

There's a smaller thing too. This is often the last thing you say. They're watching whether you can be clear and brief under mild pressure, because that's what you'll do in meetings, on calls, with customers. A rambling four-minute answer tells them something even when the content is good.

What not to say

"I'm a hard worker, I'm passionate, and I'm a quick learner."

Every single candidate says this, so it carries no information. They can't picture anything, can't repeat it to their boss, and can't use it to choose you over the next person. It's not wrong, it's just invisible.

Walking back through your resume, job by job, from the beginning.

They have the resume. Re-reading it out loud takes three minutes and tells them nothing new, and by minute two they're thinking about their next meeting instead of you.

"Because I really need this job" or anything that centers what you need.

It's honest, and the need may be real, but this question is the one place they're asking what they get. Save your reasons for wanting the job for "why do you want to work here." They're different questions.

"Honestly, I don't know, you'd know better than me." Or hedging into apology.

Modesty reads as doubt here. If you can't name a reason to hire you, you've handed them a reason not to, and they'll take it because deciding is hard.

How to build a strong answer

  1. Pick the one thing they care most about, before you walk in.
    Reread the job posting and find what shows up first and repeats. Then listen during the interview — when they describe the problem, the backlog, the person who just left, the thing they wish someone would own. That's your target. If they named a specific problem in the room, use their words back: "You mentioned the handoff between sales and support keeps breaking." That one sentence proves you were listening and beats any adjective.
  2. Name two or three strengths, not seven, and make them concrete.
    Two or three is what a person can hold in their head. Make each one something you can point at: a system you built, a type of customer you handle, a tool you know cold, a certification, a language. "I've run month-end close for a [size] team for [number] years" is a strength. "Detail-oriented" is a word.
  3. Attach a short piece of proof to each one.
    One sentence each. What you did, and what changed. Use real numbers if you have them and remember them accurately — if you don't, say it plainly: "we cut the backlog roughly in half over a quarter" is fine. Don't invent a figure to sound sharper. If they ask a follow-up about a number you made up, the whole interview goes with it.
  4. Close with the connection, then stop talking.
    One line that ties it back: "That's the same problem you're describing, and I'd want to start there." Then be quiet. The silence after a clear answer feels long to you and normal to them. Total time: sixty to ninety seconds. Practice it out loud once with a timer, so you know what ninety seconds feels like in your mouth.
  5. Be honest about the gap, if there is an obvious one.
    If you're missing something they clearly want, don't pretend it isn't there and don't apologize for a paragraph. Name it in one clause and move to what you do bring: "I haven't used [tool] in production, though I've worked in [similar tool] for years and I'd expect a few weeks to get fluent." Candidates who name their own gap calmly tend to get believed on everything else.
  6. Say it in your own words.
    The samples below aren't scripts. Memorized answers come out flat, and they fall apart the moment the interviewer interrupts. Keep the three points and build the sentences fresh.

Examples to adapt

These are shapes, not scripts. Say them in your own words with your own facts — anything in brackets is a detail only you know, and it has to be the true one.

Mid-career, laid off, interviewing for a job much like the one you had.

Three reasons. First, you said the team is behind on [the thing they mentioned] and nobody owns it end to end. I owned exactly that at [employer] for [number] years, including the ugly part — [the specific hard piece]. Second, I've worked through a reorg and a hiring freeze there, so I'm used to getting things done with fewer people than the plan called for. When we lost half the team, I rebuilt the process so [the actual result]. Third, I'm not looking for a stepping stone. This is the work I'm good at and the work I want. I'd expect to be useful within the first month, not the first quarter.

It leads with their problem, not your history. The layoff isn't hidden or explained away — the reorg shows up as evidence of what you can handle. And the last line answers a doubt they didn't say out loud: whether an experienced person will stay.

Early career, one internship, applying for your first full job.

I'll be straight with you — I don't have years behind me, so let me tell you what I do have. During my internship at [employer] I was given [the specific task] and ended up [what you actually did or built]. Nobody was checking on me daily, so I learned to figure things out and ask good questions instead of a lot of questions. Second, I've spent [time period] getting solid in [specific tool or skill], which you listed in the posting, and I can show you [the project or work sample]. And third, you'll be training whoever you hire for this role either way. I'd rather you train someone who takes notes, does the reading, and doesn't need to be told twice. That's what my manager at [employer] said about me, and I'd want you to ask her.

It names the experience gap in the first sentence, then stops discussing it. It turns "junior" into a real argument — you're going to train someone regardless — and it ends by offering a reference, which is a thing only a confident person does.

Changing fields, where your background doesn't obviously match.

You're going to hire someone with a more direct background than mine, or someone like me. Here's the case for me. I spent [number] years in [previous field] doing [the transferable work], and the core of it is the same thing this job needs: [the shared skill]. When I [specific example], that was really [the skill] under a different job title. I also know the customer side of your business in a way most applicants won't, because I was that customer for [number] years — I know what makes them call, complain, and leave. What I don't have yet is [the honest gap]. I've been working on it through [the actual course, project, or practice], and I'd expect to be slower than a direct hire for the first couple of months and even after that.

It says the hard thing first, which makes everything after it credible. The transferable skill is named specifically instead of gestured at, and the honest timeline on ramping up reads as someone who's thought it through rather than someone selling.

What comes next

Answer this one well and the interviewer usually goes here:

  • What would you want to work on in your first ninety days?
  • What's the part of this job you think you'd struggle with?
  • You mentioned [the thing you claimed]. Walk me through how that actually went.
  • What would your last manager say is your biggest weakness?
  • We have other strong candidates. What makes you different from them?
  • Do you have any questions for us?

Say it out loud before it counts.

Reading a good answer and giving one are different skills, and the gap shows up in the room. Offer asks you this question out loud, on a clock, and tells you what landed. The first one is free.

Practice this out loud

You already know the answer to this one — you just need to say the true part out loud, in three pieces, and then let the room be quiet.