How to Answer 'Why Do You Want to Work Here?'

A professional preparing an interview answer

To answer "why do you want to work here?" well, you need three specific things: something real you know about them, the problem this role exists to solve, and one proof that you have solved that problem before. That is the whole answer. The enthusiasm, the compliments, the line about how you have always admired the company - that is decoration, and interviewers can hear decoration from across the table.

You have answered this question in every interview you have ever had, and you have probably answered it the same way every time: something about the company's reputation, its mission, the exciting moment it is in. It sounds fine. It is also the answer every other candidate gave that day, which means it does nothing to separate you - and it quietly tells the interviewer that you have not thought about the job as a job.

What the question is really testing

The interviewer is not asking whether you like them. They are asking three things at once. Have you done enough work to understand what this job actually is? Do you want this job specifically, or would any job do? And will you still be here in a year, or is this a stop on the way to something else? A generic answer fails all three at once, which is why it feels so flat in the room even when it sounds polished in your head.

The reframe: it is a fit question, not a flattery question

The answers that land are bridges, and a bridge has three spans: what you know about them, what they need, and what you have already done. The bridge only holds if all three are specific. "I admire your culture" is not a span. "You are rebuilding your onboarding flow after the acquisition, and I rebuilt a broken onboarding flow at my last company" is a bridge - and it is one sentence.

Step 1: Do the twenty minutes of research that makes the answer possible

You cannot answer this question without knowing something real, and you cannot fake knowing something real. Twenty minutes is enough if you spend it in the right places.

Their product or service, from the customer's side. Use it, read the reviews, read the pricing page. You are looking for one detail you could only know by paying attention.
Their most recent move. A launch, a new market, an acquisition, a leadership change, a public commitment. The last six months of news is where the specific reason usually lives.
The problem the role exists to solve. Read the posting again as a problem statement rather than a wish list, and write down the outcome they are hiring for.
The team and the person you would report to. Their remit, their recent work, the language they use. This is where you find the sentence that makes the interviewer look up.

If you want a structured version of this pass, the method in How to Research a Company Before an Interview walks through it in order.

Step 2: Name the problem the role exists to solve

Every posting is a problem statement in disguise. "Own the quarterly reporting cycle" means the reporting is slow or unreliable. "Partner with sales on pipeline hygiene" means the pipeline is messy. "Build the onboarding programme" means there is not one yet. Translate the responsibilities into the outcome they want, and say that outcome out loud in your answer. Naming their problem is the fastest way to sound like someone who has already started.

Step 3: Build the three-part bridge

Now assemble the answer. Three sentences, in this order, and no more than about forty seconds.

What I know about you. One specific, current, verifiable detail - not a compliment. "You have just opened the European market and you are hiring your first regional team."
What you need. The problem the role exists to solve, in your own words. "Which means someone has to build the process from scratch and make it work across two regulatory environments."
What I have done. One proof, with a result. "I did exactly that at my last company - I built the regional onboarding process for a team of nine and cut the time to first deal by half."

Notice what is missing: no adjectives about yourself, no summary of your career, no flattery. The answer is an argument, and the argument is that their problem and your proof are the same shape.

Step 4: Add the one reason that could only be true for this employer

Here is the test that separates a good answer from a memorable one. Read your reason out loud and ask: could I say this sentence about their closest competitor? If the answer is yes, it is not a reason - it is a category. "I want to work in a fast-growing company" is a category. "I want to work on the problem your European launch creates, because I have spent four years on exactly that problem" is a reason. One reason, specific enough that it could not be true anywhere else, is worth more than three paragraphs of enthusiasm.

Three scripts you can adapt

1. Moving to a similar role at a different company

"I have been doing this work for six years, and the part I keep coming back to is the messy middle - the point where a process exists but nobody trusts it. You are at that point with your reporting cycle, and that is the work I am best at. At my last company I took a reporting process that took nine days and got it to two, and the team actually started using it."

2. Changing fields

"I am moving from operations into product, and I am doing it deliberately. What I bring is the part most product hires do not have: I have been the person on the other end of the roadmap, so I know which decisions create work downstream. You are hiring for a product role that sits between engineering and the field team, and that is exactly the seam I have worked on for years."

3. An internal move

"I have been on this team for three years and I know where the friction is, because I have been living in it. The role you are hiring for owns the handoff between us and the support team, and that handoff is the thing I have been quietly fixing for a year. I want to do it with the authority to actually change it."

The three-part bridge worksheet

Build the answer in one pass, in this order. The three rows are the whole method.

Span	What goes in it	The test it has to pass
What I know about you	One current, specific, verifiable detail about the company.	Could you only know this by paying attention? A compliment fails; a recent move passes.
What you need	The problem the role exists to solve, in your own words.	Did you translate the posting into an outcome, or just repeat its responsibilities?
What I have done	One proof with a result attached.	Is it the same shape as their problem? If not, pick a different proof.

What good looks like

The answer is three sentences and about forty seconds long.
The first sentence names something real and current about the company.
The second names the problem the role exists to solve.
The third gives one proof with a result.
The reason passes the competitor test - it could not be true of anyone else.
No compliments, no resume recital, no mission statement.

Where people get stuck

Stuck because you do not know enough about the company yet. Twenty minutes in the right places is enough: their product from the customer's side, their last six months of news, the posting read as a problem statement, and the team you would join. One specific detail is all the first sentence needs.

Stuck because your reason sounds like everyone else's. That is the competitor test failing. Replace the category with a reason: not "fast-growing company" but "the European launch you are staffing right now", because you have done that exact build before.

Stuck because you are changing fields and the proof feels indirect. Name the seam instead of the gap. Find the part of the role that sits between your old field and the new one - the handoff, the translation, the shared problem - and show that you have already worked on exactly that.

Common mistakes

Complimenting instead of connecting. "You are a great company" is not a reason; it is a greeting.
Reciting your resume. They have it. This question is about them, not a second chance to summarise your career.
Answering with the company's mission statement. If your answer could be printed on their careers page, it is not yours.
Being honest about wanting any job. "I need a role that fits my skills" is true and fatal. Pick the specific reason and commit to it.
Naming a reason that is really about you. "You have great benefits" is a reason to accept an offer, not a reason to want the work.
Going long. Forty seconds is the target. A three-minute answer to this question reads as nervousness.
Not knowing what the company does. This is the one question where a shallow answer is immediately visible.

The follow-up they will ask next

Almost every interviewer follows this question with "and why are you leaving your current role?" The two answers have to agree. If you want this job because of the specific problem it solves, your reason for leaving should point in the same direction - toward the work, not away from a person. Keep it forward-looking, keep it short, and never criticise a former employer in the same breath.

A twenty-minute prep pass

Ten minutes: find one current, specific detail about the company and write down the problem the role exists to solve. Five minutes: write your three-part bridge in three sentences and read it out loud. Five minutes: apply the competitor test to your reason and cut anything that could be true of anyone else. That is the whole preparation, and it is the difference between an answer they forget and an answer they repeat to the hiring manager.

Where this fits

The research pass is the same one in How to Research a Company Before an Interview, and the proof you bring to the bridge is the match report in How to Answer 'Why Should We Hire You?'. The opening answer that sets up this one is in How to Answer 'Tell Me About Yourself', the questions you ask back are in Questions to Ask in an Interview, and the Interview Prep Roadmap sequences the whole set.

Start this week

Pick the role you want most and do the twenty minutes. Write the three sentences, say them out loud, and cut the reason that could belong to anyone. Then walk in and answer the question they actually asked - not the one everyone else answered.

Quick answers

Short answers to the questions this piece gets asked most.

Why do you want to work here?
Because of one specific thing: the problem this role exists to solve, and the proof you have solved it before. Name something real you know about them, translate the posting into the outcome they need, and give one result that shows you have done that exact work. Compliments are not reasons.

How do I answer this without sounding generic?
Apply the competitor test. Read your reason out loud and ask whether you could say the same sentence about their closest competitor. If you could, it is a category, not a reason. Cut it and replace it with something only true of this employer - a current move, a specific problem, a team you have actually studied.

How long should the answer be?
About forty seconds - three sentences. What you know about them, what they need, and what you have done. A three-minute answer to this question reads as nervousness, and the interviewer only needs the bridge.

What if I am changing fields?
Lead with the seam, not the gap. Name the part of the role that sits between your old field and the new one, and show that you have already worked on exactly that seam. The operations-to-product answer works because it names the handoff, not the ambition.

Read next:How to Answer Behavioral Interview Questions (No Scripts) — A story-bank method that beats memorized answers, with STAR built in.Video-First Interviews: How to Master One-Way and AI Screens — How to handle one-way video and AI-led screens without freezing on camera.Interview Silence: What "We'll Be In Touch" Really Means — What interview silence really signals, and the follow-up that revives it.

LaunchPath Careers tool: want to build this with structure instead of guesswork? LaunchPath Careers has a Interview Story Bank and a Interview Prep Roadmap. Start at LaunchPathCareers.com.

LaunchPath Careers by UFO Chaser® helps job seekers build a strategy-first job search. Learn more at LaunchPathCareers.com.

Search This Blog

Cosmo's Career Strategy Blog