“Why do you want to work here?” is one of the most failed questions in modern interviews, and almost nobody fails it because their motivation is bad. They fail it because their answer could be pasted, word-for-word, into any other interview at any other company. According to a frequently cited industry stat, roughly 47% of candidates lose interviews due to insufficient knowledge of the company. This question is where that gap shows. Below is a three-part framework, fifteen sample answers across very different employer types, and a list of phrases that flag you as unprepared.

Why interviewers ask this

Interviewers are not testing whether you like the salary, the benefits, or the office snacks. They already assume you want those. What they are actually probing is two things at once: research depth and cultural alignment. Research depth is the easy half — did you read past the homepage? Did you look at recent product launches, the engineering blog, the CEO’s posts, or how they talk about customers? Cultural alignment is the harder half — does your version of “good work” overlap with theirs?

Harvard Business Review’s Joel Schwartzberg makes a sharp point: interviewers ask this because you cannot articulate compelling reasons for wanting to join a company you do not understand. The Muse adds that a generic answer — one you could reuse at three competitors — is read as “this person is interviewing everywhere and we are nothing special.” That signal alone is often enough to push a candidate from “yes” to “maybe,” and “maybe” rarely becomes an offer. The job here is to make the answer impossible to recycle.

The three-part framework

Use three beats. In order. Each beat is one or two sentences. Total airtime: 60 to 90 seconds.

1. Specific company signal. Name one concrete thing about the company that you could not have known without doing real research. Not the About page mission statement. Something like a recent product decision, a podcast the founder did, a Series B announcement, a public engineering write-up, a shift in pricing model, a customer story they shipped last month. This is the proof-of-research beat.

2. Personal connection. Tie that signal to something genuine about your background or values. Not “I share your passion for excellence.” Something like: “I spent two years building the exact thing you just open-sourced,” or “I left my last role because we treated reliability the opposite way.” The personal connection should make the first beat feel earned, not researched-the-night-before.

3. Forward action. End with what you would do here, specifically. Not “I want to grow with the team.” Something like: “I want to spend the next two years on the kind of inference cost problems your December launch implies you’re hitting.” This is the beat where you stop being a candidate and start being a future coworker.

15 sample answers

1. Early-stage startup, engineer. “Your blog post about ripping out the monolith last quarter is what convinced me to apply. I just did the same migration at my current company and it broke me in interesting ways. I want to land somewhere small enough that the rewrite is still hot, and your team is at exactly that stage.”

2. Big-tech, product manager. “Two things. One, your roadmap doc that got shared on Lenny’s Newsletter was the clearest articulation of marketplace prioritization I’ve read. Two, I’ve spent four years on two-sided marketplaces and kept hitting the same trust-and-safety wall you wrote about. I want to work on that wall.”

3. Non-profit, program lead. “I tracked your literacy program in three states last year because my mom ran a similar one in Ohio. Your evaluation methodology — actually publishing the negative results — is rare. I want to bring the operations rigor I learned in private sector to a program that’s honest about what works.”

4. Agency, senior designer. “Your case study for the Patagonia rebrand is the reason. Most agencies show the final art; you walked through the three directions you killed and why. That’s how I think about design reviews, and I have never worked somewhere that documented it the same way.”

5. Fully remote SaaS, customer success. “Your handbook is public, and I read the section on async escalation paths twice. I’ve been a remote CSM for three years and the thing that breaks is exactly what you’ve built guardrails around. I want to do the work, not relitigate the rituals.”

6. Fintech scale-up, data scientist. “Your fraud team published a paper on graph embeddings for ring detection last September. I have been working the same problem at a smaller scale, and I want to ship it against your data volume.”

7. AI infrastructure startup, ML engineer. “Your December launch implied you’re hitting serious inference cost issues — the latency numbers in the changelog told on you a little. That is the problem I want to spend the next two years on, and your team is small enough that I would actually touch it.”

8. Consulting firm, analyst. “I read the partner’s piece on energy-transition portfolios and it changed how I framed my undergrad thesis. I want to work somewhere the senior people still write, and where the writing is held to that standard.”

9. Healthcare startup, ops manager. “Your founder did a podcast about why you walked away from a CVS partnership. That trade-off — short-term revenue versus the clinical model — is exactly the kind of decision I want to be near. My last company made the opposite call and I watched the product erode.”

10. Hardware company, mechanical engineer. “The teardown YouTube did of your last product was brutal and your engineering lead responded with a public post agreeing with half of it. That kind of public iteration is rare in hardware. I want to design where iteration is allowed to be visible.”

11. Media company, senior editor. “Your beat on housing policy is the only one I read end-to-end every week. I came up in regional news where every story had to justify itself in 600 words, and I want to bring that economy to a national outlet that still cares about reporting depth.”

12. Climate non-profit, policy researcher. “Your team’s filing on the EPA methane rule was cited in two of the briefs I wrote last year. I want to be on the side that writes the source documents, not the side that quotes them.”

13. Cybersecurity firm, threat researcher. “Your write-up on the supply-chain compromise in January was the technical reference I sent to my whole team. The fact that you publish detection logic rather than gating it is why I’m here, not at your competitor down the road.”

14. EdTech, curriculum lead. “I taught your beta product to a class of 9th graders last spring as part of a district pilot. The kids actually used the feedback loops. I want to work on what made that happen, not on whatever the next venture-funded competitor pitches.”

15. B2B SaaS, sales engineer. “Your CRO went on a webinar and said something I have been waiting to hear from a vendor for years — that the SE should own the technical narrative through close, not hand off at the demo. That maps to how I already work, and most teams pretend otherwise.”

What NOT to say

Closing move and practice routine

The closing move on this question is to make the interviewer believe you would not give the same answer to their three closest competitors. The cleanest way to prove that is to anchor the answer in something the company published, said, or shipped in the last ninety days. Anything older feels like Wikipedia.

A workable research routine, in under an hour: read the last six posts on the company’s engineering or product blog, skim the founder’s last ten LinkedIn or X posts, watch one recent podcast appearance from a leader (Lenny Rachitsky’s podcast, First Round Review, or whatever is industry-relevant), check the changelog or release notes, and read one customer story. Then write the three-beat answer out longhand. Read it back. If you could send the same paragraph to any of their competitors and have it still make sense, it is not specific enough — go back to the company signal beat and replace the abstract noun with a proper noun.

Practice it twice out loud, not five times. Five times makes you sound rehearsed; two times makes you sound prepared. And once you have the answer working, do not memorize it word-for-word — memorize the three beats. The exact phrasing should feel slightly different every time you deliver it. That is what genuine sounds like in an interview room.