Turning resume bullets into interview answers
Everything on your resume is an invitation to a question. Preparation is mostly deciding what you will say when it is taken up.
Interview preparation usually gets treated as a separate exercise from the resume. It is not. Your resume is the agenda: interviewers read it beforehand, mark the things that interest them, and ask about those. Preparing well is mostly a matter of taking your own document seriously as a list of forthcoming questions.
Audit your own page
Go through your resume and mark every claim that would make a reasonable person curious. Every figure. Every strong verb. Every gap, transition or short tenure. That list is close to the actual interview.
For each item, be able to answer three things: what was the situation, what did you specifically do, and how do you know it worked. The third is where most answers collapse — people can describe what they did and go vague on how the outcome was established.
Answer at the right altitude
The most common interview failure is not a wrong answer but an answer pitched at the wrong level of detail. A question about how you turned a function around is asking for the approach and the judgement calls, not a chronological account of eighteen months.
So I joined in March, and the first thing was we had a lot of issues with the reporting, and then in about May we started looking at the systems, and there was a lot of resistance from the team…
Three problems: reporting nobody trusted, no clear ownership, and a team that had been through two restructures. I fixed ownership first, because the other two were downstream of it. Took about nine months. Happy to go deeper on any of those.
Structure, then the offer to expand. The interviewer picks the branch, and you have not spent four minutes on the part they did not care about.
Two minutes is a long answer. Land the structure, then stop and let them steer.
Prepare the uncomfortable ones deliberately
- The short tenure. State the reason plainly, without defensiveness, and move on. Length of explanation signals discomfort more than the fact does.
- The gap. Say what it was. Redundancy, caring responsibilities, illness, a deliberate break — all of these are ordinary. Vagueness is what makes them sound like something else.
- The thing that failed. Have one real answer ready, with what you would do differently. A candidate at senior level who has never got anything wrong is not credible.
- Why you are leaving. Forward-looking, never a criticism of your current employer, even when the criticism is deserved.
Bring the document with you
Take a printed copy and let yourself refer to it. It is not a memory test, and an interviewer watching you check a figure rather than guess at it reads that as precision.