How to answer why do you want to work here

Two things are being measured, and only one of them is enthusiasm. The first is whether you did research beyond the careers page. The second, quieter one, is retention risk: an interviewer who cannot tell why you picked this company assumes you applied everywhere and will leave for the next offer.

That is why the answer is scored on specificity rather than warmth. Saying you admire the culture is not wrong, it is simply unfalsifiable, and an unfalsifiable answer gives the interviewer nothing to write down. A detail that could only apply to this employer gives them a line for the debrief.

You already suspect the generic version is failing, and you are right. What follows is the three-part structure that replaces it. It moves from something true about them, to something true about you, to the overlap.

• The observation. One concrete thing: a product decision, a public engineering write-up, a market they entered, a constraint they work under. It must be something you could not say about a competitor.
• The connection. Why that observation matters given work you have already chosen to do. This is where your history does the persuading, not your adjectives.
• The forward half. What you want to work on there in the first year. Concrete beats ambitious.

Consider a data analyst interviewing at a logistics company. Instead of praising the culture, she noted that the company had moved its routing decisions from nightly batches to near real time, said that her last two roles were both about shortening the gap between a measurement and a decision, and named the reporting layer she would want to work on. Nothing there is flattery, and all of it is checkable.

The same three parts work for the sibling questions in this family, which are collected on the practice hub.

These four patterns are the ones interviewers report hearing most, and each has a repair.

• Reciting the mission statement. They wrote it, so quoting it back proves only that you opened the homepage. Repair: name a decision that shows the mission being applied, not the sentence itself.
• Praising size or prestige. Being a market leader is a fact about them, not a reason for you. Repair: say what the scale would let you personally work on.
• Talking only about what you get. Growth, mentorship and learning are legitimate motives that answer a different question. Repair: pair each one with what you bring in return.
• Praise that survives a find and replace. If swapping the company name leaves the answer intact, it is not an answer. Repair: add the one sentence that breaks when you swap the name.

A quick test before an interview: write your answer, replace the employer with their closest competitor, and read it again. If it still works, you have not answered yet.

Research first, phrasing second. Thirty minutes is usually enough if you look in the right places: recent product or pricing changes, the engineering or company blog, a founder or executive interview, the actual job posting, and reviews written by customers rather than employees. Note anything that surprised you, since surprise is what makes an observation sound like yours.

Then say it out loud, because this answer is short enough to over-rehearse into something stiff. Aim for 45 to 75 seconds. Practice it against a follow-up too, since strong answers invite what specifically would you want to work on? and that second question is often where the real scoring happens. Running that exchange a few times is what mock interviews are for.

One caveat for asynchronous rounds: if the question arrives in a recorded one-way interview, no follow-up is coming, so the specific observation has to appear in the first fifteen seconds rather than at the end.