How to Answer "Why Do You Want to Work Here?"
The short answer
Give one specific reason about the company, one about the role itself, and one about what you bring. Name something concrete you could only know by researching them — a product decision, a technical problem, the stage they are at — then explain why your experience fits it. Aim for 45 to 60 seconds.
This is the question that separates candidates who researched the company from candidates who applied to forty of them. Here is how to answer it without flattery.
Or skip ahead and have your answer scored — free, no account needed.
Why interviewers ask “Why do you want to work here?”
Hiring is expensive and people who take a job for want of a better option leave within a year. The interviewer is checking whether you have an actual reason to be in this conversation, and — quietly — how much effort you put in before showing up. It is also one of the easiest questions to prepare and one of the most commonly fumbled, which means a good answer stands out more than it should.
What they are actually listening for
- Did you research us, or could this answer be pasted into any application?
- Do you understand what the company actually does, including how it makes money?
- Are you drawn to the work itself, or only to the title, the salary, or the logo?
- Is what you want from us something we can realistically give you?
- Have you connected your own experience to our problem, or just praised us?
The structure to use: Them - The role - You
The mistake almost everyone makes is answering only the first third: a paragraph of praise for the company and nothing about the job or themselves. A complete answer moves through all three, in this order, and takes under a minute.
Name one specific thing about the company
~20 secondsLead with a concrete detail you could only know from research — a product decision, a technical approach, their market position, a recent change.
Specificity is the entire test. "You are a leader in the space" fails it; "you moved billing in-house last year, which is an unusual call at your size" passes it. Good sources are the company blog and engineering blog, recent funding or earnings news, the product itself (use it if you can), and the job description, which usually leaks the team's real priorities.
Say why the role is the one you want
~20 secondsExplain what about this particular position fits what you are looking for next: the scope, the problems, the stage, the team.
This is where you show you read past the job title. Point at something in the description — ownership of a specific system, a greenfield build, being the first hire in an area — and say plainly why that is what you want now. It also quietly answers "why are you leaving?" before it is asked.
Close with what you bring to it
~15 secondsConnect one piece of your experience directly to the problem you just described, so the answer ends on value rather than on wanting.
One sentence. "I have done exactly this migration once before, and I would like to do it again somewhere the stakes are higher" turns an answer about your motivation into an answer about their outcome. Without this beat, a good answer still sounds like you asking for something.
Example answers to “Why do you want to work here?”
These are written to be spoken, not read. Do not memorise them — take the shape and put your own experience through it.
Example 1
Software engineer
Interviewing at a mid-stage infrastructure company
The thing that got my attention was your post about moving off the managed queue and building your own delivery layer. That is an unusual decision at your size, and the reasoning in the write-up — that you needed ordering guarantees the vendor would not commit to — is the kind of trade-off I enjoy arguing about.
The role itself is the other half of it. I have spent three years as one of several engineers on a mature platform, and this is a chance to own a system end to end while it is still being shaped. That is the scope I am looking for next.
And it is close to what I have already done: I ran the migration from Rabbit to Kafka at my current company, including the six months of dual-writing nobody enjoys. I would rather do that again somewhere it matters more.
Why it works
- Opens with a detail that proves real research and could not be recycled for another employer.
- Engages with a technical trade-off rather than complimenting the company.
- The role paragraph doubles as an honest answer to "why are you leaving?".
- Ends on relevant experience, so the answer closes on value rather than desire.
Example 2
Product manager
Interviewing at a consumer fintech app
I have been using the app for about eight months, and the thing I keep noticing is that you say no to features other people would have shipped. There is no crypto tab. The savings flow is four screens. That restraint is rare and it is usually a sign the product team has actual authority.
The role appeals because it is the first dedicated PM on retention. I have spent two years doing retention work as one of four things I owned, and I want it to be the whole job — particularly somewhere the underlying product is good enough that retention is a solvable problem rather than a symptom.
The most relevant thing I have done is rebuilding an onboarding flow around a single activation metric, which moved week-four retention from eleven to nineteen per cent. That is the shape of work I would want to start with here.
Why it works
- Shows the candidate actually used the product and formed a view about it.
- The observation is about a decision, not about the brand, which is much harder to fake.
- Names why this role specifically fits their trajectory.
- Closes with a measurable, directly transferable result.
Common mistakes (and the fix)
Praising the company in ways that fit any company
"You are an industry leader with a great culture and I love your mission" contains no information. Interviewers hear it several times a week and read it as a lack of preparation.
Fix: Replace every generic compliment with a specific fact. If your sentence would still be true of three competitors, cut it.
Making it entirely about what you get
Answers built on career growth, learning opportunities, and a step up in scope are about your needs. They are fair reasons, but on their own they give the interviewer nothing about why hiring you is a good idea.
Fix: Keep the growth reason, but always close on what you bring to the problem you just described.
Leading with pay, benefits, or remote policy
These are legitimate and you should absolutely check them, but leading with them signals the work itself is secondary and hands the interviewer an easy reason to doubt your commitment.
Fix: Save compensation and logistics for when you ask questions, or for the recruiter conversation where they belong.
Repeating the "About us" page back to them
Reciting the mission statement proves you visited the website, nothing more. Everyone in the room already knows what it says.
Fix: Go one layer deeper: the engineering blog, a recent product change, their pricing page, an earnings call, or the product itself.
Getting a basic fact wrong
Naming the wrong product, the wrong market, or a competitor's feature ends the answer instantly and is remembered longer than anything else you say.
Fix: Check the two or three facts you plan to cite the morning of the interview. Companies change quickly.
Free · no account needed
Say your answer out loud. Get it scored.
Reading about the structure is not the same as saying it. Answer “Why do you want to work here?” the way you would in the room, and get a score plus three specific fixes. Aim for 45-60 seconds (roughly 110-150 spoken words).
This browser cannot record audio. .
Practise the other nineteen questions too
“Why do you want to work here?” is one question. Paste the actual job posting and your CV and prepare.fyi generates the twenty questions that company is most likely to ask, then lets you answer them out loud — with a live AI interviewer and a scored breakdown of every answer.
“Why do you want to work here?”: frequently asked questions
- What if I mainly want the job for the money or the title?
- That is a normal reason and you do not have to pretend otherwise, but it is not the answer to this question. Find the part of the work you would genuinely choose — the problem, the product, the scope, the people — and lead with that. If you honestly cannot find one, that is useful information about whether to take the job.
- How much research is enough?
- Thirty focused minutes is usually plenty: the product itself, the careers or engineering blog, the last two or three pieces of company news, and the job description read closely. You need two or three specific facts you can cite confidently, not a full briefing.
- Is this the same as "why are you interested in this role?"
- Close, but the emphasis moves. "Why this company" wants the company reason first; "why this role" wants the job reason first. The same three beats work for both — just lead with whichever one they asked about and keep the other two.
- What if I am applying to a company nobody has heard of?
- That usually makes the question easier, because a small company gets fewer researched answers and notices immediately when they get one. Use the product, the founders' public writing, the funding stage, and the job description. Being early is itself a legitimate specific reason if you say why you want that.
- Should I mention someone I know who works there?
- Yes, if it is true and you have actually spoken to them. "I talked to X on the platform team and what she said about how you handle on-call is a large part of why I applied" is strong, specific evidence. Name-dropping someone you have not spoken to is a bad risk in a small industry.
Practise the next question
Opening
“Tell me about yourself”
It is the first question in almost every interview, and the one most candidates waste. Here is the structure, three full example answers, and a way to practise yours out loud right now.
Compensation
“What are your salary expectations?”
The first person to name a number usually loses a little ground. Here is how to deflect without sounding evasive, and what to say when deflecting stops working.
Self-awareness
“What is your greatest weakness?”
Everyone knows "I am a perfectionist" is a non-answer, including you. Here is how to give a real one without damaging your candidacy.
Behavioral
“Tell me about a time you failed”
The trap is choosing a failure so small it proves nothing. Here is how to pick one that is real, tell it in ninety seconds, and come out of it looking better.