Why most people practise the wrong way
Most candidates prepare by grinding problems alone. That builds recall, but it skips the part that actually fails people in interviews: thinking out loud, handling pressure, and responding to a follow-up you did not expect. A mock interview is the closest you can get to the real thing without the stakes, so it deserves a plan rather than a few random sessions in the final week.
The goal of a mock plan is not to feel ready. It is to find the specific places where you go quiet, ramble, or freeze, and then close those gaps one at a time. A good plan is structured, repeatable, and honest about what is not working yet.
Set a target and work backwards
Start with the loop you expect to face. A backend role might include a coding screen, a system design round, and two behavioural conversations. A frontend role might swap system design for a UI build or a debugging exercise. Read your target job descriptions and list the rounds you are likely to get.
Then assign each round a confidence score from one to five. Be strict. A three means you can muddle through on a good day. Anything below a four needs deliberate practice. This scoring tells you where to spend time, so you are not over-preparing the round you already handle well.
A four-week structure works for most people:
- Week one: baseline mocks across every round type, no preparation, just to measure where you are.
- Week two: focused drills on your two weakest rounds.
- Week three: full mock loops that string rounds together, closer to interview conditions.
- Week four: light maintenance, sleep, and one or two final mocks to stay warm.
If you only have two weeks, compress weeks two and three and keep the baseline session. Skipping the baseline is the most common mistake, because it removes your only honest measurement.
Find partners and tools that push back
A mock interview only helps if the interviewer challenges you. A friend who nods along teaches you nothing. You have a few options:
- Peers in the same job search. Trade interviewer and candidate roles. The person interviewing learns just as much by watching for vague answers.
- Paid mock services. Platforms like Interviewing.io and Pramp connect you with engineers who run realistic loops, and some offer anonymous practice.
- An LLM as a practice interviewer. This is cheap and available at any hour. The trick is forcing it to behave like a real interviewer rather than handing you the answer.
A useful prompt for AI practice looks like this:
Act as a senior backend interviewer for a 45-minute coding round.
Give me one problem. Ask me to clarify before I code.
Push back on my approach with one follow-up before I write anything.
After my solution, probe edge cases and complexity.
Score me on communication, correctness, and how I handled ambiguity.
The point is to stop the model from being a polite tutor. Make it interrupt, question, and withhold approval.
Run each session like the real thing
Treat a mock as a dress rehearsal, not a study session. Set a timer. Use the same tools you will use in the real interview, whether that is a shared editor, a whiteboard, or a video call with screen share. Talk through your reasoning even when it feels awkward, because silence is what interviewers struggle to score.
Record the session if your partner agrees. Watching yourself is uncomfortable and extremely useful. You will catch filler habits, long pauses, and moments where you jumped to code before understanding the problem. These are invisible to you in the moment.
After each mock, spend ten minutes on three questions:
- Where did I lose the interviewer's confidence?
- What did I assume that I should have checked?
- What would have made my answer one level stronger?
Write the answers down. A practice plan without notes is just activity, and you will repeat the same mistakes.
Drill behavioural rounds with the same rigour
Engineers often over-index on technical rounds and wing the behavioural ones. That is a mistake, because behavioural rounds are where level and judgement get assessed. Build a small bank of stories covering conflict, failure, ownership, ambiguity, and influence. Practise telling each in two minutes with a clear situation, action, and result.
In a mock, have your partner ask follow-ups like "what would you do differently" or "how did the other person react". The follow-ups are where weak stories collapse, so that is exactly where you want the practice.
Track progress and know when to stop
Keep a simple log: date, round type, confidence before, confidence after, and the single biggest fix. Over a few weeks you will see scores climb, and you will see which round refuses to improve. That stubborn round is where to book a paid mock with a real engineer, because it usually signals a blind spot you cannot see alone.
Stop ramping in the final two days. More cramming raises anxiety and lowers performance. A short, easy mock the day before keeps you warm without draining you. The plan has done its job when your weakest round sits at a four and you can explain your thinking under time pressure without going quiet.
Continue your prep
Pair your mock plan with role-specific material and sample answers: