Most interviewers are not working from a prepared question bank. They have your resume open in front of them, and they are asking about the things on it that look interesting or unclear.
That is unusually good news, because it means you wrote the agenda. Every bullet is a question you have invited. Preparing for an interview is largely a matter of making sure you can answer each one well.
The core exercise
Print your resume. For every bullet, write two or three sentences answering: what was the situation, what did I personally do, and what happened as a result. Then say it out loud once.
This takes about an hour and does more than any list of common interview questions. Two things fall out of it:
- You find the bullets you cannot defend. Every resume has one or two claims that sounded fine while writing and collapse when spoken. Better to find them now than in the room. Sometimes the right response is to soften the bullet.
- You stop groping for examples mid-answer. Most rambling in interviews is retrieval, not thinking. Once the stories are loaded, answers get shorter and more specific.
The questions that come from the page
| Question | What they are actually checking |
|---|---|
| Walk me through your resume. | Whether you can tell a coherent story with a direction, in under three minutes. |
| Tell me more about this project. | Whether the bullet is yours, and how deep your involvement went. |
| How did you measure that 40% improvement? | Whether your numbers are real and whether you understand what you measured. |
| Why did you leave this role? | Risk. They want a neutral reason, not a grievance. |
| You were there ten months — what happened? | Whether short tenure was circumstance or pattern. |
| What was the gap in 2024? | Nothing sinister. They just want the ambiguity closed. |
| You list Kubernetes. What have you done with it? | Whether your skills section is honest. |
The walk-through answer
Almost every interview opens with some version of this, and almost everybody handles it badly — either a two-word summary or a nine-minute chronology from university onwards.
Aim for 90 seconds to two minutes, structured as a direction rather than a list:
- Where you started, in one sentence
“I started in operations at a logistics company, mostly reporting.” No detail, no dates.
- The turn
The moment your direction became deliberate. “I kept building the analysis nobody else was doing, so I moved into the data team.” This is what makes it a story rather than a chronology.
- What you do now, with one concrete result
The single achievement closest to the job you are interviewing for.
- Why you are here
One sentence connecting the trajectory to this role. This is the part that makes the interviewer feel the conversation has a point.
Answering about gaps and departures
These feel high-stakes and are usually low-stakes, provided you answer briefly and without defensiveness. The pattern that works: state it plainly, add one sentence of context, then return to the work.
Why did you leave?
Works
- The team was reorganised and my role moved away from the technical work I wanted, so I started looking. I stayed through the handover.
- I took eight months out for caregiving. I kept up with the field and did two contracts towards the end before looking for something permanent.
- It was a ten-month stint — the company changed direction two quarters after I joined and the role I was hired for stopped existing.
Avoid
- My manager was difficult and the culture was quite toxic, honestly.
- I would rather not go into it.
- I was looking for a new challenge and an opportunity to grow professionally.
The first weak answer creates a risk in the interviewer's mind that has nothing to do with your competence. The second creates a bigger one. The third is so generic it reads as concealment — which is the opposite of the intent.
Keeping answers the right length
The most common failure in behavioural interviews is not weak content, it is length. A four-minute answer buries the good part.
- Situation and task in two sentences. Enough context to make the action legible, no more.
- Action gets the bulk. This is what they are assessing. Say “I”, not “we”, when describing your own decisions.
- Result with a number, and one sentence on what you would do differently. The reflection is what separates senior answers from junior ones.
- Then stop. Around 90 seconds. Silence after an answer is the interviewer thinking, not an invitation to keep going.
Prepare your own questions from their posting
The end of the interview is the part candidates waste. Generic questions about culture get generic answers. Questions drawn from the posting land differently, because they show you read it as a description of real work.
- “The posting mentions consolidating reporting across teams — how far along is that?”
- “What does the first 90 days look like for whoever takes this?”
- “What is the thing about this role that people underestimate?”
- “Who would I work with most closely, and what do they need from this role?”
Take the answers seriously as information, not just as your turn to look engaged. This is where you find out whether you actually want the job — which matters, because the point of tailoring the resume and preparing the stories was never to get any offer. It was to get the right one.
Frequently asked questions
How do I answer “walk me through your resume”?
In 90 seconds to two minutes, as a direction rather than a chronology: where you started in one sentence, the moment your path became deliberate, what you do now with one concrete result, and why this role is the next step. Group early roles together and spend your time on the most recent two.
How should I explain an employment gap in an interview?
State it plainly, add one sentence of context, and return to the work: “I took eight months out for caregiving, kept up with the field, and did two contracts before looking for something permanent.” Brevity signals it is genuinely not an issue; over-explaining suggests otherwise.
What if an interviewer asks about a skill I overstated on my resume?
Answer honestly and immediately — describe exactly what you have done with it and where the limits are. Interviewers respect a clear boundary far more than a vague answer, and they detect the vague answer nearly every time. The real fix is upstream: only list skills you would be happy to be tested on.
How long should an interview answer be?
About 90 seconds for a behavioural question. Two sentences of situation, the bulk on what you specifically did, a result with a number, and one line of reflection. Then stop — a pause afterwards is the interviewer thinking, not a prompt to continue.
How many prepared stories do I need for an interview?
Around six, covering a hard technical problem, a conflict, a failure, a leadership moment, a project you owned, and a time you changed your mind. Most questions are variations on those themes, so a small set of well-rehearsed stories can be angled at nearly anything.