What the interviewer is testing with a soft question
"Why do you want to work here?" sounds like small talk and gets graded like a filter. The interviewer is checking one thing: did you choose this company on purpose, or is this one of forty open tabs and they happened to reply first. An answer that could be pasted into a rival company's interview, unchanged, quietly answers "forty tabs," no matter how warmly you deliver it.
Short answer: Name two or three things that are specifically true of THIS company, and connect each to something specifically true of you. Pull those things from the job description, the engineering blog, the product itself, and recent public news, not from the mission statement on the "About" page. Leave out perks, salary, and the commute. If your answer would survive being read aloud in a competitor's office with no edits, it is too generic to earn a point.
That is the whole game, and most candidates lose it before they open their mouth by treating this as the throwaway question. Indeed's guidance is direct that one reason hiring managers ask it at all is to gauge how much you researched the company, so a vague answer reads as a research gap, not just a style choice (Indeed Career Guide). Harvard Business Review makes the same point from the candidate's side: people arrive rehearsed for their greatest weakness and a proud moment, then wing this one because it sounds easy, which is exactly why a prepared answer stands out (Harvard Business Review).
The three doors: company, role, and you
A strong answer walks through three doors in order, and skipping any one of them is what makes the reply feel lopsided. MIT's careers office frames it as three linked questions: why this company, why this position, and why you will do well in it, combined into one short response rather than answered as separate speeches (MIT Career Advising and Professional Development).
| Door | The question behind it | What a strong answer names |
|---|---|---|
| Why this company | Do you actually know who we are? | A product decision, an engineering value, or a public post that only this company owns |
| Why this position | Does this job fit where you are heading? | The specific work in the posting that matches your trajectory |
| Why you | Will you do well here, not just want to be here? | One relevant result of yours that maps to a problem they have now |
Most candidates over-invest in the first door and forget the third. They describe the company back to itself in glowing terms and never say why they, specifically, will be good at the job. The third door is where enthusiasm turns into evidence. It is also the part an interviewer cannot get from your resume, so it is worth the most.
Where a specific answer actually comes from
The reason generic answers are so common is that people research the wrong surface. The "About" page is written to sound noble and applies to almost any company in the sector, so mirroring it back produces the exact sameness you are trying to avoid. The material that makes an answer land lives elsewhere.
| Source | What to mine | What you turn it into |
|---|---|---|
| The job description | The problems listed first, the stack, the team's stated goals | "Your posting leads with reliability, and that is the work I want more of" |
| The engineering blog or changelog | A real technical decision, migration, or postmortem they published | "Your write-up on splitting the monolith is the kind of problem I have been chasing" |
| The product itself | Sign up, use it, note one thing you liked or would sharpen | "I have used it for a week, and the way you handle onboarding stood out" |
| Recent news or releases | A launch, a funding round, an expansion, a public direction | "The recent move into data residency is exactly where I want to be building" |
| Glassdoor, Reddit, LinkedIn | Culture and tempo signals, read with skepticism | Tone and values you echo, never numbers you quote as fact |
The engineering blog is the most underused of these. A company that writes up its own postmortems is telling you what it cares about, in its own words, and referencing one shows you did more than skim a careers page. Start your research on the company site, as Indeed suggests, but do not stop there, because the "About Us" and "Careers" pages are exactly the surfaces every other candidate also read (Indeed Career Guide). The parts that are harder to find are the parts that make your answer sound built for this room.
The test of a good answer is not whether it sounds enthusiastic. It is whether it could only have been written about this one company.
Before and after: rebuilding a generic answer
Work through a real-shaped example. Consider a backend engineer we will call Maya, interviewing at an observability company whose product helps teams find the cause of production incidents. Here is her first draft, the one almost everyone gives:
"I want to work here because you have a great culture, a strong reputation in the industry, and it is an exciting opportunity with a lot of room to grow. I have heard great things, and I think it would be a great place to build my career."
Nothing in that is wrong. Nothing in it is about this company either. Every clause would fit a bank, a games studio, or a grocery chain. Before you commit an answer to memory, it is worth running a blunt check on the draft to see how much of it is filler that fits any employer:
// A quick gut-check you can run on a draft answer before the interview.
// It flags empty phrases that fit any employer, so you can replace each
// one with something only THIS company would recognise.
function fillerFlags(answer) {
const empty = [
"great culture",
"good reputation",
"room to grow",
"market leader",
"exciting opportunity",
"passionate about",
];
const text = answer.toLowerCase();
return empty.filter((phrase) => text.includes(phrase));
}
const draft =
"I want to work here because you have a great culture, a good reputation, " +
"and it is an exciting opportunity with room to grow.";
fillerFlags(draft);
// [ 'great culture', 'good reputation', 'room to grow', 'exciting opportunity' ]Four flags in one sentence is the whole problem in miniature. Now Maya does thirty minutes of real research. She reads the company's public incident-review blog, notices they wrote about moving from a single service to event-driven pipelines to cut alert noise, and reflects on her own last year spent owning on-call for a payments service where false alerts were burning out the team. The rewrite writes itself:
"Two things pulled me toward this role. First, the work: your posting leads with reducing alert fatigue, and your blog on moving to event-driven pipelines to cut noisy alerts is a problem I lived last year owning on-call for our payments service, where false pages were the top complaint in every retro. Second, the fit: I want to spend the next few years going deeper on reliability tooling specifically, and you build the thing I kept wishing we had. That combination is rare, which is why this is not a role I applied to casually."
Same person, same enthusiasm, completely different signal. It names their posting, their blog, and her own matching result, then closes on why she chose them. If the interviewer only has fifteen seconds of attention left, Maya can compress it without losing the specifics:
"Your posting leads with alert fatigue, which is the exact problem I owned on-call for last year, and your event-driven write-up is where I want to go deeper. This is the reliability work I have been trying to get more of."
The long version proves she did the reading. The short version survives a rushed panel. Prepare both, because you rarely control how much room the question gets.
The traps that sink an otherwise good answer
Even candidates who research well fall into a handful of predictable holes. Name them so you can hear yourself sliding.
- Flattery with no substance. "You are the best in the space" is praise, not a reason. Praise makes the interviewer wait for the part where you say something only an insider would know. If it never comes, the compliment reads as padding.
- Leading with what you get. Salary, benefits, the office, remote flexibility, the commute. Robert Half is blunt that companies do not want to hire people whose main motivation is money, and treats leading with compensation as a clear example of how not to answer (Robert Half). These may be real reasons you applied. They are not the reasons you say out loud first.
- Reciting the About page. Quoting the mission statement back proves you can read a homepage. It is the single most common tell of shallow research, because that page is written to be quotable by anyone.
- The overrun. This is not the question that wants a three-minute answer. Thirty to sixty seconds, two or three specifics, done. Past that, you are narrating, and the interviewer has moved on to their next question.
- Manufactured passion. Forcing wide-eyed excitement you do not feel is easy to spot and hard to sustain under follow-up questions. A calm, specific reason beats a loud, generic one every time.
The common root of all five is talking about the company in the abstract instead of about the specific overlap between them and you. Fix the overlap and the traps close on their own.
When you are not sure you even want the job
Here is the honest case the polished guides skip. Sometimes you are interviewing to learn, to test your market value, or because a recruiter reached out and you were curious, and you do not yet know if you want this particular job. Faking certainty in that situation backfires, because forced enthusiasm is exactly what interviewers are trained to discount.
The move is not to lie and not to confess. Anchor on the parts you genuinely find interesting, and stay neutral on the rest. You do not have to claim this is your dream company. You have to name one real thing about the work that pulls you in and be specific about it. "I am early in looking, and what made me take this call specifically was your reliability tooling, because that is the direction I want to move" is honest, and it still answers the question. What you never say out loud is "I am keeping my options open" or "I am just seeing what is out there," even when it is true, because it hands the interviewer a reason to invest their attention elsewhere.
This is also where researching the company protects you. If thirty minutes of reading turns up nothing you actually care about, that is real signal about the fit, and it is better to learn it before you accept than after you start. A specific answer and a good decision come from the same homework, which is why the research is worth doing even when you are undecided. It is the same reading you would do to research a company before an interview for any reason.
Frequently asked questions
How long should this answer be? Thirty to sixty seconds. Two or three specifics tied to the company, one reason they fit you, then stop. This is a short-answer question, and going long dilutes the specifics that were doing the work.
What if I genuinely applied mostly for the salary or the remote setup? Keep those as private tie-breakers, not your headline. Find one real thing about the work or the product you can speak to honestly, lead with that, and let the practical reasons stay unspoken. Leading with compensation reliably reads as a reason not to hire you.
I could not find an engineering blog or any recent news. Now what? Fall back to the product and the job description, which every company has. Use the product for a week, form one specific opinion, and mine the posting for the problem it leads with. A thin public footprint is common at smaller companies and is not an excuse for a generic answer.
Is it fine to say I want to work with a specific team or person? Yes, if it is true and you can say why. "I want to work on the platform team because I read your talk on your deploy pipeline" is specific and flattering in a way that lands. Name-dropping someone you have not actually engaged with is riskier and can sound hollow under a follow-up.
How is this different from "tell me about yourself"? "Tell me about yourself" is about you and your trajectory. "Why do you want to work here" is about the overlap between you and this specific company. You can prepare them together, since both draw on the same research, but keep the company question pointed outward at them, not inward at your history. See answering "tell me about yourself" for the companion opener.
Should I memorise it word for word? Memorise the two or three specifics and the one line of fit, then let the phrasing vary. A word-perfect recital sounds recited, which undercuts the sincerity the question is testing for. Rehearse the structure, not the script.
What if the interviewer is a recruiter, not the hiring manager? Keep it slightly higher level and lean on the product and the company direction rather than deep technical detail, since a recruiter is screening for genuine interest and basic fit. Save the engineering-blog specifics for the technical rounds, where they carry the most weight.
Where to take this next
- Do the reading that feeds a specific answer by learning to research a company before an interview beyond the About page.
- Mine the posting itself for the problems worth naming by reading a job description for its hidden signals.
- Prepare the companion opener with answering "tell me about yourself" so both draw on the same research.
- Turn your own curiosity into leverage at the end of the loop with smart questions to ask your interviewer.
Sources
- Indeed Career Guide, "How Best To Answer: Why Do You Want To Work Here?": https://www.indeed.com/career-advice/interviewing/interview-question-why-do-you-want-to-work-here
- Harvard Business Review, "How to Answer 'Why Do You Want to Work Here?'": https://hbr.org/2022/08/how-to-answer-why-do-you-want-to-work-here
- MIT Career Advising and Professional Development, "3 Tips for Answering 'Why Do You Want to Work Here?'": https://cdo.mit.edu/blog/2023/04/05/3-tips-for-answering-why-do-you-want-to-work-here-examples/
- Robert Half, "How to Answer 'Why Do You Want to Work Here?'": https://www.roberthalf.com/us/en/insights/landing-job/how-to-answer-why-do-you-want-to-work-here