Skip to content

Mock interviews

~6 min

In short

A mock interview is a practice round with another person who plays the interviewer. It shows you what you cannot see while solving alone: whether you explain clearly, whether you ask about constraints, and whether you stop talking when you should listen. You can run useful mocks for free, with friends or with a study partner, and you can also use free platforms that match you with strangers.

Caveat first: the free terms of the platforms listed below were not verified for this page. Check each site's current pricing and matching rules before you rely on it.

Option 1: Study partners and friends

This is the most useful free option, and it costs nothing but time.

  1. Pair up. Find one or two people who are also preparing. Classmates, a group from a coding community, or a friend who is already working all work.
  2. Agree on a format. Decide the length (for example one coding problem in 30 to 40 minutes, then 10 minutes of feedback), and who plays the interviewer each time.
  3. Give the interviewer a script. The interviewer should have a problem, a set of hints they will give only if asked, and a list of things to watch for: clarifying questions, the approach, testing, and complexity.
  4. Record it if both people agree. Watching back is uncomfortable and very useful.
  5. Give feedback in three parts. What was clear, what was unclear, and one thing to practise next time.
  6. Swap roles. You learn as much from interviewing as from being interviewed.

Keep a mock log: date, partner, problem, what went well, what to fix. The DSA section has a mock-interview log format you can copy (see DSA trackers).

Option 2: Free platforms

These sites are live and were checked on 18 Oct 2026. Their free terms were not verified.

  • Pramp (https://www.pramp.com/). Matches peers for practice interviews. Check whether the service is free today and how matching works.
  • interviewing.io (https://interviewing.io/, mock page at https://www.interviewing.io/mocks). Offers mock interviews with engineers. Some of its features may be paid, so read the current terms before booking.

If a platform asks for payment details to start a free mock, stop and check the terms first.

How to run a round that teaches you something

  • Start with the problem statement. Restate it in your own words, and ask at least two clarifying questions before you touch the keyboard.
  • Talk through your approach before you code. Say the brute force first, then improve it.
  • Name the complexity of your solution and where it could be wrong.
  • Test with a small example by hand, then with an edge case.
  • At the end, ask the interviewer one question about their work or the role. It is part of the round.

What a mock cannot tell you

A mock with a friend is not a real interview. The friend may be kinder than a stranger, and the problem may be easier than the real one. Mocks show how you think and communicate. They do not show whether you are ready for a specific company's loop, which the company itself does not publish in detail.

A simple weekly rhythm

  • One mock now and then in the stretch before you apply, as often as your schedule allows.
  • After each mock, write a single fix for the next session.
  • Every fourth week, do two mocks with partners you have not used before, to test your explanations with new listeners.

Try this

What to do this week: Message one friend or study partner and agree on a 45-minute mock for next week. Write the format in the message: one problem, 30 minutes of coding, 10 minutes of feedback. Prepare the interviewer's script before you send it.

Sources

  • Pramp, peer mock interviews: https://www.pramp.com/ (live on 18 Oct 2026; free terms not verified)
  • interviewing.io, mock interviews: https://interviewing.io/ and https://www.interviewing.io/mocks (live on 18 Oct 2026; free terms not verified)
  • Tech Interview Handbook, study plan for structuring practice: https://www.techinterviewhandbook.org/coding-interview-study-plan/ (checked 18 Oct 2026)