A four-week interview preparation plan that works

Most interview preparation consists of reading a list of common questions and nodding at the model answers. It feels productive and changes almost nothing, because reading an answer and delivering one under pressure are different skills.

Here is a preparation plan built around the skills that are actually tested. It assumes about a week and roughly forty-five minutes a day.

Day 1 — Read the job description as a test spec

The posting is not marketing copy; it is a list of the things they intend to assess. Go through it line by line and convert each responsibility into the competency behind it.

"Coordinate across engineering and commercial teams" is a stakeholder-management question waiting to happen. "Operate in a fast-moving, ambiguous environment" means you will be asked about a time you made a decision without enough information.

Write the resulting list. Six to eight competencies is typical. Everything else this week is built from that list.

Day 2 — Build a story bank, not a script

You do not need a unique answer per question. You need five to seven real experiences you know deeply:

• Something you delivered that went well
• Something that went badly, and what you changed afterwards
• A disagreement with a colleague or a stakeholder
• A time you changed your mind because of evidence
• Something shipped under a hard constraint or deadline
• A time you influenced without authority
• Something you taught, mentored or handed over

For each, write down the messy details: names of systems, actual numbers, real dates, what was genuinely uncertain at the time. You will not say all of it, but a story you know in detail can be re-cut for many questions, while a memorised answer breaks the moment the question is phrased differently.

Day 3 — Structure each story

Use STAR (Situation, Task, Action, Result) or CARL (Context, Action, Result, Learning). The framework is not there to make you sound like a robot; it exists to prevent the single most common failure in interview answers — three minutes of setup and fifteen seconds of outcome.

Practical proportions for a two-minute answer: about twenty seconds of context, seventy to eighty seconds on what you specifically did, and twenty to thirty seconds on the result and what you took from it.

Watch your pronouns. "We migrated the database" tells the interviewer nothing about you. "I owned the cutover plan and ran the rollback rehearsal" does.

Day 4 — Attach numbers, and be able to defend them

"Improved performance" is invisible. "Cut median page load from 4.1s to 1.3s, measured on our real-user monitoring" is memorable — and it invites a follow-up question you must be able to answer. Never quote a figure you cannot explain the source of. If you do not have a number, describe the change concretely instead of inventing precision.

Day 5 — Rehearse out loud, on the clock

This is the day people skip, and it is the day that matters. Say your answers aloud, timed, ideally recorded. You will discover three things immediately: your answers run long, you say "basically" more than you thought, and the story that reads well on paper has a confusing middle.

Play back one answer — the worst one. It is uncomfortable and it corrects faster than any amount of re-writing.

Day 6 — Rehearse the questions you cannot predict

Have someone ask you questions you have not prepared, or use a mock round in a tool like Employ Ready. The skill you are building is not recall; it is composure while composing. Practise saying "let me take a second to think about that" out loud, because the first time you say it should not be in the real interview.

Also prepare your own questions. Ask about how the team makes decisions, what the first ninety days look like, and what would make them regret the hire. Asking nothing reads as indifference.

Day 7 — Logistics and one light pass

Confirm the format, the platform, the names of the people, and how long it will run. Test your camera and microphone if it is remote. Re-read your competency list and story bank once — do not cram new material the night before.

During the interview

• Answer the question that was asked, then stop. Silence is the interviewer's turn.
• If you do not understand the question, ask for clarification. It reads as senior, not uncertain.
• When you do not know something, say so and describe how you would find out.
• Take notes. It slows you down in a useful way.

Afterwards

Write down every question you were asked, within an hour, while it is fresh. Whatever the outcome, that list is the highest-value preparation material you will ever have for the next one.