How to Answer 'Why Do You Want to Work Here?' (2026)

Almost everybody answers this question badly and almost nobody notices, because the bad answer sounds perfectly pleasant. "I have heard great things about the culture, you are doing exciting work in a fast-growing space, and I think I would learn a lot here." Nothing in that sentence is wrong. Nothing in it is about this company either. Swap the logo and it still works, which is precisely the problem.

The question is short and feels like a formality, so candidates treat it as one and produce warm noise. Meanwhile the interviewer is making a cold assessment: do you know what we do, have you thought about why this job in particular, and will you still be here in eighteen months. A generic answer says you are applying widely. A specific one says you chose.

This guide covers what they are really asking, a three-part structure, three full sample answers for the situations where it gets awkward, and what quietly kills an otherwise decent answer. To see whether this question is even likely to come up, and what else will, paste the job posting into the free Question Predictor and you will get the twenty most likely questions for that specific role.

Why do interviewers ask "why do you want to work here?"

They are testing three things at once: whether you have done real research, whether your reasons are specific enough to be durable, and whether you are likely to accept and stay. It is a retention question dressed as a compliment. Someone who cannot say why this company over any other is someone who will leave for the next offer, and hiring is expensive.

The research element is the easiest to read and the one most candidates fail. An interviewer has heard their own homepage read back to them hundreds of times, so anything you could have learned in ninety seconds registers as no preparation at all. What lands is evidence you engaged past the marketing: a product decision, a recent change of direction, a specific problem the role exists to solve.

The durability element is subtler. Salary, location and "I need a job" are true of most candidates and predict nothing about how long you stay. Reasons tied to the actual work survive contact with a hard week in month four. There is also a quiet self-interest angle: interviewers chose to work there too, and hearing an outsider say something true and flattering about the place is persuasive in a way that generic praise never is, because generic praise is not about them.

What is the best structure for answering it?

Three parts, in this order: something specific about the company, something specific about the role, then the connection to where you are heading. Company, role, you. It runs sixty to ninety seconds spoken, it keeps you off vague culture talk, and it ends on the thing the interviewer most wants to hear, which is that this job is a deliberate step rather than an available one.

Part one: the company, specifically. Name one thing you can only say about them: a product decision you have opinions on, a market position, a recent shift. The test is whether the sentence would survive being said to a rival; if it would, it is not specific enough. "You are one of the few companies here building the infrastructure rather than reselling someone else's" passes. "You are an innovative leader in your field" does not.

Part two: the role, specifically. Plenty of people want to work somewhere and would be miserable in the actual position. Point at something concrete in the job description and say why it appeals: the scope, the ownership, the particular problem, the stage. This also demonstrates that you read the posting properly, which is a lower bar than it should be and still routinely missed.

Part three: you, forward. Join it to your own trajectory: what you want to be doing more of, why now is the right point for this move. This is the beat that turns flattery into a reason, and it answers the unspoken version of the question ("why would you leave a perfectly good job for this one") without you having to be asked.

How much company research is actually enough?

Enough to say one thing they would not expect a stranger to know, and to have a view about it. That is a much lower bar than reading everything and a much higher one than skimming the About page. Thirty focused minutes usually gets you there: the product itself, one recent piece of news, and one thing about how they work.

Use the product if you possibly can. Sign up, install it, click around, form an opinion. "I made an account last week and the onboarding does X, which is a deliberate choice given Y" is worth more than any amount of reading, because almost nobody does it and it is instantly verifiable as real. If the product is not accessible, the next best things are their engineering blog, a recent talk, or their public documentation.

Then find one recent change: funding, a launch, a market they entered, a pivot, a new leader in your area. Recency signals that your interest is current rather than assembled from whatever the company looked like three years ago, and it gives you something to be curious about, which is more attractive than something to praise.

Look too at how they operate, because that is your day-to-day: remote or office, how they ship, how much autonomy one person gets. Employee reviews and the careers page lie in opposite directions, so triangulate. For a named company, our company interview questions pages set out the rounds and what candidates report being asked.

What does a strong answer actually sound like?

Three full answers below, each following company, role, you. They cover the situations where this question gets awkward: changing careers, having been made redundant, and moving to a direct rival. Notice that each one says something specific about the company before it says anything about the candidate. The bracketed parts are where your own specifics go.

(a) Career changer

The reason I went after this one specifically is that you build for operations teams rather than for engineers, and having spent four years on the receiving end of tools like this, I have strong opinions about what most of them get wrong. I installed [product] a couple of weeks ago and the [bulk editing flow] is the first one I have used that assumes the user is doing this fifty times a day. As for the role, what appeals is that it sits close to the customer rather than three layers back; the description talks about [running discovery sessions directly], and that is the part of the work I have been doing informally for years without the title. I want to build the thing rather than file tickets about it, and this is a role where my operational background is an asset instead of a detour.

The career changer's task is to make the old career the reason rather than the obstacle. This one turns four years on the customer side into domain expertise and closes on intent rather than escape.

(b) Made redundant

I will be straightforward about the timing: my role went in [the restructure in March], so I am looking now rather than in a year. That has made me more selective rather than less, because I have had time to look properly at where I want to go next, and this is the role I have been most deliberate about. You are at the point where [the platform is being rebuilt for scale rather than for the first version], and that specific stage, taking something that works and making it hold at ten times the volume, is where I have done my best work. The role fits that; it is broad enough that I would own [the data pipeline end to end], which is what I want after three years of owning one slice. So the honest version is that the timing was not my choice, but the target absolutely is.

Redundancy is not a weakness and the worst thing you can do is behave as though it is. This names it in one plain sentence, refuses to apologise, then spends the rest on genuine specifics. The line about being more selective, not less, does real work.

(c) Moving to a direct rival

I know the space well, having spent [three years] on the other side of it, and the reason I approached you rather than the reverse is that your bet on [self-serve rather than enterprise sales] is the one I think is right. I have watched that decision play out from a competitor's seat and it is genuinely harder to execute than the alternative, which is part of why it interests me. On the role, what I want next is [owning retention rather than acquisition], and this position is scoped around exactly that. To be clear about the obvious question: I am not bringing anything confidential with me, and I would not want a hire who would. What I am bringing is four years of understanding what this market wants.

The rival move has one landmine and this defuses it before anyone raises it. Addressing confidentiality unprompted reads as integrity rather than defensiveness, and converts the elephant in the room into a point in your favour.

What kills this answer?

Most failures are not dramatic, just forgettable, which for a question designed to differentiate you amounts to the same thing. The pattern is nearly always identical: the answer is true, pleasant, and equally applicable to fifty other employers. These are the recurring ones, roughly in the order interviewers hear them.

• Praise that fits any company. "Great culture", "exciting growth", "innovative products", "market leader". Unfalsifiable and interchangeable. If the sentence works with a different company name in it, cut it.
• Making it entirely about you. "This role would help me develop my skills." True, and irrelevant to them. Your benefit belongs in part three, after a reason that is about the work.
• Salary, location or commute as the headline. Legitimate reasons to want a job, terrible reasons to lead with, because they say nothing about whether you will do it well or stay in it.
• Trashing your current employer. "I want out of a toxic environment" answers a different question and plants a doubt about how you will talk about this company later. Frame everything as moving toward something.
• Reciting the homepage. Reading their marketing copy back to them proves you can read, and creates an awkward moment for the interviewer who either wrote or resents that copy.
• Obvious flattery. Laid on thick it reads as insincere or desperate, and experienced interviewers discount it entirely. One accurate observation lands harder than a paragraph of admiration.
• Getting a fact wrong. Naming a product they discontinued is worse than saying nothing, because it proves the research was shallow rather than absent. Check anything you plan to mention.

How do you answer if you do not have a burning reason?

Be honestly specific rather than dishonestly passionate. You do not need to have dreamed of working there; you need one true reason that is about the work rather than the paycheque. "This is the problem I find interesting and you are one of a handful of companies working on it seriously" is a sufficient answer, with the advantage of being true.

Most jobs are nobody's calling and interviewers know it. What they screen out is indifference, not the absence of destiny. So find the truest specific thing available: the technical problem, the stage of company, the scope of the role. Stated plainly, that beats manufactured enthusiasm, which experienced interviewers detect immediately and mark down.

The one thing not to do is fake it hard. Overclaimed passion invites a follow-up ("what specifically about our approach?") that you cannot answer, and that collapse is worse than the modest version would have been. Before the interview, paste the job posting into the Question Predictor to see which questions the role is likely to open with, because this one often arrives second and there is no recovering from fumbling it cold.

For the moment a question lands sideways, GhostPilot is a real-time interview copilot: a Chrome extension side panel or a Windows desktop app that follows the conversation and has a structured answer ready roughly two seconds after the question is asked, so you have a shape to work from rather than a blank. The free tier is ten minutes of live session a week with no card, which is enough to rehearse this answer properly.

Frequently Asked Questions

How long should the answer be? Sixty to ninety seconds. That covers one specific thing about the company, one about the role and a forward-looking close, with a sentence of substance behind each. Past two minutes you have started answering "walk me through your career" instead, and the specificity gets diluted by volume.

Is it different from "why do you want this job?" Slightly, and it is worth noticing which you were asked. "Why this company" wants the organisation-level reason; "why this job" wants the role-level one. The three-part structure covers both, so just change the weighting.

Should I mention salary or benefits? Not in this answer. They are legitimate factors with a proper place, which is the compensation conversation. Naming them here suggests the work itself is not the draw, which is exactly the doubt this question exists to test for.

What if I am applying to a lot of companies? Everybody is, and interviewers assume it. They are checking whether you thought about this one specifically, not whether it is your only application. Thirty minutes of real research per company you actually care about is enough.

What if I have not used their product? Say what you engaged with instead: documentation, an engineering blog post, a talk, a public case study, or a conversation with someone who works there. If the product is accessible at all, though, use it. Thirty minutes puts you in a very small minority of candidates.

Closing

"Why do you want to work here" is a specificity test, graded almost entirely on whether your answer could have been given to somebody else. Do thirty minutes of real research, find one thing you can only say about them, connect it to something concrete in the role, and close on where you are heading. Ninety seconds, no salary, no commute, honestly specific rather than dishonestly passionate.

Get GhostPilot on the Chrome Web Store