How to answer · Updated May 11, 2026

Why do you want to work here?

The complete answer guide: what this question really tests, two example strong answers in different angles, the common weak answer rewritten, and the trap most candidates fall into. This is a why this company / role archetype question — see the broader pattern guide for the structural shape.

What this question is really testing

The interviewer isn't asking whether you want the job—they already know you do, or you wouldn't be sitting there. What they're actually measuring is whether you've done your homework and whether your career motivations align with what this specific role will actually entail. They're looking for evidence that you understand what makes this company different from its competitors, what problems this team is solving, and why those particular challenges excite you. The binary read is simple: did you spend 30 minutes researching us, or are you copy-pasting the same answer across 50 applications?

The deeper concern is retention and motivation. Hiring is expensive, and the interviewer is trying to predict whether you'll still be energized six months in when the novelty wears off. Generic enthusiasm ("I've always admired your company!") signals that you're chasing a brand name or a paycheck, which means you'll leave the moment a shinier opportunity appears. Specific enthusiasm ("I noticed your team rebuilt the recommendation engine last quarter, and the technical approach in your engineering blog post on embeddings is exactly the kind of problem I want to spend my time on") signals that you understand the actual work and have genuine reasons to stick around when things get difficult.

Two strong answers, two angles

Angle A: Mission-driven with specific evidence

"I've been following your work in climate tech for about a year, specifically since your Series B when you announced the partnership with industrial manufacturers. What excites me is that you're not building consumer apps that help people feel good about sustainability—you're actually reducing emissions at the source where 80% of the problem lives. I spent three years at a logistics company optimizing supply chains, and I saw firsthand how hard it is to get enterprises to change their operations. The fact that you've signed six Fortune 500 companies in 18 months tells me you've figured out the change management piece, not just the technology. That combination of impact and execution is exactly where I want to focus the next phase of my career."

Angle B: Skills-match with company inflection point

"You're at an inflection point that maps perfectly to what I do best. I saw that you grew from 8 to 40 customers in the last year, and your Series A deck mentioned expanding to mid-market accounts. I've built that exact playbook twice—at my last company, I was the third sales hire and created the first repeatable process for mid-market deals, which became the template as we scaled from $2M to $15M ARR. I thrive in that 'figure it out' stage where there's enough traction to prove the model works, but everything still needs to be systematized. Looking at your team page, it seems like you're still in that phase where the founders are on sales calls, and I'd love to be the person who helps you transition from founder-led to process-led sales."

The common weak answer

"I've always admired your company's culture and values. You're a leader in the industry, and I think this would be a great opportunity for my career growth. I'm really passionate about what you do here, and I think my skills would be a great fit for the team."

This answer fails because it's completely interchangeable—you could deliver this exact response to any company in any industry. The interviewer hears: "I didn't research you, I need a job, and I'm hoping you'll just move on to the next question." The phrase "great opportunity for my career growth" is particularly damaging because it frames the company as a stepping stone for your ambitions rather than positioning you as someone who will solve their problems. Even worse, "passionate about what you do" without any specifics signals that you don't actually know what they do beyond what's on the homepage. A simple reframe: replace "I've always admired your culture" with one specific cultural artifact you noticed (a blog post, a product decision, how they handled a PR crisis) and explain why that particular example resonates with your work style.

The one trap most candidates fall into

The trap is complimenting the company when you should be complimenting the work. Candidates think they're supposed to flatter the interviewer by praising the brand, the reputation, or the prestige. So they say things like "You're the best in the industry" or "Everyone knows you're the market leader" or "I've wanted to work here since college." This backfires because it makes you sound starstruck rather than discerning. The interviewer doesn't want someone who wants to work anywhere at their company—they want someone who specifically wants to do this job on this team solving these problems.

The fix is to go one level deeper than the company to the actual work artifact. Don't say "I love your product"—say "I've been using your API for a side project, and the way you handle rate limiting is more elegant than any other service I've integrated." Don't say "Your marketing is brilliant"—say "Your recent campaign repositioning from a feature to a workflow solution is exactly the kind of strategic shift I helped execute at my last company, and I want to keep working on that level of problem." The specificity proves you've engaged with their actual output, not just their reputation, and it gives the interviewer concrete evidence that you understand what you'd be walking into.

Common questions

How long should my answer to "Why do you want to work here?" be?

Aim for 60-120 seconds spoken (250-350 words). Long enough to land the situation, action, and result; short enough that the interviewer has room to follow up. Anything past two minutes risks losing them.

Should I memorize my answer word-for-word?

No — that reads as canned and falls apart the moment the interviewer asks a follow-up. Memorize the structure (the bones of the story) and the specific numbers/names that anchor it. Let the words come naturally each time.

What if I have a really good story but it was years ago?

Recent is better, but a strong story from 3 years ago beats a vague story from last quarter. If the example is older than 5 years, frame it as the moment that crystallized the lesson, then briefly bridge to how you've applied it since.

Can I use the same story for multiple questions?

Often yes — strong stories tend to demonstrate multiple competencies. The trick is reframing the angle each time. Same situation, different opening sentence: lead with the conflict for conflict questions, lead with the leadership move for leadership questions.

How do I know if my answer is actually good?

Practice it out loud and have it scored. The fastest way is a mock interview where the AI flags exactly what's vague, where you used 'we' when the question asked about 'I,' and rewrites the weakest sentence. Reading example answers helps; getting yours scored is what moves performance.

Reading isn't practicing.

Try answering this question right now before checkout, with real Claude-scored feedback in 5 seconds.

Practice this question free →
How to answer: Why do you want to work here? (2026 guide) — InstantInterviewer