How to prepare for an interview in one week

You cannot learn a subject in a week, but you can absolutely become interviewable in one. The difference is rehearsal, not revision.

Most people spend the week re-reading things they already half-know, because reading feels like progress and speaking out loud feels stupid. Then they sit down in the interview and discover that knowing something and being able to say it under mild fear are unrelated skills.

Here is a week that fixes the second one.

Day 1 — turn the job description into a checklist

Print the job description. For every requirement, write one of three things next to it: have it, have something close, do not have it.

That page is now your syllabus. You are not preparing for "an interview", you are preparing for the eight things this specific company wrote down. Anything not on the page is optional.

The have something close row is where interviews are won. Those are the answers you need to build carefully, because they are true but need framing.

Days 2 to 4 — rehearse out loud, not in your head

Pick your six most likely questions. For each, say the answer aloud, once, without stopping. Record it if you can bear to.

You will hear immediately what you cannot hear while thinking: the sentence that runs for forty seconds without a verb, the story with no ending, the part where you say "and yeah, so" three times.

Rehearsing in your head only ever practises the version that already works.

The STAR problem

Everyone is told to use Situation, Task, Action, Result. Most people then spend ninety seconds on Situation and ten on Result, which is exactly backwards.

The interviewer needs about one sentence of context. What they are actually assessing is the Action — what you specifically decided and did — and whether the Result is real. Cut the setup ruthlessly and spend the time on the decision you made.

If you cannot say what you personally decided, it is not your story to tell.

Day 5 — one mock under real conditions

Real conditions means: camera on, out loud, no notes, someone else asking, and no restarting when you fumble. Fumbling is the thing you are practising.

A mock you can pause is a reading exercise. The whole value is in recovering mid-sentence, because that is what actually happens on the day.

Day 6 — prepare the questions you ask them

Three questions, none of which are answered on the careers page. Good ones tend to be about how the team actually works: what does a bad week look like here, what is the thing that most surprises new joiners, how does this role get judged after six months.

This is also the only part of the interview where you are assessing them, and after a week of being examined it is easy to forget you are allowed to.

Day 7 — stop

Do not cram the night before. Re-read your checklist once, then leave it. Tired and rehearsed beats exhausted and over-prepared, every time.

If you only have two days

Do Day 1 and Day 5. The checklist and one honest mock will get you most of the value. Skip the rest without guilt.

What preparation cannot fix

It cannot make you qualified for a role you are not qualified for, and it cannot make you want a job you do not want — which comes across more clearly than most people believe.

What it can do is remove the gap between what you know and what you manage to say. That gap is usually the whole difference between two candidates with the same CV.

If it helps to have the week laid out and something keeping you to it, that is what KyzenX does — and its Interview Coach runs the mock, out loud, and tells you where the answer fell apart.