How to prepare for an interview without memorising scripts
Most interview advice tells you to rehearse answers. That is the wrong target. Rehearsed answers sound rehearsed, and the moment the question is phrased slightly differently, the script falls apart. What works is preparing material rather than answers: six or seven real situations from your own work that you know in detail, which you can reshape to fit whatever is actually asked.
The STAR structure, and why interviewers use it
Behavioural questions all follow the same logic: past behaviour is the best available predictor of future behaviour. Interviewers are usually trained to score answers against four elements, which is why the STAR structure exists:
- Situation — the context, in one or two sentences. Where, when, what was at stake.
- Task — what you specifically were responsible for. Not the team, you.
- Action — what you actually did, step by step. This should be the longest part.
- Result — what changed, with a number wherever you have one.
The two elements people skip are Task and Result. Skipping Task makes it unclear whether you did the work or watched it happen. Skipping Result leaves the interviewer with a story and no outcome, which scores as neutral at best.
Build a story bank, not a script
Before an interview, write out six to eight situations from the last few years, each with the STAR elements filled in. Choose them so they cover a spread: a success, a failure, a conflict, a deadline, something you led, something you learned. Almost any behavioural question can be answered from a bank like that, because interviewers are asking about the same handful of underlying qualities in different words.
Talk about failure properly
"Tell me about a time you failed" is not a trap, and the wrong answer is a disguised strength like "I care too much about quality". Interviewers are checking two things: whether you can recognise a real mistake, and whether you changed anything afterwards. Pick a genuine failure with real consequences, own your part in it plainly, and spend most of the answer on what you did differently next time.
The salary question
If asked early for a number, it is reasonable to ask what range the role is budgeted for — many employers now publish it, and in a growing number of places they are required to. If you must give a number, give a researched range rather than a single figure, and base it on the role and market rather than on what you currently earn.
Always have questions for them
"Do you have any questions for us?" is part of the assessment, not the wind-down. Having none reads as low interest. The strongest questions are specific to the conversation you have just had, and they tell you something you actually need to know: what success looks like in the first six months, why the role is open, how the team handles disagreement, what the interviewer finds hardest about working there.
Practical things that change outcomes
- Reread the job posting the morning of the interview. The vocabulary it uses is the vocabulary the interviewer will use.
- Have your resume in front of you. You will be asked about specific lines on it, and hesitating over your own history is costly.
- Prepare for the gaps. If your resume has a career break, a short tenure or a change of field, expect the question and have a calm two-sentence answer ready.
- For video interviews, test the setup on the actual platform, not a different one, and put the camera at eye level.
- Write down the interviewers' names when they introduce themselves.
Frequently asked questions
Are my answers saved anywhere?
They save in your own browser's local storage so you can come back to them. Nothing is uploaded, nothing is associated with you, and clearing your browser data removes them. That is also why there is no login.
How long should an answer be?
Ninety seconds to two minutes for a behavioural question. Much shorter and you have not given enough detail to score; much longer and the interviewer stops tracking the thread. Reading a draft aloud is the fastest way to check.
Should I use the same story twice?
Try not to. If you keep returning to one project, the interviewer learns about one project rather than about you. That is exactly why a bank of six to eight situations is worth building.
