"Why Do You Want to Work Here?" How to Answer (With Examples)

The short answer: name one specific thing about this company that you couldn't say about its competitors, say why it matters to you, and connect it to what you'd do in the role. Three sentences, about 30 seconds. "Your mission is inspiring" and "it's a great company" are the answers interviewers hear all day and forget immediately, because they could be said about anywhere. The answer that works proves you looked, and shows you'd want this job even if the one across the street paid the same.

The rest of this guide is the formula, a 20-minute research routine that gives you the specific detail, four example answers, and the things that quietly sink this question.

What they're actually asking

On the surface it's about the company. Underneath, the interviewer is checking three things:

1. Did you do any homework? People who researched the company before the interview usually researched the role too. People who didn't are often applying everywhere.
2. Is there a real fit, or just a job? Everyone needs a job. They want to hear why this one, because a reason is what keeps people from leaving in eight months.
3. Do your reasons match what the job actually is? If you say you love their creative culture and the role is quarterly compliance reporting, that mismatch is a flag.

Notice what isn't on the list: flattery. Interviewers don't need to hear that the company is great. They need to hear that you know what it does and want to do it with them.

The three-part answer

1. Something specific about them. A product, a customer group, a recent decision, how they work, something the hiring manager said in an earlier round. It has to be something you couldn't paste into an answer for a competitor.

2. Why that matters to you. One sentence that ties it to your own work or what you want next. This is where the answer stops being research and starts being a reason.

3. What you'd bring to it. A short bridge to the role: the skill or result from your background that fits what they're doing. It turns "I like you" into "I'd be good at this here."

That's the whole structure. Keep it to three or four sentences. Long answers to this question start to sound rehearsed.

“The answer to 'why do you want to work here' has to fail one test: you couldn't say it about their competitor. If you could, it isn't a reason yet.”

Share on X→

Twenty minutes of research that's enough

You don't need a deep dive. You need one or two true, specific things. In order of usefulness:

• The job posting itself. Reread it for what they emphasize, the problem the role exists to solve. The best answers often come straight from here: "the posting talks about rebuilding the onboarding flow, and that's the kind of project I've done twice."
• Their own news from the last six months. The company blog, press page or LinkedIn page: a launch, an expansion, a new market, a change in how they work. Recent beats impressive.
• The product, as a customer. Sign up, use it, read the reviews. "I've been using it for a week, and the onboarding was the smoothest I've seen in this category" is worth more than any mission statement.
• The people. Look up your interviewers and a couple of people in the team on LinkedIn. What they post about tells you what the team cares about right now.
• What a previous round told you. If a recruiter or manager already described the team, quote them back. "When Dana mentioned the team owns the whole customer journey, that's what made me more interested" is specific and flattering in the right way.

Write down two specifics. Use one in your answer and keep the other for a follow-up.

Four example answers

Adapt these; don't recite them. The specifics are the point, and yours will be different.

An experienced candidate, same industry:

"Mostly it's the move into small-business customers. I've spent four years on the enterprise side of payroll software, and the thing I always wanted to fix was how long setup takes for a 20-person company. Your push into that segment this year is exactly that problem, and it's the part of my work I'm proudest of: I cut implementation time from six weeks to ten days at my current company."

A career changer:

"I've been a teacher for six years, and the reason I'm moving into learning design is that I want to build training that reaches more than thirty people at a time. Your customer academy is the best example of that I've found. It's built like a real course, not a help center, and I'd like to help build the next version of it. I've been designing my district's new-teacher onboarding for two years, which is the same job at a smaller scale."

A new graduate:

"Two reasons. I used your app all through my final year to manage a group project, so I know the product from the user side, which most applicants won't. And the rotational program means I'd see support, product and sales in the first year, which is exactly how I want to start: I know I like this industry, and I want to find out where in it I'm most useful."

Someone who knows the company less well, after a recruiter call:

"Honestly, the call with Priya last week is what moved this to the top of my list. She described a team that ships small and often and measures everything, and that's how I've worked best. The posting's focus on retention over acquisition fits too. Most of my results in the last two years were churn reductions, including a 4-point drop at my current company."

All four follow the formula: something only true of this company, why it matters to the person, and a bridge to what they'd bring.

What to leave out

• Salary, benefits, location, remote work. They may well be real reasons, but leading with them says you'd leave for a better package. Save them for the offer.
• Generic praise. "Great culture," "industry leader," "I love your mission." Fine as a single clause, never as the answer.
• Their own website read back to them. Quoting the "About us" page word for word is the same as saying nothing.
• "I need a change" or anything about your current employer. That's an answer to a different question, and it pulls the conversation toward why you're leaving.
• Things you can't back up. If you say you love their product, be ready for "what do you use it for?"

Variations of the question

The same answer works, with a small adjustment, for all of these:

• "Why this role?" Lead with part three (what you'd bring) and keep part one short.
• "Why us and not [competitor]?" Name the real difference, kindly. Never criticize the competitor; say what's specifically different here.
• "What do you know about us?" Start with your two research points, then turn it into why they matter to you.
• "Where else are you interviewing?" Different question. You can say you're talking to a few companies in the space, then come back to why this one is high on your list.

If it comes up in the phone screen, the recruiter is mostly checking you know what the company does. A two-sentence version is enough there; save the full answer for the hiring manager.

When they push back

Good interviewers sometimes follow up: "Lots of companies are doing that. Why us specifically?" That's your second research point. It's also why you write down two: the first answer opens the door, and the second proves the first wasn't a guess.

The short version

• One specific thing about them, why it matters to you, what you'd bring. Three or four sentences.
• Twenty minutes of research is enough: the posting, their recent news, the product, the people.
• Write down two specifics, use one, keep one for the follow-up.
• Leave out pay, perks, generic praise and anything about your current job.
• If you could say the same answer to their competitor, it isn't finished yet.

This question is one of the twelve that come up in nearly every interview, and it usually lands right after tell me about yourself. If the interview is already booked, the Interview Dossier builds your prep for that one role from your resume and their posting, including the questions your background is most likely to attract. And when it's your turn at the end, these are the questions worth asking.