How to run a useful mock interview

Updated October 2026 · 484+ words · By MatchMyInterview Team

A mock interview is useful when it feels slightly uncomfortable and still stays kind. You need a clock, a role, and a person who will interrupt you.

Agree the format before you start. Forty-five minutes is enough for most first sessions: five minutes to set context, twenty-five minutes of interview, ten minutes of reverse interview, five minutes of verbal feedback. Write the agenda in chat so neither of you drifts.

Pick one role. “Software engineer” is too broad. “Backend engineer, Java, 0–2 years” is usable. Share a job description or a short list of skills. If you do not have a posting, invent a realistic one and stick to it.

The interviewer should prepare eight questions and expect to use five. Mix a walk-through of a past project, one debugging or case prompt, and one communication check such as explaining a trade-off to a non-engineer. Leave room for follow-ups. The value is in the second question, not the first.

The candidate should treat it as live. Open a blank note, think out loud, and ask clarifying questions. If you freeze, say so and restart the thought. That is closer to a real round than a memorised speech.

After you switch roles, submit written feedback the same day. Rate communication, problem solving, and role knowledge separately. One specific example is worth more than a paragraph of praise. Then book the next session while both calendars are open.

Do this twice a week for a month and you will have a trail of evidence — which questions hurt, which stories landed, and which skills peers actually observed. That trail is what MatchMyInterview is for.

Common mistakes: arriving with no job description, spending twenty minutes on introductions, skipping the reverse interview, and never writing feedback. If you only have thirty minutes, cut introductions, not the write-up.

For technical roles, keep a shared notepad. Paste the prompt. Ask the candidate to restate constraints. If they jump to code, pause them and ask for an approach first. That single habit mirrors most real onsite rounds.

For consulting, product, finance, HR, and government exams, the same skeleton still works. Change the prompt, not the clock. A case, a campaign brief, a ratio analysis, a grievance scenario, or a current-affairs question can all fill the twenty-five minute block.

Record only if both people agree. Many peers prefer notes. If you do record, say where the file lives and when you will delete it. MatchMyInterview is for practice, not for publishing someone else’s voice without consent.

Bring a closing question you actually care about: “What would you ask me in a real loop?” or “Which part of my story sounded rehearsed?” Those answers are often more useful than the score.

Finally, protect the relationship. Thank the person. Offer a second session only if you both want one. Ghosting after a session wastes the credit and the trust the platform needs to work.