How to Answer Why Do You Want to Work Here

Answer “Why do you want to work here?” by connecting one specific fact about the company or team, one part of the role you genuinely want to do, and one strength you can use there. Keep it to roughly 30 to 60 seconds. You don’t need to claim the company has been your lifelong dream; you do need to show that your application was deliberate.

What is the interviewer really asking?

The wording sounds like a request for praise, but the useful question underneath is simpler: “Why does this particular match make sense?” The interviewer is listening for evidence that you understand the job, have a credible reason to want it, and can contribute after you arrive.

That means a good answer has to cover both sides. Talk only about what you want and you can sound as though the company is a convenient stop. Talk only about how wonderful the company is and you can sound rehearsed. The strongest answer joins your interest to their need.

Interviewers may phrase it as “Why do you want to work for us?”, “Why are you interested in this role?” or “Why this company?”. Treat those as the same core prompt unless the wording clearly focuses on the position rather than the organization.

What three parts should your answer include?

Use this compact structure:

1. Name one real reason the company, product, team or problem interests you.
2. Connect that reason to a responsibility in the job description.
3. Show how a relevant skill or past result would help you contribute.

The order matters because it moves from their world to the job and then to your evidence. You might say: “I noticed your customer team is moving from reactive support toward customer education. This role would let me build the onboarding materials and workshops I most enjoy creating. In my current position, I rebuilt the first-month email series and worked directly with support to answer the questions new customers asked most often.”

The example doesn’t rely on vague claims about culture. It points to an observable direction, names the work, and gives the interviewer a reason to believe the candidate can do it.

How do you find a specific reason in ten minutes?

Start with the job description, not the company’s mission page. Mark two responsibilities you’d be happy to spend real time doing and one problem the new hire probably needs to solve. Then look at the company’s product pages, recent newsroom posts, team page or public engineering and marketing posts for evidence that connects to those responsibilities.

You’re looking for one usable fact, not a company history lesson. A product launch, a new customer group, a technical migration, a change in how the team works, or a clearly stated value can all work if you can explain why it matters to the job. Avoid repeating a slogan without adding your own connection.

Check that your chosen fact is current enough to mention. If the only evidence is an old announcement, frame it as background rather than something happening now. If you can’t verify a company claim, stay with what the job description tells you about the role.

Finally, say the answer aloud once. If any sentence could be used for fifty other employers, replace it with the company fact, job responsibility or personal evidence you found. This quick specificity test does more for your answer than adding extra enthusiasm.

What if you are interested in the role but not the company?

You can be honest without saying “I just need a job”. Most candidates aren’t devoted fans of every employer they meet. Pick the strongest truthful point of interest: the work itself, the customer problem, the chance to use a skill at greater scale, the team’s operating style, or the responsibilities you want to own.

For a company you feel neutral about, a grounded answer could be: “What caught my attention was the role’s mix of account analysis and direct client work. I like finding the pattern behind a customer problem and then explaining the fix in plain language. I’d bring experience doing that across a busy portfolio, and I’d like to learn how your team handles larger accounts.”

That answer doesn’t pretend the company’s mission changed your life. It still proves that you read the role, understand the work and have a reason to continue the conversation. Genuine interest in the job is enough when you express it specifically.

Don’t invent a personal connection to the product, repeat values you don’t share, or claim that the employer is your first choice if it isn’t. A polished lie becomes fragile as soon as the interviewer asks, “What specifically impressed you?” A modest truth is easier to defend.

How should answers change for different roles?

A software engineer should focus on the technical problem, the product constraint or the way the team builds. For example: “I’m interested in the reliability work mentioned in the posting because I’ve spent the past two years reducing failures in payment services. The chance to work on a larger transaction volume appeals to me, and I could bring the incident-review process I used to help my current team catch repeat issues.”

A product manager can connect a customer problem to cross-functional work: “Your move into tools for small finance teams stood out because those users have little time for setup. I enjoy turning messy customer feedback into a clear product decision. In my last role, I worked with design, engineering and support to simplify an onboarding flow, so the mix of discovery and delivery here feels like a strong fit.”

For sales, show that you understand the buyer and can create value: “I’m drawn to the consultative part of this role. Your customers seem to be choosing between keeping a manual process and changing how their team works, so the conversation is bigger than a feature demo. I’ve sold into a similar decision and learned how to build agreement across operations and finance.”

If your first conversation is a phone screen, make the company connection early because the recruiter is checking basic motivation and fit. Our phone screen interview tips explain how to prepare a short answer and sound ready without reading a script.

How long should your answer be?

Aim for three to five sentences, usually 30 to 60 seconds when spoken naturally. That gives you enough room for the company detail, the role connection and your evidence without turning the answer into a speech.

If the interviewer opens with this question, choose the shorter version. You’ll have time to add detail later. In a final round, you can refer to something you learned in earlier conversations: “After speaking with the support lead, I’m even more interested in how this role brings product feedback into weekly planning.” That shows your interest grew from the actual process.

Write a full version during practice, then reduce it to three prompts rather than memorizing every word. Memorized paragraphs often sound flat and can collapse if the interviewer interrupts. Three prompts keep the logic in place while letting your delivery remain conversational.

What weak answers should you avoid?

“The company has a great reputation” is incomplete because it never says what the reputation is for or why that matters to you. “I’m ready for a new challenge” focuses on your need while leaving the employer out. Salary, benefits, remote work and location may be sensible reasons to consider a job, but they shouldn’t carry this answer because they don’t explain your interest in doing the work.

Another common mistake is giving a second version of “Tell me about yourself”. Your career summary can support the final part of the answer, but it shouldn’t replace the company and role connection. Choose one relevant proof point instead of reciting your background.

Watch for exaggerated words such as “dream”, “perfect” and “passionate” when they aren’t true. Calm specificity sounds more credible than oversized enthusiasm. The interviewer needs a reasoned match, not a performance.

What should you say if they ask a follow-up?

The most likely follow-up is “What about our company interests you specifically?”. Answer by expanding the evidence you already named. Explain where you found it, what you understood from it and how it connects to the job. If you mentioned a public product change, be ready to discuss the customer problem rather than pretending you know the internal strategy.

If they ask “Why us instead of a competitor?”, don’t criticize other employers. Compare on the dimension that matters to your work: customer type, product stage, team ownership, technical problem or learning opportunity. You can say, “I’m speaking with a few good teams, but this role gives the person direct ownership of onboarding rather than splitting it across several functions. That scope matches the work I want to do.”

If new information changes your view during the interview, use it. A thoughtful response can begin, “What I’ve heard today adds another reason”. Then point to a specific project or team practice the interviewer described. This makes the answer feel present rather than preloaded.

How can you practise without sounding scripted?

Prepare three versions: a 20-second opener, a 45-second normal answer and a longer version with one extra example. Don’t write three separate speeches. Use the same three-part logic and vary the detail.

Record one practice attempt and listen for generic phrases, rushed delivery and sentences that are too long to say comfortably. Replace any vague praise with a fact. Cut any background that doesn’t help explain the match. Then practise once with a follow-up so you’re ready to move beyond your opening answer.

If you expect several interviewers, decide which proof point will make sense to each audience. A hiring manager may care about the work you can own, while a senior leader may listen for the broader customer or business problem. The advice in our panel interview guide can help you keep one clear answer while adjusting the detail for the person who asked.

You can also rehearse with a live prompt instead of staring at notes. Hiintly can listen during a practice call and surface resume-personalized suggestions, which helps you test whether your key points are easy to use under pressure. A free 10-minute session is enough to see how it feels live.

What is a strong final template?

Use this as a planning frame, then replace every bracket with something true: “I’m interested in [specific company, team or product fact] because [honest reason it matters to you]. The chance to [important responsibility] matches the work I most want to do next. In [relevant situation], I [action and useful result], and I’d be excited to bring that experience to this team.”

Read it once and ask three questions. Could this answer belong to another company? Does it name work you genuinely want? Does the proof point show what you can contribute? If the answers are no, yes and yes, you’re ready. Pair that preparation with a few questions to ask the interviewer so you can test whether the role matches the reasons you just gave.