
Start from what they need
Take the top three requirements from the job post. Those are the three things the interviewer is trying to tick off. Your answer is the list of ticks, with proof.
Match each one with evidence
| They need | You say |
|---|---|
| Someone who can own a service | I have been on call for checkout for two years. |
| Someone who works well with product | I wrote the estimates and the trade-offs for our last three launches. |
| Someone who can mentor | Two engineers I mentored now run their own services. |
Adjectives do not count as evidence. Hard-working, passionate and a fast learner are claims. A thing you did is proof.
Add one thing they did not ask for
The requirements describe the average good candidate. One extra thing makes you a specific one: you have worked in support and know what customers ask, you have taught, you know the industry they sell to. Choose something true that this team could use.
An example
"You need someone who can own a payments service, work closely with product, and mentor. I have run on-call for checkout for two years. I write the estimates for our launches. Two engineers I mentored now run their own services. And before I was an engineer I spent a year in support, so I tend to notice the customer problem behind a ticket."
What to avoid
- Comparing yourself with the other candidates. You have not met them.
- Humility that turns into a list of what you lack.
- Repeating your whole CV.
- Going past a minute.
If you do not meet every requirement
Almost nobody does. Say what you have, say plainly what you have not done yet, and tell the story of the last time you had to learn something like it. A specific story about learning is worth more than saying that you learn fast.