How to Answer "Why Do You Want to Work Here?" (+ Example Answers)
Three things belong in the answer: something specific about the employer, something specific about the role, and the reason those two fit what you can already do.
By Desmond Okafor · Published · Updated · 11 min read

By the end of this guide you'll be able to build an answer to "Why do you want to work here?" that names a real detail about the employer, connects it to work you have actually done, and lands in under 90 seconds. The method is the same whether you're a new graduate, stepping up, switching industries or coming back after time out — only the evidence changes.
You'll also get five worked examples and a short checklist you can run your own answer against before the interview.
Why interviewers ask it
Interviewers use this question to test three things.
First, motivation: whether your reasons for applying come from the work itself, or simply from the fact that the posting existed. Second, preparation. Anyone can skim a careers page, so they are listening for a detail you could only know if you looked past it — how the team is structured, what the product actually does, how the service is delivered, who the customers are.
Third, retention risk. Hiring takes time and money, and an answer that would fit any employer in the sector suggests you'd leave for the next one that calls. Some panels add a fourth check: judgement about fit. If your description of the place doesn't match what it's like to work there, the compliment reads as a misread rather than as enthusiasm. Say what you understand the job to be, and let them correct you.
Other ways you'll hear it
The same question gets dressed up in several ways. Treat all of these as a cue for the same prepared answer:
- "What attracted you to this role?"
- "Why us, rather than our competitors?"
- "What do you know about what we do here?"
- "What made you apply?"
- "Why this company at this point in your career?"
- "What are you hoping to get out of this job?"
The last one tilts towards you rather than them, so lead with what you want to do more of, then tie it back to the employer. "Why us, rather than our competitors?" needs one sentence that shows you know what makes this employer different — a market, a method, a size, an ownership model — not a criticism of anyone else.
How to build your answer
Use the Anchor, Match, Forward framework. It gives you three beats and a short closing line, which is enough for 60 to 90 seconds without rambling.
- Find the anchor. Pick one specific, checkable thing about the employer: the product line, the type of client, the geography they serve, a recent expansion or service change, the way the team is set up. One is enough. The anchor proves you looked, and it stops the answer sounding like it was written for the whole industry.
- Add the role hook. Name the part of the job description that made you apply — a responsibility, not the title. "The posting puts quality checks with the same person who runs the line" tells them you read it. This separates wanting the employer from wanting the job, which interviewers hear as two different things.
- Match it with your own evidence. Follow the hook with one short piece of proof from your experience: a task you've done, a problem you've handled, a result you can describe. Without this, enthusiasm floats; with it, the answer doubles as a reason to hire you.
- Say the fit out loud. One forward-looking sentence: what you'd do with the first few months, or what you want to get better at here. It answers the retention question without you promising anything you can't keep.
- Cut and time it. Read it aloud, cut adjectives, and time it. Aim for 45 to 90 seconds. Then prepare a 20-second version for a recruiter screening call and the full version for the hiring manager — the question gets asked at both stages and the right length differs.
What counts as a good anchor varies by employer. For a large national company, the detail might come from the annual report or a product page; for a small local business, it's more likely to come from what you've seen as a customer, what a current employee told you, or what the job posting itself says. Both are legitimate. Use whichever is actually available to you, and don't pretend to knowledge you don't have.
Example answers
New graduate
Maya, final-year marketing student, applying for a junior content coordinator role at a garden supply retailer
Most retailers in this space publish discount codes. You publish growing guides — the one on container vegetables is what sent me to your site in the first place, as a customer. That's the work I want to be close to, because it's the only marketing I've done that people thanked me for. I ran the newsletter for our student union for two years. It started as a sporadic listings email and I turned it into a weekly piece with a how-to at the top, which is when people began replying to it and forwarding it on. I'd be coming in junior, so I'd expect to spend the first months on scheduling, proofing and asset handling. But I'd like to be in a place where the content has a point beyond the promotion, and from the outside that's what yours seems to do.
Step up in the same field
Darren, warehouse team lead, applying for shift supervisor at a regional distribution centre
I've led a picking team of nine for three years, and the thing I kept running into was that I could fix my own shift and nothing else. Handover was where the problems lived. Your posting says the supervisor owns the cross-shift handover and the agency staffing plan, and that's the exact scope I've been reaching for without the authority to do anything about it. I already run the daily start-up brief and I rebuilt our pick-path labelling after a run of mis-picks, which cut the arguments between shifts more than it cut the errors — both mattered. I also wanted a site this size. At my current place one person covers everything; here there's an operations team, which means I'd learn the planning side properly instead of improvising it.
Industry switch
Alicia, account manager moving from print advertising into software sales
Honestly, the pull is the renewal cycle. In print I sold a page, the campaign ran, and the relationship reset to zero every quarter. Your accounts are annual subscriptions with an onboarding period, which means the job is keeping people successful rather than re-selling them the same thing. I've been doing a version of that already — my biggest client stayed six years because I sat in their planning meetings and brought them ideas they hadn't asked for. I know the product knowledge is the gap. I've spent the last two months in your help centre and your release notes, and I can describe what your reporting module does, though not yet how a customer actually configures it. I'd want a ramp where I shadow implementations before I'm on my own calls. The selling part I can bring with me on day one.
Career change
Tom, restaurant general manager of eleven years, applying for a patient services coordinator role at a community health clinic
Two things brought me here. The first is that this clinic takes walk-ins and runs an evening session, which tells me the front desk is a genuinely busy, unpredictable environment rather than a scheduling screen. That's the environment I'm good in. I've run a seventy-cover dining room on a short-staffed Saturday — booking conflicts, people upset about a wait, four things needing a decision at once — and kept the room calm. The second is that I want the pressure to be in service of something other than table turns. I'm not pretending to clinical knowledge; I'd be learning your systems, the intake paperwork and the privacy rules from scratch, and I'd expect to be slow for a while. What I'd bring immediately is the part most people find hardest, which is holding the counter together when the day goes wrong.
Returning after a career gap
Renée, bookkeeper returning after three years out as a full-time carer, applying to a nonprofit finance assistant role
I'll be direct about the gap: I stepped out in 2022 to care for my mother full time, and I'm coming back now because that chapter has ended and I'm ready to work. I'm applying here specifically because you're small enough that the finance assistant touches everything — payables, the grant reporting, the month-end pack — rather than sitting on one ledger all day. I did nine years of exactly that kind of generalist work for a family-run builder's merchant, and I kept my hand in during the gap doing the books for my brother's two-van plumbing business, including their VAT and payroll runs. Grant reporting is new to me and I'd want training on your restricted-fund coding. But I've reconciled a messy set of accounts before, I know what a clean audit file looks like, and I'd rather rebuild in a place where the work is varied than go somewhere I'd be bored in a month.
Mistakes to avoid
| Mistake | Fix |
|---|---|
| Reciting the "about us" page back to the panel — founding year, mission statement, values list. | Swap it for one operational detail: a product, a client type, a location, a service model. One real thing beats three slogans. |
| Making the whole answer about what you'd get — training, progression, exposure, a foot in the door. | Keep one sentence about what you want to learn, and spend the rest on what you'd do for them. |
| Praising them in terms that would fit any employer in the sector: "great reputation", "people-first culture", "industry leader". | Ask yourself whether a competitor could claim the same sentence. If yes, cut it and replace it with something only they could claim. |
| Running three minutes because you crammed in every fact you found. | One anchor, one role hook, one piece of evidence, one closing line. Time it at under 90 seconds out loud. |
| Criticising your current employer as the reason you're leaving — "the management there is a mess". | State the pull, not the push: name the thing this job has that yours doesn't, and leave your current employer out of it. |
| Using a detail that's out of date or wrong, like a product they discontinued or an office they closed. | Check the date on anything you quote, and frame it tentatively — "as I understand it" — so a correction becomes a conversation rather than a stumble. |
Your answer checklist
Run your draft against these five before the interview. If any one is missing, the answer will sound generic no matter how enthusiastic you are.
- One specific thing about this employer that a competitor could not also claim — a product, a client base, a location, a size, a way of working.
- One thing from the job description itself, described as a responsibility rather than a title, so they can hear that you read past the headline.
- One piece of evidence from your own experience that connects to that responsibility: something you did, with enough detail that it sounds like a memory rather than a claim.
- An honest note on the gap, if there is one — the skill you'd be learning, the system you don't know yet — because naming it yourself is more convincing than hoping nobody asks.
- A closing line that looks forward, covering what you'd want to be doing in the first few months. It answers the unspoken question about whether you'll stay without you having to promise anything.
Frequently asked questions
When in the interview does this question usually come up?
Most often in the first few minutes, right after "tell me about yourself", and again at the screening stage with a recruiter. Some panels save it for the end as a softer closing question, and some skip it entirely and ask "what do you know about us?" instead. Prepare two lengths: a 20-second version for a phone screen, where the recruiter is checking you're not applying to everything, and the full version for the hiring manager, who wants the evidence. If it comes up late in a long interview, trim it — by then they've heard your examples and only need the "why here" part.
How long should the answer be?
Roughly 45 to 90 seconds, which is about 120 to 180 spoken words. Under 20 seconds reads as indifference; over two minutes and you're using time you'll want later for your strongest examples. The reliable test is to record yourself and listen back: if you can't say what the single anchor was after hearing it once, it's too long or too vague. Cut the adjectives first — they're where the padding usually lives.
What follow-up questions come after it?
Expect at least one of: "What do you know about what we do?", "Why this role rather than the one you're in?", "What else have you applied for?", and "What concerns you about working here?". The last one catches people out after a glowing answer. Have one honest, non-fatal concern ready — a commute, an unfamiliar system, the scale of the team — framed as a question you'd want answered rather than a dealbreaker. If they ask where else you're interviewing, a general answer is fine: the type of role and stage you're at, without naming other employers.
What if the real reason is the pay, the location or the schedule?
Those are legitimate reasons, and interviewers know they exist — but they shouldn't be the opening line, because they say nothing about whether you'll be good at the job. Lead with the work, then it's fine to add a practical reason as a supporting point: a predictable shift pattern, a commute that works, a site near family. On pay specifically, whether a range appears in the posting varies by employer and by state, since pay transparency rules differ across the US and other countries. Check the posting first, then ask the recruiter directly at screening stage rather than folding it into this answer.

Written by
Desmond Okafor
Desmond talks to people mid-career about what their jobs actually look like day to day, past the job description. He's suspicious of any career advice that sounds too tidy.



