The Complete Interview Preparation Framework

Two candidates with identical experience will get different outcomes from the same interview, and the difference is almost never intelligence. It is preparation: whether they have their evidence organised, whether they answer the question that was asked, and whether they can explain their reasoning out loud without losing the thread.

The good news is that this is trainable. What follows is the system we run with coaching clients, condensed into something you can do alone in a week.

Start with the right frame

An interview is not an examination with a pass mark. It is two parties testing a hypothesis: that this person and this role are a good fit. Interviewers are not trying to catch you out — they are trying to reduce the risk of an expensive mistake, and most of them are nervous about getting it wrong.

Two consequences follow. First, you are allowed to ask clarifying questions; doing so demonstrates exactly the behaviour they want at work. Second, you are also assessing them. Candidates who genuinely evaluate the employer interview better, because the desperation drains out of their answers.

Research that actually helps

Reciting the company's founding year impresses nobody. Useful research produces three specific things.

1. A model of how they make money. Who pays, for what, how often, and what would grow that number. For a product company, try the product. For a service business, read the case studies. For a public company, skim the latest results presentation — the strategy slides tell you what leadership is worried about.
2. A view of where your role sits. Read the advert as a document written by someone with a problem. What is the problem? A new team, a backlog, a departure, a regulatory deadline? Your answers should keep returning to it.
3. Two intelligent questions. Not "what does a typical day look like", but questions that could only be asked by someone who has done the reading.

Build a story bank once

Most interview panic comes from trying to retrieve a relevant example in real time. Solve it once: write 8–12 stories from your career, each in five or six sentences, and reuse them across every interview you do for the next two years.

Cover these situations:

• A result you are proud of, with a number attached
• A failure and what changed afterwards
• A conflict with a colleague or stakeholder
• A time you influenced without authority
• A deadline you saved, and one you missed
• A decision made with incomplete information
• Something you taught, mentored or documented
• A process you changed
• Feedback that stung and what you did with it
• The most technically or intellectually demanding thing you have done

One story often answers four different questions. Tag each with the competencies it demonstrates — ownership, collaboration, judgement, resilience — so you can retrieve it by theme rather than by memory.

STAR without the rambling

STAR — Situation, Task, Action, Result — is standard because it works. It fails when candidates spend 80% of the answer on context. Here are the proportions that work:

Two failure modes to watch for. The first is "we": if the whole story is what the team did, the interviewer cannot score you. Say "I" for your actions and "we" for the context. The second is the missing result — an answer that stops at "and then we launched it" leaves the most valuable part unsaid.

Aim for 90 seconds to two minutes. Then stop and let them probe. The follow-up questions are where the real assessment happens, and they are much easier to answer well than a monologue.

The competency round

Behavioural interviews are scored against a rubric. Interviewers are usually told to look for evidence at a particular level, which is why they keep digging with "and what did you do then?" They are not being hostile; they are filling in a scorecard.

Questions you should have an answer ready for:

• Tell me about a time you disagreed with your manager.
• Describe a project that did not go to plan.
• Give me an example of prioritising under conflicting pressure.
• When did you last change your mind about something important?
• Tell me about working with someone difficult.
• What is the most significant piece of feedback you have received?

On the failure question specifically: choose a real one with real consequences, own your part without theatrical self-criticism, and spend most of the answer on the change you made afterwards. A candidate whose worst failure is "I care too much about quality" reads as either evasive or lacking self-awareness.

Technical and case rounds

The content differs by discipline, but the assessment is remarkably consistent: can you structure an ambiguous problem, communicate while you work, and recognise trade-offs?

1. Restate the problem in your own words and confirm the constraints. Ten seconds that prevent ten wasted minutes.
2. Ask clarifying questions — scale, users, data volume, budget, who the stakeholders are. Candidates who dive straight in score lower even when the answer is right.
3. Say your plan before executing it. "I'll start with the data model, then the read path, then talk about caching." Now the interviewer can steer you.
4. Narrate your reasoning, including dead ends. Silence is the biggest scoring risk in a technical interview.
5. Name the trade-offs explicitly. Every real solution sacrifices something; saying so is what separates a senior answer from a textbook one.
6. Finish with what you would do next given more time.

Questions worth asking

You will be offered time for questions in every round. Have five ready and ask two or three that fit the interviewer.

• What does someone need to achieve in the first six months for this to be a clear success?
• What is the biggest constraint the team is working under right now?
• How are decisions made when the team disagrees on priorities?
• What happened to the last person in this role?
• Which part of this job do people usually find hardest?
• How is performance reviewed, and how often does it translate into pay?

Do not ask about holiday allowance in the first round, and do not ask a question that the careers page answers. Save compensation for the recruiter, who expects it and can actually answer.

After the interview

• Within an hour, write down every question you were asked while it is fresh. This is how your preparation improves across a search.
• Within 24 hours, send a short thank-you note — four sentences, one of which adds something you wish you had said. It rarely wins the job, but it is remembered.
• If you are rejected, ask once, politely, for one thing you could have done better. Perhaps a third of recruiters answer, and that answer is worth more than a week of generic advice.
• Keep going. A search is a sequence of independent events. The rejection you received this morning has no bearing on the interview you have this afternoon.

Preparation will not make an unsuitable role suitable. What it does is make sure that when the fit is right, nothing about your delivery hides it.