Requirements are a question list
“Experience managing a regional P&L” is “tell me about the largest budget you have owned, and the month it went wrong.” Treat each line that way and most of the interview is on the page in front of you.
Interview preparation
Preparation that is about this job, not about interviews in general.
Most interview preparation is reading. Reading is the least useful thing you can do with the three evenings you have. Here is the routine that is worth the time, and the part of it a tool can carry for you.
The routine
Seven stages, in this order
The order matters: every stage after the first is better for having done the one before it.
- Understand the job
- Line up your CV
- Add your material
- Configure
- Practise
- Review the questions
- Improve
Understand the job
Paste the description in and have it broken down: required skills by category, nice-to-haves, and what the team is plainly struggling with.
Line up your CV
Against that breakdown, where you are strong and where you are thin — before an interviewer finds the thin part for you.
Add your material
Project write-ups, architecture notes, the design doc you are proud of. The specifics live in these, not in your CV.
Configure
How long your answers should run, how formal, STAR or free-form, which language. Set once, used by every session.
Practise out loud
A mock interview from that job description: it asks, you answer, it scores and says what was missing.
Review the questions
Every question you have been asked, in practice and for real, collected in one place.
Improve
Fix the two weakest answers rather than re-reading the six strong ones. Then do it again.
Stage one
Read the job description like an interviewer wrote it
Because one did. Every requirement in it is a question somebody has been told to ask.
The order is a priority list
What is in the first three bullets is what the team is short of. That is where the hard questions and the follow-ups will be, and where a thin answer costs the most.
The gaps are the preparation
Where your CV does not meet the description, you need an honest answer ready — the nearest thing you have done, and what you would do to close the rest. Not a bluff.
Stage two
Four stories carry most of an interview
Pick them from your own CV, write the numbers down, and practise them until the shape is automatic. Then almost any behavioural question is one of these four, redirected.
Something you shipped
What it was, who it was for, what it cost, what it changed. The number at the end is what makes it a story rather than a claim.
Something you fixed under pressure
An incident, a deadline, a migration that went sideways. What you did first, what you chose not to do, and how you knew it was over.
A disagreement
With a peer, a manager or a customer. What they wanted, what you wanted, how it was settled. “I persuaded them” is a worse answer than “I was wrong about one part.”
Something that went wrong because of you
The one most people prepare worst. It needs a real failure, a real consequence, and a change you actually made afterwards — specific enough to be checkable.
Stage three
Say it out loud, to something that answers back
The gap between an answer you have thought about and one you have said is wider than people expect, and it closes in about two attempts.
Questions you did not choose
Generated from the real job description, so they land where the role lands rather than where you are comfortable. Mock interviews →
Scored, with the reason
Each answer marked, with what was missing — a number, a trade-off you skipped, a result you did not state.
Repeat the weak ones
The whole value is in the second attempt at a bad answer. How to run the practice loop →
And on the day
Preparation is most of it. The call is the rest.
When the interview itself starts, the same material — your CV, the job description, your documents — is what the live assistant answers from. Nothing is set up twice.
Questions
About preparing
How long before an interview should I start preparing?
Three evenings is enough for most roles, and more than three is usually spent re-reading things you already know. One to understand the job description and find where your CV is thin against it, one to write out the four or five stories you will keep reaching for, and one to practise saying them out loud against questions you did not choose.
What is the single highest-value thing to prepare?
Four stories from your own experience, each with a number in it, that can be bent to answer most behavioural questions: a thing you shipped, a thing you fixed under pressure, a disagreement you handled, and a thing that went wrong because of you. Almost every behavioural question is one of those four in a costume.
Is practising out loud actually different from thinking it through?
Yes, and it is the difference that shows up in the room. An answer you have only thought about is three bullet points; said out loud for the first time it comes out as ninety seconds of circling before the point. The gap closes after about two attempts, which is why two attempts beat an hour of reading.
How do I prepare for a technology I used years ago?
Write the specifics down rather than re-learning the subject. What it was, how big, who it was for, what went wrong, what you measured, what you would do differently. An interviewer is testing whether you were there; a refreshed overview of the technology does not demonstrate that, and three concrete details do.
Can I prepare from the job description alone?
You can get most of the way. A job description names the skills, the seniority and usually the team's current problem, and the questions follow from those. What it cannot tell you is where your own CV is weak against it, which is the part worth knowing — so the useful exercise is the two read side by side.
What should I do in the last hour?
Nothing new. Re-read the job description, re-read your own CV as a stranger would, say your four stories out loud once each, and stop. Anything learned in the last hour is not available under pressure, and the time is better spent arriving calm.
Read next
Related pages
Start with the job description.
Paste it in, see what it asks of you, and find out where your CV is thin — before someone else does.
Create your account