The three-part answer
- Why this kind of work: what part of the job you are actually drawn to, tied to something you have done before.
- Why this company: something specific and verifiable — their product, market position, engineering approach, or a decision they made.
- Why now: what makes this the sensible next step from where you are.
Ninety seconds is plenty for all three. Most candidates cover only the second, and do it with generic praise.
A worked example
"I have spent three years on internal tools, and the part I have enjoyed most is working directly with the people using them — I can ship something on Tuesday and watch it change someone's Wednesday. This role is the same loop but with external customers and a lot more scale.
On the company specifically: I have followed how you handled the pricing migration last year, and publishing the postmortem when it went badly is not a common instinct. That is the kind of engineering culture I want to work in.
And now, because I have taken internal tools about as far as I can at my current size — I want a bigger surface area and more senior people to learn from."
What sinks the answer
- Praise that could apply to any well-known company: "You are a leader in the space and I admire your innovation."
- Making it entirely about what you get — salary, title, remote work — with nothing about the work itself.
- Reciting the About page back to the person who works there.
- Being honest to the point of self-harm: "I need a job and you are hiring."
- Talking mostly about your current employer's problems.
Doing the twenty minutes of homework
You need one genuinely specific fact. Twenty minutes gets you there:
- Read the last three posts on their engineering or company blog.
- Use the product if you can, even the free tier, and form one opinion about it.
- Check recent news — funding, launches, leadership changes, layoffs.
- Read the job posting a third time and note which responsibility is listed first. That is usually the real job.