How a pair mock interview works: five steps and finding a teammate

Lead: what a pair mock actually is

A pair mock is not a webinar and it is not LeetCode with an audience. Two people at a similar grade take turns: one interviews, one answers, then you flip. IT Career Gym finds the other person. You still have to write first, pick a slot, and show up with questions you can actually score.

If you wanted a teammate for a single problem — a bug, a design sketch, a pet-project review — that is the same match with a shorter script. Sixty minutes, one topic, no role swap. Say so in the first message so nobody preps a two-hour loop.

Open Find a partner while you read. The steps below are what happens after the bell says you have a match — not a second product.

The five steps

This is the same loop the bot describes after a match. On the site it lives under Find a partner. Nothing here is automatic except the pairing.

1. 1

   Get the contact

   Write first. Name the track and the length. Say you found them on IT Career Gym.

2. 2

   Pick a date you can both prep for

   Not tonight if neither of you has questions. Two to four days is the usual window.

3. 3

   Prep as the interviewer

   You cannot score an answer you have not solved. Build a short set, then sit with it.

4. 4

   Two halves, feedback after each

   30 or 60 minutes a side. Then you swap. That is the mock, not a 10-minute chat.

5. 5

   Keep the pair if it worked

   Nobody owes you a second call. If both of you want another round, book it before you hang up.

1. Get the contact

Matching looks for a similar grade and request — Backend with Backend, a band you chose, IT or languages. On the website the result lands in the header bell and in My subscriptions. The optional Telegram bot is @IT_Interview_Partner_Bot; it is not required to run the mock.

The platform does not send your first message. You do. Keep it boring:

Hi — IT Career Gym matched us. I am looking for a 60-minute Backend mock, two halves. Are you free Thursday evening?

Do not paste a résumé, a phone number, or a full CV into a public comment. The match card already has the channel you need. If the grade is only a partial match, say so up front and still run the session if you both agree.

2. Pick date and time

There is no calendar inside the gym. Agree in the chat you already opened. Leave enough gap that both of you can finish step 3. A mock at midnight because “we should start today” usually means empty questions and a polite 20 minutes.

Put the length in the same message as the date: 60 minutes (30/30) or 120 (60/60). Then stop negotiating tools until the slot is real.

3. Prep the questions

Each of you owes the other a set: a few practical tasks, a few theory prompts, or a mix. That is the interviewer’s job. If you only plan to “see how it goes”, you cannot give feedback that is more than “yeah, seemed fine”.

Steal the raw material, do not invent a second LeetCode. Express quizzes are short enough to turn into a 30-minute half. Longer holes belong in a deep quiz. For system design, start from a write-up like Amazon system design or Stripe, then ask it out loud — not as a recap of the article.

Work the tasks yourself first. If you cannot tell a weak answer from a strong one, you are not ready to sit in the interviewer chair.

Stuck on a prompt you want to ask? Steal the stem from an express quiz or a deep quiz, then still run it on a human. The model will not sit in the other chair on the day.

4. Run the mock

At the agreed time, join any call you both already have. The gym does not host video. Pick one board and one room and stay there.

Those three are options, not a stack you must install. If you already live in another room, use that.

The shape of the hour (or two):

• Half A. Person A interviews for 30 or 60 minutes, then gives feedback — what landed, what was hand-wavy, what to retry.
• Half B. Person B does the same. You are not “done” after one side. That is a coffee chat.

Feedback is part of the slot, not a later email you will skip. Two or three concrete notes beat a paragraph of praise. Then, if you want another round, say so before you leave.

A 60-minute teammate session

Same matching. Different contract. You are not swapping interviewer hats. You are sitting on one problem for an hour: a failing test, a design you cannot finish, a pet project that needs a second pair of eyes.

Write that in the first message. Bring the artifact (repo, board, quiz topic). Sixty minutes, then stop. If you both want a proper two-sided mock later, book it as a separate call — do not morph a debug session into an unpaid interview loop.

The contact still comes from Find a partner. Grade and request still matter. The difference is the agenda, not a second matcher.

5. Useful materials

Do not open a random list of 150 problems the night before. Pull a small set from the gym and from this blog:

• The blog — company loops, STAR, last-week playbooks. Use one article as the theme of a half, not as a script to read aloud.
• Express quizzes — enough questions for a short half if you have already solved them.
• The last week before the interview — if the real loop is close and you need a triage, not a new mock format.
• STAR stories — if the other half is behavioral, not a coding task.