Why do you want to work here?
Take a moment.
Say your answer out loud or write it down first — retrieval is what makes it stick. Reveal when you're ready.
Short answer
Connect three researched threads: what the company does that genuinely interests you (product/mission), what the role offers matching your trajectory, and what you bring that maps to their current needs. Specifics prove research; generic praise kills credibility.
Detailed explanation
This filters mass-applicants from interested ones. Research layer: recent launches, engineering blog posts, tech-stack mentions in job posts, funding/product news, Glassdoor themes. Build the bridge both directions — 'their problem' meets 'my strength': 'You're rebuilding for scale after that outage postmortem; I've led similar migrations' outperforms 'you're an industry leader' every time. Genuine angle required: find the part you'd actually care about — if mission feels distant, connect through craft ('complex domain problems'), growth ('you're doubling the platform team'), or product love ('I use it daily'). Structure: hook with a specific observation → tie to your experience → forward-looking contribution. Avoid: compensation-first framing, vague culture compliments, reading their About page aloud, comparing against competitors negatively. Interviewers want evidence you'll stay engaged through hard sprints.
Example
"Your engineering blog post on cutting p95 latency by rewriting the ingestion pipeline caught my attention — I spent last year doing exactly that for our analytics service. This role owns that pipeline's next phase, and my experience with Kafka partitioning strategies maps directly onto your scaling roadmap. Honestly, rare to see a role match a specialty this closely."Interview tip
Cite one artifact you actually consumed (blog post, changelog, talk). Then make the skills-match explicit. One specific detail outweighs ten compliments.
Common mistakes
- Answering generically enough to fit any company.
- Leading with perks or salary rationale.