Why Do You Want to Work Here? How to Answer With Proof, Not Praise

12 min read

Updated October 8, 2026·Originally published October 8, 2026

Answer 'why do you want to work here?' in under a minute: the Name–Bridge–Bring structure, a 30-minute research sprint, and a scored weak-vs-strong answer.

To answer "why do you want to work here?", name one specific, checkable thing about the company — a product decision, a strategic move, a way the team works — then connect it to something you have actually done, and close with what you would bring or want to build there. Keep it under a minute. The test is simple: if you could swap in a competitor's name and the answer still works, it is too generic. "You're a leader in the industry with a great culture" fails. "You moved your whole carrier network onto one routing platform, and I've spent four years building route-planning software" passes.

The rest of this guide gives you the structure for that answer (Interview Drills calls it Name–Bridge–Bring), a 30-minute way to research a company, worked answers for four common situations, the mistakes that sink the answer, how it differs from "why should we hire you," and a real scored example: the same question answered weakly and then rewritten, each scored three times by the Interview Drills scorer.

What is the interviewer actually asking with "why do you want to work here?"

"Why do you want to work here?" is a research check disguised as a motivation question: the interviewer is listening for whether you know anything about this company that you could not have known about any other company. A candidate who has looked will say something specific in the first sentence. A candidate who has not will reach for adjectives — "great," "innovative," "leader."

The question also carries two quieter checks. One is fit: does your reason for wanting the job match what the job actually is? The other is staying power: if your only reason is the next step for your own career, the interviewer may wonder how long you will stay once that step is taken.

The question arrives in several forms, and they all want the same thing:

• "Why do you want to work here?"
• "Why this company?" / "Why us?"
• "What made you apply for this role?"
• "Out of everywhere you could be interviewing, why here?"

The Interview Drills scenario for this question puts it in its sharpest form — "So — why us? Out of everywhere you could be interviewing, why this company?" — and its coaching note sets the bar plainly: name something real and specific, connect it to where you are heading, and keep it under a minute.

How do you structure the answer? The Name–Bridge–Bring method

Name–Bridge–Bring is a three-beat structure for "why this company?": Name one specific thing about the company, Bridge it to something you have actually done, and Bring it home with what you would contribute or build there. Three to five sentences, under a minute.

Why the Name beat must be checkable. A specific fact — a product launch, a published post, a pricing change, a public hiring push — is something the interviewer can recognise in one sentence. That recognition is the whole point: it is proof that you did the research, delivered before you ask for anything.

Why the Bridge beat is the easiest one to skip. It is easy to name a real fact and then stop, which turns the answer into a compliment. The bridge is what makes the reason yours. It answers the unspoken follow-up: "Fine — but why does that matter to you?"

Why the Bring beat matters more than it looks. In the scored example later on this page, our own rewrite scored 91 out of 100, and the scorer's top note on it was still that the answer was framed entirely around what the candidate wanted ("want to be on," "want to learn"), not what the company would get. That is the gap the scorer named first, and closing it costs one sentence.

How do you research a company quickly enough to answer this?

You do not need hours. You need one fact you can say in a sentence, one link to your own experience, and enough depth to survive one follow-up question. Here is a 30-minute research sprint that gets you there.

1. Minutes 0–5: Read the job posting as a company document. What is the role built to fix or grow? The first two or three responsibilities are a better guide to the company's current priority than the About page.
2. Minutes 5–15: Find one recent decision. Look at the company's news or press page, its blog or engineering blog, product release notes, and recent posts from its leaders. You are looking for a choice the company made — something it built, changed, stopped, or bet on — not a value statement.
3. Minutes 15–20: Look at the people. Check the interviewer's and hiring manager's professional profiles for what they have worked on or written about. This can tell you which part of the company your Name beat should come from.
4. Minutes 20–25: Use the product, if you can. Sign up for the free tier, read the help docs, or look at what customers see. A firsthand observation ("your setup flow asks for billing before it shows any value") is stronger than anything you read about the company.
5. Minutes 25–30: Write three lines, then say them out loud. One Name, one Bridge, one Bring. Then ask yourself the follow-up the interviewer is most likely to ask — "what did you think of that?" — and make sure you have one more sentence behind each line.

A few rules that keep the sprint honest:

• Pick a decision over a description. "You serve mid-market retailers" describes the company; "you stopped selling to enterprise last year to focus on mid-market" is a decision, and decisions give you something to have an opinion about.
• Only cite what you could defend. If you name a blog post, be able to say what it argued. If an interviewer asks a question you cannot answer, the fact hurts you more than it helped.
• Prefer firsthand over secondhand. "I've heard great things about the culture" is hearsay. "Your engineers write public post-mortems, and I read the one on the March outage" is evidence.
• Avoid reciting the mission statement. The interviewer wrote it, or works next to the person who did. Hearing it read back adds nothing.

What does a good answer sound like? Four worked examples

The four answers below are illustrative examples written for this guide; every company in them is fictional. Each one follows Name–Bridge–Bring, and each is short enough to say in under a minute.

An experienced professional moving to a larger company

Role: senior analyst at Tallgrass Clinics, a fictional regional clinic network.

"Tallgrass started publishing wait-time data for every clinic on your website last spring, which I haven't seen another network do. I've spent five years building scheduling reports for a two-clinic practice, and the most useful thing I ever did was get those numbers in front of patients, not just managers. I'd like to do that across forty clinics, and I'd bring a reporting model that already cut our no-show rate."

Why it works: the Name is a public, checkable decision, the Bridge is a real overlap with the candidate's work, and the Bring line names a specific thing the company gets.

A recent graduate with little work experience

Role: junior marketing coordinator at Brambleway Learning, a fictional education-software company.

"I used Brambleway's study app all through my second year, and what stuck with me was that it told me when I was ready for a test instead of just counting hours. When I read your job posting, the first responsibility was writing the in-app messages students see, and that's the part of the product I noticed most as a user. I ran the social accounts for my university's tutoring center for two years, so writing short messages that get students to act is the thing I've practised most."

Why it works: a user's firsthand experience is a legitimate Name beat when you lack industry history, and the Bridge connects to real, if small-scale, experience.

A career changer

Role: instructional designer at Brambleway Learning, moving from classroom teaching.

"Your team publishes the research behind each new course module, including the ones that didn't work, and that's how I've tried to run my classroom for eight years — test a lesson, measure it, change it. I'm moving out of teaching because I want to design learning for thousands of students instead of thirty. You're one of the few companies I found where the designers are expected to show their evidence, and I'd bring eight years of testing lessons on real students."

Why it works: the career change is framed as a direction toward something, not an escape from something, and the Bring line turns the old career into an asset.

A small company with almost nothing published

Role: operations coordinator at Ostrander Valve Works, a fictional family-owned manufacturer.

"There isn't much about Ostrander online, so I read the job posting closely. It says you're moving order tracking off spreadsheets this year, and you're hiring someone to own that. That's exactly the project I ran at my last job — I moved our warehouse from three spreadsheets to one shared system in about four months. I'd much rather do that work at a company where it matters to the whole operation than be one person on a large team."

Why it works: when the public record is thin, the job posting is the research — and saying so honestly reads as resourceful, not underprepared.

What are the most common mistakes when answering "why this company?"

The central mistake is generic praise — an answer built from adjectives that would fit any company in the industry. CleverPrep puts the test in one line: "If you can swap the company name and the answer still works, it's a fail." Every mistake below is a variation on failing that test, or on making the answer about what you get instead of what they get.

Four of these — generic praise, secondhand evidence, all take and no give, and hedging — are exactly what the Interview Drills scorer flagged in our own weak example in the scored section below.

How is "why do you want to work here" different from "why should we hire you"?

"Why do you want to work here" asks about your motivation and research; "why should we hire you" asks about your value. The first starts from the company and moves toward you. The second starts from your evidence and moves toward their needs. The Interview Drills scenario for "why should we hire you" says it directly in its coaching note: "The interviewer isn't asking why you want the job — they're asking what you uniquely bring."

The overlap is the last beat. A strong "why here" answer ends with a Bring line, which is a small preview of "why hire me." If both questions come up in the same interview, do not repeat yourself: use your company research for the first and your strongest result for the second.

What a scored answer actually looks like

We wrote the two answers below as examples (they are not from users) and typed them into the Interview Drills scorer for this question's scenario, "Why This Company?", on October 8, 2026, scoring each three times. The scorer is the app's own (same prompts, model, and schema as its public score API), and it grades this scenario with its introduction-question rubric (Present–Past–Future), which rewards opening with where you are now and closing by connecting your background to this specific opportunity. That is why one run docked our rewrite for not naming the candidate's current role earlier. Typed answers carry no voice signal, so Delivery here judges how the text reads; spoken answers add pace, filler words, and pauses.

Answer (first take, typed):

"I've always admired your company. You're a leader in the industry and you have a great reputation, and I've heard really good things about the culture here. I'm looking for a place where I can grow my career and work with talented people, and this seems like a great opportunity to do that."

Overall score: 18 / 100 on all three runs. First run:

• Clarity 22 · Confidence 30 · Structure 20
• Conciseness 40 · Delivery 35 · Audience awareness 15

What the scorer flagged (first run, condensed):

• Generic praise ("a leader in the industry," "a great reputation") signals no research; replace it with one verifiable detail, such as a product decision or a recent strategic move
• "I've heard really good things about the culture" is secondhand evidence that undermines credibility; cite something you found yourself
• "Grow my career and work with talented people" says what you want, not what you bring; add one line about what you would contribute
• "This seems like a great opportunity" hedges; commit to the position or end on your contribution

Our rewrite (written by us, longer and specific, then scored the same way: 91 on all three runs):

"Two things. First, Northwind moved its whole carrier network onto one routing platform last year instead of buying regional tools, and your engineering blog post on why convinced me you treat logistics as a software problem. That's the kind of team I want to be on. Second, I've spent four years building route-planning features at a smaller freight company, and the next thing I want to learn is doing it at national scale. You're one of the few companies where that's the day job, not a someday project."

Northwind is a fictional company. The rewrite moves: (a) a Name beat the interviewer can check — a specific platform decision and a specific blog post; (b) a Bridge to four years of directly relevant work; (c) a clear reason this company and not another ("one of the few companies where that's the day job"). The hedges disappear because the candidate has something concrete to say.

The rewrite is not perfect, and the scorer said so. Its main improvement note on the first run was that both points describe what the candidate wants ("want to be on," "want to learn") and that one line on what the candidate would bring to Northwind's routing work would round it out. That is the Bring beat — which is why Name–Bridge–Bring treats it as required rather than optional.

How should you practise this answer before the interview?

Write your three lines, then say them out loud at least three times, changing the wording each time so no single phrasing hardens into a script. This answer is short, which makes it easy to over-rehearse into something that sounds recited — and easy to under-rehearse into a ramble when the question comes early and unannounced. Aim for under a minute; the answer-length guide covers timing by question type.

Prepare it alongside its neighbours. "Why this company?" can come right after "tell me about yourself," and the two should point the same way — the tell me about yourself drill covers that opening answer. It also shows up as a short interest check in the recruiter screen, and again, with more depth expected, in the hiring manager interview. If your interview is tomorrow, the 24-hour prep plan shows where this answer fits in one evening.

Interview Drills is an AI-powered interview training platform designed for people who have a real interview coming up. It diagnoses interview weaknesses with a free 3-minute quiz, prescribes a 14-day training track of practice drills, scores spoken answers on six dimensions in under 60 seconds, and, on the Interview Accelerator and Interview Pro plans, feeds the candidate's resume into scoring and feedback.

If you are not sure which part of your interviewing needs the most work, the free 3-minute quiz (25 questions, no account needed) identifies your interview persona and blind spot.

Frequently asked questions

What is the best answer to 'why do you want to work here?'

The best answer names one specific, checkable thing about the company — a product decision, a strategic move, a way the team works — connects it to something you have actually done, and ends with what you would bring or want to build there. Keep it under a minute. If you could swap in a competitor's name and the answer would still work, it is too generic.

How long should my answer to 'why this company?' be?

About 45 to 60 seconds spoken, which is roughly three to five fairly long sentences. That matches the 60-second target of the Interview Drills drill for this question; the site's answer-length guide allows motivation answers up to 75 seconds. One specific reason with a link to your experience beats a list of five compliments. If the interviewer wants more, they will ask a follow-up — and a short, specific answer invites exactly the follow-up you prepared for.

What if I can't find anything specific about the company?

Use the job posting itself as your source: what the role is built to fix tells you what the company is working on. You can also say what you learned from the recruiter or from an earlier interviewer, and ask a sharp question back. Admitting the public information was thin and showing how you read the posting is far stronger than generic praise.

Is it okay to say I want the job for the salary or benefits?

Not as your lead reason. Pay and benefits are legitimate factors, but leading with them tells the interviewer you would leave for the next better offer. Lead with the work and the company's direction; compensation belongs in the salary conversation, not in your answer to why you want to work here.

What is the difference between 'why do you want to work here' and 'why should we hire you'?

'Why do you want to work here' tests your motivation and research: why this company, not any company. 'Why should we hire you' tests your value: what you would deliver for them. The first starts from the company and moves toward you; the second starts from your evidence and moves toward their needs. Both should end with a line about what you would contribute.

Can I give the same answer to every company?

You can reuse the structure — one specific thing about them, the link to your experience, what you would bring — but not the content. The first sentence must be about this company and no other. A single generic answer reused everywhere is exactly what the swap test catches: it fits every company, so it proves nothing about this one.

What should I say if this company isn't my first choice?

Do not say so, and do not fake devotion either. Answer honestly about what genuinely interests you in this role and company — there is always something, or you would not be interviewing. A specific, true reason delivered plainly is more convincing than exaggerated enthusiasm, and it does not require ranking the company against your other options.