Interviews · 5 min read
The interview prep that actually moves the needle
A lot of interview preparation is spent on the wrong things. Memorising scripted answers makes you sound rehearsed, and reciting a company About page rarely helps. The preparation that actually changes the outcome is more useful, and usually less work, than the kind most people do the night before. It also makes you calmer on the day, because it is built on what you genuinely know rather than what you crammed.
Understand the role, not just the company
It is easy to read about a company. It is far more valuable to understand the specific role: what it exists to do, what good looks like in it, and what the team is quietly struggling with.
When you understand the work, you can talk about their problems instead of your history. That is what an interviewer is really listening for, even when the question is about you. They are working out whether you get it.
You can usually piece this together from the job ad, the company website, and a little thought about why the role is open at all. A newly created role and a replacement are rarely looking for quite the same person.
Build a small set of strong stories
Most interview questions are variations on a few themes, so you do not need a different answer for each one. You need four or five real examples from your own experience that you can adapt on the spot.
Pick stories that show range, and know each one well enough to tell it without notes.
- A result you are genuinely proud of
- A problem you solved under pressure
- A time you worked through a disagreement
- A mistake, and what you took from it
With these ready, most questions become a matter of choosing which story fits, not inventing an answer from nothing.
One story can answer several questions
This is why stories beat scripted answers: one good example stretches a long way. A project you turned around can answer "tell me about a challenge", "a time you led", "a time under pressure", and "something you are proud of", with a different emphasis each time.
So you are not memorising twenty answers. You are learning five strong stories well, then choosing the angle that fits the question in front of you. That is far less work, and it never sounds rehearsed.
Practise out loud, not in your head
Answers feel clear in your head and fall apart the moment you say them. Practising out loud, ideally to another person, exposes the rambling and the gaps fast. You do not need to over-rehearse. Two or three run-throughs of your key stories is enough to make them feel natural rather than memorised.
If you cannot find someone to practise with, record yourself on your phone and play it back. It is uncomfortable, and it is the fastest way to hear the tangents and the answers that never quite reach a point.
Prepare your own questions
The questions you ask are part of how you are judged, and they tell you whether you actually want the job. Have a few ready that go past the obvious: how the team works, what success looks like in the first months, where the role is heading.
Asking nothing suggests you are not really interested, or have not thought about it. Asking something thoughtful does the opposite.
Sort the practical things
Nerves are worse when the logistics are uncertain, so take them off the table the day before.
- Test your camera, microphone and link if it is remote
- Know the names and roles of who you are meeting
- Have your resume and a few notes within reach
- Plan to arrive, or log on, a few minutes early
On the day, slow down
Under pressure, people rush. Take a breath before you answer, and remember it is completely fine to pause and think, or to ask for a question to be repeated. A considered answer delivered calmly beats a fast one delivered in a panic every time.
The short version
Preparation is not a script. It is knowing the role, having your stories ready, removing every avoidable distraction, and giving yourself room to think on the day.