A three-part structure, five worked answers for different career stages, and the fixes for an answer that could be about any employer.
By the end of this guide you'll have a 60-to-90-second answer to "Why do you want to work here?" built from three parts: one specific reason tied to this employer, the parts of the role you actually want, and one piece of evidence that you can do them. You'll also know the variants of the question, the follow-ups that usually come next, and the five mistakes that make an answer sound generic.
The examples below cover a new graduate, a step up in the same field, an industry switch, a career change and a return after a gap, so you can see what the structure looks like when the raw material is different.
Why interviewers ask it
Three competencies are on the table. The first is preparation: did you research the employer, or are you reading the mission statement off the wall behind them? The second is motivation specific to this employer and this role, rather than wanting any job that pays. The third is retention risk — whether you're likely to stay long enough to be worth training (Resume.io, undated; CV-Review.com, undated). One guidance note from MIT Career Education & Professional Development (2023) frames a good answer as covering why this company, why this position, and why you'll succeed in it.
How heavily it's weighted varies. A hiring manager at a small company may use it as conversation. A structured panel — common in US state and federal agency hiring — may score your answer against the duties in the posted announcement, so tie your reasons to those duties explicitly.
Other ways you'll hear it
The same question wears several names, and each phrasing leans on a different part of your answer — company, role, or you (Frontline Source Group, undated):
- "Why this company?" — leans on your research
- "Why do you want this job?" — leans on the role itself (Indeed Career Guide, undated)
- "Why are you interested in this position?" (Indeed Career Guide, undated)
- "Why are you interested in this job?" (Robert Half, undated)
- "What attracted you to this role?"
- "Why us rather than our competitors?" — a harder variant that usually arrives as a follow-up
Treat them as one question with a shifted emphasis. Have all three parts ready and lead with whichever the phrasing asks for.
How to build your answer
Use the Company + Role + Fit formula: one specific reason tied to the employer, the responsibilities that appeal to you, and how your skills and experience match (InstantDocsAI, undated; CV-Review.com, undated).
- Research before you write anything. Read the employer's own website — mission, goals and current priorities — alongside the job description (CareerOneStop, U.S. Department of Labor, undated). Look for something concrete and recent: a new site, a product line, a published report, a service they run. You need one detail you could not have guessed.
- Pick one company reason and make it checkable. "Great culture" is not checkable. "You publish your water quality reports and I used three years of them" is. One strong reason beats three vague ones, and it proves the research without you announcing that you did any.
- Name the parts of the role you want. Go to the duties in the posting and say which ones you're reaching for. This separates wanting this job from wanting a job, which is exactly what the interviewer is testing (Resume.io, undated).
- Prove the fit with one compressed example. Supporting your interest with a concrete piece of past work makes it credible. The STAR method — Situation, Task, Action, Result — works, and the PAR method (Problem, Action, Result) is a tighter version suited to short, outcome-focused answers (Frontline Source Group, undated). In a 90-second answer, PAR usually fits better.
- Point forward. Add one line on where this role leads for you — role fit to your strengths, company fit to the researched detail, future fit to your direction (InterviewPilot, undated). This is the part that answers the retention question they haven't asked out loud.
- Say it aloud and time it. Practising answers aloud, and working out how you meet each job requirement before the interview, is standard preparation advice from CareerOneStop (U.S. Department of Labor, undated). Trim until it runs 60–90 seconds without rushing.
Your answer checklist
A good answer includes all five of these:
- One researched detail about this employer that you could not have guessed from the industry alone, drawn from their own site, job description or announcements (CareerOneStop, U.S. Department of Labor, undated)
- The specific parts of the role you want, named from the duties in the posting rather than described in general terms
- One piece of evidence — a short Problem–Action–Result example — showing you've already done something like it (Frontline Source Group, undated)
- A forward-looking line connecting the role to where you're heading, which quietly answers the retention question (InterviewPilot, undated)
- A runtime of 60 to 90 seconds, practised aloud rather than read (Resume.io, undated)
Frequently asked questions
When in the interview will this question come up?
It can arrive early, as a tone-setter right after the small talk, or near the end, where it's used to confirm your interest and enthusiasm before you leave (Robert Half, undated). Prepare for both. Asked early, keep it tight and let the detail come out later in the conversation. Asked at the end, you can reference things you learned during the interview itself — a project the hiring manager described, a problem the team mentioned — which is more convincing than anything you could have prepared. Where it falls also depends on the format: a structured panel, common in US public-sector hiring, usually asks questions in a fixed order from a script, while a hiring manager running an informal first-round call may drop it in wherever it fits.
How long should the answer be?
Roughly 60 to 90 seconds is the usual recommendation (Resume.io, undated). Another way to put it: aim for about a minute and never go past two (Frontline Source Group, undated). That's enough for three beats — one company reason, the parts of the role you want, one short piece of evidence — and not enough to start listing. If you're over, the fix is almost always to cut the second and third company reasons, not to speed up. Time yourself out loud once or twice; most people's silent read-through is considerably faster than their spoken answer.
What follow-up questions usually come next?
Expect the interviewer to press on whichever part you were thinnest on. Common follow-ups include what attracted you to this role over the others you applied for, what you know about the organisation's competitors, and where you see yourself in five years (CV-Review.com, undated). The competitor question is the one people get caught by: be able to name what this employer does differently, in a way that isn't flattery. For the five-year question, keep your answer pointed in the same direction as the forward-looking line in your main answer — if the two don't match, that's exactly the inconsistency they were probing for.
What if I applied because I need a job and the company doesn't stand out to me?
Then do the research now and find something real. Read the employer's own site for its mission, goals and current priorities, and read the job description properly (CareerOneStop, U.S. Department of Labor, undated); then work out how you meet each requirement before the interview (CareerOneStop, undated). Most organisations have at least one thing worth being specific about — a customer they serve, a process they run, a problem they're clearly trying to solve. You don't have to claim it's your dream employer. You do have to show you considered this one in particular rather than applying by the dozen, because wanting this specific job, rather than any job, is a large part of what's being tested (CV-Review.com, undated).