---
title: How to Answer "Why Do You Want to Work Here?" (2026)
description: How to answer "why do you want to work here?" without generic flattery — a simple structure, real examples, and the mistakes that make interviewers tune out.
url: https://usegreenroom.app/blog/why-do-you-want-to-work-here
last_updated: 2026-06-25
---

← Back to blog

Interview prep

# How to answer "why do you want to work here?"

June 24, 2026 · 11 min read

![How to answer why do you want to work here — interview answer guide from Greenroom, the AI mock interviewer](/assets/blog/why-do-you-want-to-work-here-hero.webp)

The interviewer asks it with a small, knowing smile, because they have heard the answer four hundred times: *"So, why do you want to work here?"* And four hundred times they have heard some version of "You're a great company with a strong culture and I want to grow my skills" — a sentence so generic it would work equally well for a bank, a bakery, or a nuclear submarine. They nod, write nothing, and quietly file you under "applied everywhere." You didn't give a wrong answer. You gave a forgettable one, which in a competitive process is worse.

"Why do you want to work here?" looks like a softball and is actually a filter. Learning **how to answer "why do you want to work here"** well is one of the highest-return things you can prepare, because almost everyone does it badly, which means a specific, genuine answer makes you stand out with very little competition. This guide gives you the structure, real examples, and the exact mistakes to avoid.

## What the interviewer is really asking

Behind the friendly phrasing are three real questions the interviewer wants answered: **Do you actually know what we do, or did you mass-apply? Will you stay, or jump the moment something shinier appears? And do your motivations line up with what this role and company can realistically offer?** They are screening for genuine interest and fit, because a hire who is excited about *this* job specifically is more motivated, more likely to stick around, and cheaper than re-running the search in eight months.

This is why generic praise fails so completely: "great culture" answers none of those three questions. It doesn't prove you know what they do, it doesn't distinguish them from any competitor, and it doesn't connect to anything specific about you. The fix is specificity — and specificity comes from research. If you haven't done that groundwork yet, our guide on [how to research a company before an interview](/blog/how-to-research-a-company-before-interview) is the prerequisite for everything below.

## A simple structure for the answer

A strong answer to "why do you want to work here" has three parts, and you can assemble it in under a minute. Think of it as **them + you + the bridge**: something specific about the company, something true about you, and the connection between the two.

- **1. Something specific about them.** A product you've used, a recent launch or value, a problem they solve, a technical choice you respect. This proves you did the work. "I've been using your app for budgeting for about a year" or "I read about your move to a usage-based pricing model."
- **2. Something true about you.** Your relevant experience, a value you hold, a kind of problem you love working on. This makes it personal and impossible to copy. "I've spent the last two years on payments systems and I genuinely enjoy the reliability side."
- **3. The bridge.** Connect the two and point forward: why this company is where your thing and their thing meet, and what you want to contribute. "So a role building the payments platform at a company I already trust as a user is pretty much exactly what I was looking for."

That's it. Specific observation, genuine personal hook, forward-looking connection. It reads as a real reason, not a compliment, because it is one.

![A comparison table showing a generic forgettable answer versus a specific memorable answer to why do you want to work here](/assets/blog/why-do-you-want-to-work-here-diagram.webp)

*Generic vs. specific — the same question, two completely different impressions. Aim for the right-hand column.*

## Examples that work (and why)

**For a product company you admire:** "I've used your product for about a year, and the thing that stuck with me is how much care went into the onboarding — it's the rare app my non-technical parents actually figured out. I've spent my career on consumer-facing frontends and that obsession with making complex things feel simple is exactly the work I want to keep doing. So joining the team that builds that experience is genuinely appealing, not just a job."

Why it works: specific product observation (onboarding), genuine personal connection (consumer frontend career + a real anecdote), forward bridge (wants to keep doing this work, here). Nothing in it could be copy-pasted to another company.

**For a mission-driven company:** "You're tackling medical billing for small clinics, and that's not abstract to me — my sister runs a two-person practice and loses evenings to insurance paperwork. I've watched that problem up close. I want my work to remove that kind of friction for people, and you're one of the few companies actually building for that segment instead of the big hospital networks."

Why it works: it ties the mission to a true, specific personal story, and it shows the candidate understands the company's market position (small clinics vs. big hospitals) — research showing through.

**For a role-fit / growth angle (when you're early-career):** "Honestly, two things. The work itself — this role is building data pipelines, and that's the part of my last internship I kept volunteering for. And the team: I saw your engineering blog post on how you handle on-call, and that culture of writing things down and not blaming people is rare and exactly how I want to learn. I'd grow fast here, and I'd grow in the right direction."

Why it works: even the "growth" answer is anchored to specifics (data pipelines, a real blog post, a named cultural value), which keeps it from collapsing into generic "I want to learn." It also honestly fits an early-career candidate without faking deep mission alignment.

## Adapting the answer to your situation

### If you need the job and don't have a deep passion for it

You don't have to fake a calling. Anchor your answer to something genuinely true and specific that you *can* stand behind: the actual work, a skill you'll build, a value the company demonstrably has, the quality of the team. "I'm drawn to this role because it's hands-on backend work at real scale, which is exactly where I want to deepen, and from everything I've read your team takes engineering quality seriously" is honest and effective. Interviewers can smell manufactured passion; sincere specificity always beats it.

### If you're switching industries or roles

Lead with the bridge. Make the connection between where you've been and where they are the centerpiece: what transfers, and why their company is the right place to make the move. Tie it to a real reason you're switching, not a vague "new challenge." Our guide on [answering "tell me about yourself"](/blog/how-to-answer-tell-me-about-yourself-software-engineer) pairs well here, since the two answers should tell one coherent story.

## How this compares to how most people prepare

Most candidates "prepare" this answer by reading a list of sample answers on a careers blog and lightly memorizing one. The problem is that memorized sample answers are generic *by design* — they're written to fit any company, which is exactly the quality that makes them fail. A GeeksforGeeks-style "top HR questions" list or a generic ChatGPT answer gives you the *shape* of a good answer but none of the specific content, because the specifics can only come from your research and your real life. Worse, a memorized answer comes out stiff and recited, and "why do you want to work here" is precisely the question where sincerity is the whole point.

Here's the honest tradeoff. Reading examples (like the ones above) is useful for learning the structure — that's why they're here. But the answer only works when you fill the structure with *your* specifics and then say it out loud enough times that it sounds like you, not a script. That second part is where most prep stops and where [Greenroom](/) helps: it asks you "why do you want to work here?" in a real spoken mock, listens to your answer, follows up with "and what specifically about that appeals to you?" the way a real interviewer would, and flags when you've drifted into generic territory. It's the difference between having an answer and being able to deliver one. For more on the HR round overall, see our [HR interview questions guide](/blog/hr-interview-questions-answers).

## Mistakes that make interviewers tune out

- **Generic flattery.** "Great company, great culture, great people." If it fits any employer, it answers nothing. Cut every sentence that could be copy-pasted.
- **Making it all about you.** "This job pays well and is close to my house" may be true, but an answer purely about what *you* get signals you'll leave for the next raise. Balance your motivation with what you'll contribute.
- **Reciting the mission statement.** Quoting their tagline back at them is flattery, not understanding. Filter the mission through your own real experience instead.
- **Obvious research gaps.** Praising a product feature they discontinued, or getting their market wrong, is worse than saying less. Use current information.
- **Faking passion.** Over-the-top enthusiasm for a job you clearly need reads as inauthentic. Sincere, specific, and measured beats theatrical every time.

> **The core truth:** "Why do you want to work here?" rewards specificity, not enthusiasm. Combine one real thing about them, one true thing about you, and the bridge between — then say it out loud until it sounds like you. An answer that could fit any company answers nothing.

## Rehearse it out loud, with follow-ups

A great answer to "why do you want to work here" that you've only written down will come out clumsy the first time you actually say it — and the interviewer always has a follow-up ("what specifically?") that a written answer never prepared you for. The fix is to rehearse it spoken, against something that pushes back. [Greenroom](/) runs spoken mock interviews that ask the real HR and motivation questions, follow up on vague answers, and give feedback on how specific and genuine you sounded. Build your structure from this page, fill it with your research, and practise it until "why us?" becomes the easiest question of the day.

## Frequently asked questions

### How do I answer "why do you want to work here?"

Use a three-part structure: something specific about the company (a product you have used, a recent launch, a value), something true about you (your relevant experience or a problem you love solving), and the bridge connecting them with what you want to contribute. Specificity is the whole point — an answer that could fit any employer answers nothing, so anchor it to real, current details from your research and your own life.

### What is the interviewer really looking for with this question?

Three things: whether you actually know what the company does or mass-applied, whether you are likely to stay rather than jump to the next offer, and whether your motivations align with what the role can realistically offer. They are screening for genuine interest and fit, because someone excited about this specific job is more motivated, more likely to stay, and cheaper than re-running the hiring search later.

### What should I avoid when answering why I want to work here?

Avoid generic flattery that fits any company, making the answer entirely about what you get (salary, location), reciting the company mission statement verbatim, praising features or facts that are out of date, and faking over-the-top passion for a job you clearly need. Each of these signals either a lack of research or a lack of sincerity, and interviewers tune out fast when they hear them.

### How do I answer if I do not have a strong passion for the company?

You do not need to fake a calling. Anchor your answer to something genuinely true and specific that you can stand behind — the actual work, a concrete skill you will build, a value the company clearly demonstrates, or the quality of the team. Honest specificity, like "this is hands-on backend work at real scale, which is exactly where I want to deepen," beats manufactured passion every time, because interviewers can sense the difference.

### How long should my answer to this question be?

About thirty to sixty seconds. Long enough to include all three parts — a specific observation about them, a true detail about you, and the bridge — but short enough to stay tight and confident. Rambling dilutes the specificity that makes the answer work. Deliver the core answer, then stop and let the interviewer ask a follow-up rather than over-explaining.

### Should I prepare this answer for each company separately?

Yes. The structure stays the same, but the specifics must change per company, because the whole strength of the answer is that it could only be said about this one employer. Spend a few minutes of your company research pulling out one product detail, one recent fact, and one genuine personal connection, then assemble them into the structure and rehearse it out loud so it sounds natural rather than recited.

"Why do you want to work here?" rewards a specific answer delivered like you mean it. [Greenroom](https://usegreenroom.app/) runs spoken mock interviews that ask the real motivation questions, follow up on vague answers, and give feedback on every one. Free to start.