Mock interviews: how to prepare and use the feedback
A mock interview is only as useful as what you do before and after it. How to prepare so it feels real, what to ask the interviewer, and how to turn the feedback into practice.
Share on WhatsApp
Conceptual image · created with AI
Real interviews rarely explain why you were rejected. A mock interview can, which makes it one of the most useful hours in a job search. But many people treat it as a casual chat, hear some kind words, and change nothing. The value is not in sitting the mock. It is in preparing as if it were real and acting on what you hear.
This guide covers the three parts: preparing so the mock tests what a real interview would, getting honest feedback out of the interviewer, and turning that feedback into practice before your next real one.
What you should come away with
- Prepare for a mock exactly as you would for a real interview, or it will not tell you much
- Give the interviewer a real posting so they can play a real role
- Ask for the two things most worth fixing, not general impressions
- Write the feedback down within an hour, in your own words
- Practise the weakest answer aloud until it is easy
- Book a second mock two or three weeks later to check what changed
Start by choosing a real target. A mock interview for 'a job' is too vague to be useful. Pick one kind of role, ideally one real posting, and give it to the interviewer in advance along with your resume. A mock for a graduate engineer trainee role, a junior data analyst role or a customer support role will each test different things, and the interviewer can only play the part well if they know which one they are playing.
Then prepare as you would for the real interview, because a mock you have not prepared for mostly tells you that you had not prepared. Read the posting and list what it asks for. Prepare a one-minute introduction that says who you are, what you are looking for and why. Revise the fundamentals of the role. Be ready to explain every project on your resume: the problem, what was built, which part was yours, what went wrong and what you would change. Prepare four or five real stories from college, projects, internships or work that show how you handle a deadline, a disagreement or a mistake, each told as the situation, what you did and what happened.
Prepare the awkward answers too. If you have a backlog, a gap year, a change of field or a low percentage, you will be asked about it, and a mock is the safest place to practise saying it calmly. A short, honest answer that ends with what you did next is almost always better than an evasion.
Treat the setting as real. Dress as you would for the interview. Arrive or join on time. If the mock is on video, test your camera and microphone, sit somewhere quiet, and put the camera at eye level. Have your resume and the posting in front of you. The more real it feels, the more the mock will show you how you behave under real pressure, which is the thing you cannot find out on your own.
During the interview, think aloud. Interviewers cannot assess reasoning they cannot hear, and many candidates lose marks not because their answer was wrong but because they went silent for a minute and then produced it. If you do not understand a question, ask what was meant. If you do not know something, say so and explain how you would find out. A mock is the place to practise these habits, so use it.
When the interview ends, the useful part begins. Ask for feedback directly, and ask specific questions rather than 'how did I do?'. Which answer was weakest, and why? What would have made my project explanation clearer? Was there a point where you stopped following me? If this were a real interview, what would have worried you? And the most useful question of all: what are the two things most worth fixing before my next interview? Interviewers who volunteer for mocks are usually glad to be asked properly, and a direct question gets a more honest answer than a general one.
Listen without defending yourself. It is natural to explain why you answered as you did, but every minute spent explaining is a minute of feedback you do not hear. Say thank you, ask a follow-up question if something is unclear, and save your own view for later.
Write the feedback down within an hour, in your own words, while you still remember the exact questions. Note the questions you were asked, the ones you struggled with, and the two things the interviewer said to fix. If you were given a written note, add your own notes to it. Feedback you do not write down tends to shrink to a vague feeling within a few days.
Then turn it into a plan for the next two weeks. If your project explanation was weak, rewrite it as a two-minute account and say it aloud ten times, to a friend or to your phone. If you went silent on technical questions, practise solving problems aloud, narrating each step. If your behavioural answers wandered, structure each of your stories and time them. If your introduction was too long, cut it to a minute. Work on the two most important things, not on everything at once.
An AI chatbot can help with volume, asking you practice questions at any hour, and that is worth doing. But it cannot see that you look lost or hear that you rushed, so keep at least one more round with a person.
Finally, book a second mock two or three weeks later, ideally with a different interviewer, and tell them what you were working on. If the same problem comes up again, you know where to keep working. If it does not, you have evidence that the practice worked, which is the most reliable kind of confidence there is.