There's a specific way this question gets answered badly, and it's not laziness. It's that candidates answer the half they prepared.
They researched the company, so they talk about the company: the mission, the growth, the product they admire. All true, all researched, and it answers a question nobody asked — why is this company good? The interviewer knows. They work there.
The question is why you and this company and this role, together. Three things, and the answer has to join them.
The three parts
| Part | The claim | What it sounds like when it's missing |
|---|---|---|
| Them | Something specific and true about this company | Generic praise that fits any competitor |
| The role | Why this job rather than a similar one elsewhere | Enthusiasm for the company with no interest in the work |
| You | What in your history makes this the sensible next step | A flattering answer that could be anyone's |
Most answers have one part. Good answers have all three in about four sentences. The joining is the whole exercise — each part should make the next one inevitable.
The substitution test
Take your answer and swap in a direct competitor's name. If it still works, you haven't answered the question.
Then a harder version: swap in a different role at the same company. A lot of answers survive the first test and fail the second, which is how you end up sounding enthusiastic about the employer and indifferent to the job — a combination that reads as someone who applied to twelve openings there.
The most useful research isn't about the company, it's about the role's shape. "You're a Series B company growing fast in a big market" is true of hundreds of employers and tells the interviewer nothing about why you're sitting there. "This role owns both the API and the client that consumes it, which is unusual — most places split those" is a sentence only someone who read the job description carefully could produce, and it implies you know what you're signing up for. Specific beats impressive.
A worked answer
"Two things. The first is narrow: this role owns the migration, not just the new system. I've done that twice and it's the part I'm actually good at — building the replacement is the easy half, moving people onto it without breaking anything is where the work is, and most job descriptions quietly leave it out.
The second is that you've got a product with real usage and a codebase that's about six years old. That combination is specific — plenty of interesting problems and no option to rewrite from scratch, which is the constraint I like working under.
Honestly, the thing that made me apply rather than bookmark it was the line about the platform team being new. Joining something at the point where the shape isn't decided yet is worth more to me than seniority."
Thirty-five seconds. Nothing in it is praise. Every sentence is a claim about fit that the interviewer could disagree with — which is what makes it credible.
Three situations that are harder
You need a job and that's mostly it
Common, and the honest version is usable if you do one thing: find the part of the role you'd genuinely choose, and lead with that. Not the whole truth, but not a lie either.
"I'll be straightforward — I'm looking actively, my last role ended in a restructure. What made me apply to this one specifically is that it's the first support-engineering role I've seen that sits inside the product team rather than next to it. I've worked in both setups and the second one is why I left a job once."
Interviewers respect this far more than a performance. What they're screening for isn't devotion; it's whether you'll still be interested in eight months.
It's a big, famous company
The trap is that everyone says the same three things about them, and the interviewer hears all of it every day. Go one level down: a specific team, a specific product surface, a specific engineering or design decision they made publicly.
"The honest answer isn't the brand — it's that you shipped the offline mode last year, and I spent a month failing to build something similar at a much smaller scale. I'd like to work somewhere that got it right."
You don't know much about them yet
It happens — a recruiter reached out, the process moved fast. Say so, and convert it into a question. That's not a weak answer; it's the beginning of a conversation, and it's much better than inventing enthusiasm.
"Less than I'd like, honestly — your recruiter reached out three days ago. What I've got so far is the shape of the role, and the part that got my attention is X. What I can't tell from the outside is Y, and it's the thing that would decide it for me."
The company appreciation
“I've been really impressed by your growth, the mission resonates with me, and everyone I've spoken to seems genuinely passionate about the product.”
Warm, generic, and interchangeable between you and the four other people interviewing this week. It also puts the interviewer in the awkward position of accepting a compliment instead of learning something.
The specific fit
“This role owns the migration, not just the new system — and that's the half I'm good at and the half most descriptions leave out.”
A claim about the work, tied to something in your history, that only applies to this posting. It also tells them what you'd want to talk about next, which is a gift to an interviewer with ten minutes left.
Where the material comes from
You need roughly twenty minutes, not two hours, and the sources that produce usable sentences are narrower than people expect:
- The job description, read closely. Especially what it doesn't say, and anything unusual about the scope. This is where most of the best answers come from and it's free.
- The changelog, release notes or engineering blog. Concrete things they built recently.
- One person's public writing — the hiring manager, a team lead. Not to flatter them; to know what they care about.
- The thing you couldn't find out. A genuine gap is material: it becomes a question, and a question is stronger than a fact.
What produces nothing usable: the About page, funding announcements, and the values page. Those generate exactly the generic answer this article is about.
The efficient version of this research, including what to skip, is here: how to research a company before an interview. And the gap you found is usually the best thing to raise at the end: questions to ask the interviewer.
Saying it out loud
Keep it short. This question invites over-talking because the material feels flattering and safe, and a ninety-second answer about why you admire the company reads as filling time.
Say your three parts, then stop, and let them ask. The follow-up is usually the interesting conversation — and it's much better to be asked "what do you mean the migration is the hard half?" than to have pre-empted it in a monologue.
Practical target: write your answer, then run the substitution test out loud — say it once with a competitor's name and once about a different role at the same company. If both versions still sound fine, you've written a compliment rather than an answer, and the fix is almost always to go back to the job description rather than to the company website.
