OfferDrill.

Interview questions

The hard ones

How to answer "why do you want to work here?" when you've applied to forty places.

This page gives you a way to build an honest, specific answer for a company you didn't grow up dreaming about. You'll get the structure, the three things to research tonight, and sample answers you can adapt to your own facts.

Why they ask it

They're checking whether you'll show up in six months. Hiring is expensive, and the person who took the job because it was the first offer tends to leave when the second offer comes. They want a reason that's attached to something real, not a reason that's attached to being unemployed.

They're also checking whether you did any homework. Not because homework is noble, but because it's the cheapest available signal for how you'll handle work. Someone who spent twenty minutes on the company site before an interview probably prepares for other things too.

And there's a quieter thing underneath. They want to hear you connect what they need to what you do. That's the whole interview in one question. Most people answer it with flattery and miss the chance.

What not to say

"You're a leader in the industry with a great reputation and a strong culture."

You could say this about any of the forty companies, and they know it. Generic praise reads as "I didn't look you up." It burns thirty seconds and scores nothing.

"Honestly, I need a job. I've been out of work since [month] and I'm applying everywhere."

It's true, and honesty is right, but it's an answer about you and not about them. It also hands them a reason to worry you'll leave. Keep the truth, lead with the work: you can say you're looking actively and still name why this role specifically is a fit.

"The pay is good and the commute is short." Or, in a remote job, "I want to work from home."

These are legitimate reasons to take a job. They're just not reasons to hire you. Save them for when they ask what you're looking for, or for the offer conversation.

Reciting the mission statement back to them word for word.

They wrote it. Hearing it repeated tells them nothing except that you found the About page. Instead, name one specific thing the company does and say what you noticed about it.

How to build a strong answer

  1. Spend twenty minutes finding one specific true thing.
    Not the mission statement. Look at: the job posting itself (what problem are they hiring to solve?), the product or service page, recent news or a press release, the LinkedIn profile of the person you're meeting, and customer reviews. You're hunting for one concrete fact you can name out loud. "You just opened a second location in [city]." "The posting says this role owns the month-end close, which is currently split across three people." "Your whole product is aimed at [type of customer], and that's who I've spent six years serving." One fact is enough. Two is plenty.
  2. Connect that fact to something you've actually done.
    This is the part people skip, and it's the part that scores. The structure is: here's what I noticed about you, here's the work of mine it lines up with. If they need someone to clean up a messy process, say the thing you cleaned up. If they serve small businesses, say you've spent years on the phone with small business owners. The specific fact is the setup; your experience is the punch.
  3. Say what you want next, and make it true.
    One sentence about the direction you're headed and why this job points that way. "I want to go deeper on [skill] instead of wider." "I want to be somewhere small enough that I own the whole thing." "I'm early in my career and I want to learn from a team that does this at volume." This is what makes the answer sound like a choice instead of an application.
  4. Cut it to forty seconds and stop talking.
    Three or four sentences. Say it out loud once, in the car or to the wall, so the shape is in your mouth. Don't memorize the words — memorize the three beats: the specific thing, your matching experience, where you're headed. Then stop. Silence after a good answer is fine. Filling it is how good answers get ruined.

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, applying widely, and the company is an ordinary employer you had no prior feelings about.

I read the posting a few times, and what caught me is that this role owns [the specific responsibility named in the posting] end to end. That's the part of my last job I was best at — I ran [the process] for a team of [number] and took the turnaround from [the actual before] to [the actual after]. I'm looking at a lot of roles right now, I'll be straight with you, but this one I applied to twice because the scope is right. I don't want to manage a piece of it. I want to own it.

It names a real detail from the posting, backs it with a result that belongs to you, and handles the "you're applying everywhere" fact by saying it plainly and then immediately explaining what set this one apart. Adapt the specifics — the numbers have to be yours and real.

Early career, one internship, not much of a track record yet.

Two things. One, you work with [type of customer or product], and that's what I did during my internship at [employer] — I spent the summer [the actual task], so I know what the day looks like and I liked it. Two, I looked at the team on LinkedIn and most people here have been in the role three or four years before moving up. I'm looking for a first job where I'll be trained properly, not thrown at whatever's on fire. That matters more to me right now than anything else.

You're not pretending to have ten years of opinions. You name the one real experience you have, then give an honest reason about your own development. Wanting to be trained well is a good reason and employers respect hearing it said clearly.

You genuinely don't know much about the company yet, and the industry is new to you.

I'll be honest that I didn't know [company] before this posting — I came at it from the role. What I found when I looked is that you're [the specific thing you learned, in your own words]. The reason I kept reading is [the actual reason — the customer type, the size, the problem they solve, whatever is true for you]. I've done [your relevant work] for [number] years, and it transfers directly. I came into this interview with questions rather than assumptions, and I've got a few for you.

Admitting you came for the role rather than the brand is honest and extremely common — interviewers hear worse every day. It works because you immediately prove you did the research anyway. Only use this version if you actually have good questions ready.

What comes next

Answer this one well and the interviewer usually goes here:

  • What do you know about what we do?
  • What questions do you have for us?
  • What are you looking for in your next role?
  • Where else are you interviewing?
  • Why are you leaving your current job? Or: tell me about the gap.
  • What would make you turn this job down?
  • Where do you see yourself in three years?

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 don't need to love this company to answer this well — you need one true reason, said in forty seconds, and the willingness to stop talking after it.