How to practise mock interviews: a four-week plan for placement season

That gap is why a candidate who has solved hundreds of problems can still freeze on "why did you pick that approach?" Knowing something and explaining it under questioning are two different skills. Silent prep builds the first. Only practice that makes you speak, and then pushes back, builds the second.

This guide covers what makes a mock interview worth your time, the honest pros and cons of each way to get one, and a four-week plan you can start this week.

Why silent prep is not enough

When you solve a problem alone, you can pause for ten minutes, reread the question, and try three ideas without anyone noticing. You never have to put your reasoning into sentences. In an interview, every pause is visible, every half-formed idea has to be said, and the follow-up question usually lands exactly where your understanding is thinnest.

Reading answers also gives you a false sense of readiness. An explanation that feels obvious on the page often comes out jumbled the first time you say it aloud. You only find that out by saying it, ideally to someone who will interrupt.

What makes a mock interview useful

A mock that only tells you "good job" is a rehearsal, not practice. A useful one has five things:

• Realistic follow-ups. The interviewer digs into the weak part of your answer instead of moving to the next question.
• Timing. A real round has a clock. Your mock should too, so you learn how long your answers actually take.
• Being made to speak. You answer out loud, in full sentences, not by pointing at notes or typing.
• Written feedback you can act on. "Be more confident" is not actionable. "Your answer on indexing stopped at the definition and never said when an index hurts writes" is.
• Repetition. One mock shows you the problems. The second and third, on the same weaknesses, are where you actually fix them.

Your options, compared honestly

No single option is best for everyone. Most people end up mixing two or three. Here is what each one is good and less good at.

Friends and classmates

Good: free, easy to schedule, and you can swap roles, which teaches you what interviewers notice. Less good: friends tend to go easy on each other, they are often preparing the same topics at the same level, and feedback is usually vague. Fix this by giving your partner a list of follow-ups to ask and asking them to write down where you hesitated.

Seniors and alumni

Good: they have sat real rounds recently, know what panels ask, and can tell you how your answers compare. Less good: their time is limited, so you may get one or two sessions in a season, and you depend on their schedule. Save these sessions for later in your prep, when you have something polished for them to test.

College T&P or placement cell sessions

Good: often structured, sometimes run by faculty or visiting professionals, and they mimic the formal setting well. Less good: availability varies a lot between colleges, slots can be few for a large batch, and feedback may be brief. Attend whatever your cell offers and treat it as one data point, not your whole plan.

Paid human mock interview platforms

Good: you get an experienced interviewer who is not your friend, which means real pressure and usually detailed feedback. Less good: each session costs money, so most students can afford only a few, and quality depends on which interviewer you get. They work best as a checkpoint once you have fixed the obvious problems elsewhere.

AI mock interviews

Good: available any time, so you can do one late at night or three in a week without arranging anything, and you can retest the same weakness as often as you need. The better ones run as a spoken conversation with follow-ups and give you a written report. Less good: an AI interviewer cannot fully replace the feel of a person across the table, and quality varies between products. Check that the one you use makes you speak, asks follow-ups, and gives specific feedback rather than a generic score.

The four-week plan

This plan assumes you are also studying alongside it. Two to three mocks a week is realistic for most students. More than four usually means you are not spending enough time reviewing and fixing between them.

Week 1: take a baseline

Do one or two full mocks before you feel ready. That is the point. You are measuring where you are, not trying to perform. Pick the round you expect first in your process, sit it under real timing, and record it. Start with your self-introduction, since almost every round opens with it; our guide to answering "tell me about yourself" has a structure you can use.

At the end of the week, list every moment an answer broke down. This list is your plan for week 2.

Week 2: targeted fixes

Take the three biggest problems from your baseline and work on only those. If you could not explain your project's architecture, write a two-minute explanation and say it aloud until it is clean. If you went silent while coding, practise narrating your decisions using the steps in our guide to thinking aloud in a coding interview. End the week with two mocks that deliberately push into those three areas.

Week 3: round-specific mocks

Most processes have more than one kind of round, and each needs its own practice. Aim for two or three mocks this week, one per round type you expect:

• Technical discussion: fundamentals from your subjects plus deep questions about your own projects. Expect "why did you choose this?" more than "what is this?"
• Coding: a timed problem with a shared editor, explaining your approach before writing code and stating complexity at the end.
• System design: if your role includes it, practise clarifying requirements and drawing a simple design you can defend. Our system design plan for freshers covers where to start.
• HR: strengths and weaknesses, a time you handled a conflict, why this role. Short, specific stories work better than general claims.

Week 4: full dress rehearsal

Run one or two mocks exactly as the real day will go. Same clothes, same room, camera on if the interview is online, phone in another room. Keep strict timing, including the gaps between rounds if you will have more than one. Do not pause the mock to look something up. In the last two or three days, stop adding new topics and only revisit your notes from earlier mocks.

The review loop: where the improvement actually happens

A mock without review is just a stressful hour. The useful part is what you do in the thirty minutes after it. Use the same loop every time:

1. Write down two or three moments the answer broke. Be specific: the question, what you said, and where it went wrong. "Weak on DBMS" is too broad. "Could not say why a composite index helps one query and not another" is something you can fix.
2. Fix those moments, and only those. Read up, then write and say a better answer aloud until it comes out cleanly.
3. Retest the same weakness in your next mock. Tell your partner what to probe, or choose the topic yourself. If it holds up, it comes off the list. If not, it stays.

Keep all of this in one running document. By week 4 it becomes the most useful revision sheet you have, because it is made entirely from your own mistakes.

Record yourself

Record at least one mock a week, audio is enough, and listen back once. It is uncomfortable, and that is why it works. You will hear filler words, answers that go on long after the point was made, and pauses that felt short but were not. Note the two worst habits and watch for them in the next mock.

How to simulate pressure

Practising in comfort trains you to perform in comfort. A few simple ways to raise the stakes:

• Use a timer you can see, and stop when it runs out even if you are mid-answer.
• Ask your partner to interrupt with "why?" or "what if the input doubles?"
• Practise with someone you do not know well, such as a senior from another branch.
• Start mocks at the time of day your real interviews are scheduled.
• Sit at a desk with the camera on, not lying on your bed with notes nearby.

Common mistakes

• Too many mocks, no review. Five mocks a week with no notes teaches you to repeat the same mistakes faster. Fewer mocks with a proper review loop beats more mocks without one.
• Only practising your strengths. It feels good to do well in a mock. It is more useful to do badly in one on the topic you have been avoiding.
• Memorising scripts. Interviewers can tell when an answer is recited, and the first follow-up breaks it. Prepare the points you want to cover and practise saying them in different words each time.
• Waiting until you feel ready. You will not feel ready before your first mock. Take the baseline anyway.

Practising with Meera on mangoose.tech

mangoose.tech is one way to fit AI mock interviews into this plan. You pick the role and the round (technical discussion, coding, or system design), then sit a live interview with Meera, speaking your answers out loud in English. Meera follows up on the thin parts of your answer the way a panel does. Coding rounds open a code editor Meera can see, and system design rounds open a whiteboard.

Afterwards you get a written gap report that marks the specific moments your answer weakened, with what to do differently. That slots straight into the review loop above. Live roles are Software Engineering, AI Engineering, Gen AI Engineering, Data Engineering, Frontend Engineering, DevOps & Platform, and Data Science & ML.