Most interview questions are easy to fake your way through. "What's your biggest weakness" has a well-worn safe answer. "Where do you see yourself in five years" barely gets asked anymore. But two questions still reliably make good candidates freeze, because there's no template answer that survives contact with a real interviewer: "Why should we hire you?" and "Why do you want to work here?"
Both fail in the same shape. People either overcorrect into arrogance, or undercorrect into mush. Neither version actually answers the question, and interviewers can tell within about one sentence which one they're getting.
"Why should we hire you?"
Here's the trap: the question sounds like it's asking you to prove you're the best candidate alive, so people either reach for grand personality claims ("I'm a hard worker, a fast learner, and I give 110%") or freeze up because they don't want to sound like they're bragging. Both instincts miss what's actually being asked.
The question isn't "convince me you're better than everyone else." It's "can you tell me specifically why you fit this role," and the interviewer has no way of knowing that unless you show them the match yourself. Nobody else in the room has done the work of connecting your background to their open req — that's your job, and it's a research-and-assembly task, not a confidence performance.
Treat it like a pitch built from evidence that's already sitting on your resume. Pick two or three things the job actually needs — pull them straight from the posting, not from a guess — and match each one to something specific you've done. That's the whole structure. No personality claims required.
Say the role is a mid-level marketing manager position that lists "experience running lifecycle email campaigns" and "comfort working cross-functionally with sales" as requirements. Here's the weak version next to the version that actually does the job:
Weak:
"I think you should hire me because I'm a dedicated, hard-working person who really cares about doing great marketing. I'm also a fast learner and I get along well with everyone on my team."
This could be said by literally any applicant for any job, which is exactly the problem. It contains zero information the interviewer didn't already have before you opened your mouth.
Working version:
"From the posting, it sounds like two things matter most here: someone who can own lifecycle email end to end, and someone who can work closely with sales rather than just handing off leads. Those happen to be the two things I've spent the last two years doing — I rebuilt our onboarding email sequence and took our activation rate from 22% to 34%, and I sit in on sales' pipeline reviews every week because half of what I build is based on what they're hearing from prospects. I'm not coming in needing to learn what the job involves day to day, I've been doing a version of it already."
Notice the second version never claims to be the best candidate. It doesn't need to. It just makes the match undeniable by using numbers and specifics the interviewer can actually evaluate, instead of adjectives they have to take on faith.
"Why do you want to work here?"
This one fails differently. The instinct is to prove you did your homework, so people recite facts they googled the night before: "I love your mission, and I've always admired your innovative culture and commitment to excellence." The problem is that sentence is available to every single candidate who spent ten minutes on the company's About page. It signals research effort, sure, but it signals zero actual interest, because it could be copy-pasted onto a cover letter for a completely different company with a search-and-replace of the name.
The fix isn't more research. It's connection. Take something specific and true about the company or the role, and connect it to something specific and true about your own trajectory — a problem you've gotten interested in, a direction you're trying to grow in, a kind of work you want more of. The company fact and the personal fact both need to be real and specific, and the link between them needs to be something only you could draw.
For example, if you're interviewing at a company that just launched a self-serve product tier after years of being enterprise-only:
"What made me want to apply specifically is that you just launched the self-serve tier. I've spent my whole career on enterprise sales cycles that take six months to close, and about a year ago I started doing freelance consulting for smaller companies on the side, which pulled me into thinking a lot about how you sell to someone who wants to try a product today and pay with a credit card, not go through procurement. That's a genuinely different skill set, and it's the direction I want to grow in. You're one of the few companies actually making that transition right now instead of just talking about doing it."
That answer couldn't be given to a competitor down the street, even one in the same industry, because it names a specific fact about this company (the self-serve launch) and a specific, verifiable fact about the candidate (the freelance consulting work) and draws a line between them that took actual thought. That's what "doing your research" is supposed to produce, and reciting the mission statement isn't it.
Why interviewers even ask these
Neither question is fishing for flattery, and neither one is really testable in the way a technical question is. What they're testing is self-awareness on the first question — can you accurately assess your own fit, or do you only have vague adjectives about yourself — and genuine interest on the second, meaning can you tell the difference between wanting a job and wanting this job.
Interviewers ask both because weak answers to either one predict something real: a candidate who can't articulate their own fit often turns out not to have thought hard about the role at all, and a candidate reciting company facts often turns out to be applying everywhere with the same materials. Neither is disqualifying on its own, but both are a flag.
If you want a single gut check for prepping any tough interview question, not just these two, ask yourself: would this answer only make sense coming from me, or could literally anyone say it? If the sentence survives with someone else's name swapped in, it's not finished yet.