Why This Company

It appears in the recruiter screen, the hiring-manager round, and the founder round, and most candidates answer it with a paraphrase of the company's own marketing. "I'm excited about what you're building in AI" is heard as "I applied to forty places."

A good answer has three parts. Something specific about them — the product decision you noticed, the engineering blog post you read, the thing their API does that others don't. Something specific about you — why this problem connects to what you've built or want to build next. And something about fit at this stage — why a 25-person company rather than a 2,000-person one, said in terms of how you want to work.

Worked example: "I've built two features on top of model APIs and the part I found hardest was knowing whether a change actually improved anything. Your eval tooling is the first product I've seen that treats that as the main problem rather than a dashboard bolted on afterwards. And at your stage I'd get to own a surface end to end, which is the part of the last job I liked most."

Do the twenty minutes. Their docs, their changelog, their engineering blog, the founders' recent posts, and — if it's usable — the product itself. Using the product and saying something concrete about it puts you ahead of nearly everyone.

It's fine to include practical reasons — remote, comp, timing — but not as the lead. Honest and unglamorous beats invented passion, which everyone can detect.

The same content drives cold outreach. A short message with one specific observation about their product and one line on what you'd bring gets replies; a generic "I'd love to explore opportunities" doesn't. Outreach to an engineer or founder outperforms an application form at companies this size.

Prepare the inverse too: "why are you leaving?" Answer it forward-looking and without bitterness about your current employer. Criticising a previous team is remembered far longer than the reason.

At a small company the founders are choosing people who care about this specific problem, because that's what carries a team through a hard quarter. It's also a cheap proxy for diligence: a candidate who spent twenty minutes on the product before the call will probably do the same for a customer.

• If the answer fits their competitor unchanged, rewrite it.
• Three parts: something specific about them, something specific about you, and why this stage.
• Read the docs, changelog, and engineering blog; use the product if you can.
• One concrete observation about the product outperforms any amount of enthusiasm.
• Practical reasons are fine and credible, just not as the headline.
• Manufactured passion is detectable and costs more than a plain honest answer.
• Reuse the same material for cold outreach — specific beats polished, and beats an application form.
• Prepare "why are you leaving?" as a forward-looking answer with no criticism of your current team.