Guides · Interview formats and rounds

Surviving a four-round virtual onsite: an hour-by-hour plan

2026 · ~7 min read · OfferPilot AI

If the loop is today, you are not learning anything new. You are running a day. That means a fixed timetable, a ten minute protocol you repeat in every gap, your self-view hidden before round one, and a way to bury a round that went badly so it does not eat the round after it. By round three it is your voice and your attention that fail first, not your knowledge, and almost none of the standard advice is aimed at that.

The timetable, assuming a 10am start

Write your real times into this shape the night before, or over breakfast if you are reading this on the morning. The point is that nothing on the day is a decision. Every choice you make between 8am and 3pm costs attention you need for the rounds.

ClockBlockWhat you actually do
08:00Up and fedEat something you have eaten before an interview at least once. No new material, no LeetCode, no reading a system design article "just once more".
08:45Tech check, 15 minStart a meeting with only yourself in it. Test mic, camera, and share your screen once so the permission prompt is already answered. Plug in the charger. Phone on silent, face down, in another room. Two filled water bottles.
09:15Warm up out loud, 20 minSay "tell me about yourself" twice, standing. Then one story from your bank at full speed. Then walk through a problem you have already solved, narrating as if someone is listening. Speaking is the muscle, not solving.
09:40The one-pager, 10 minRead the tag list of your stories, three facts about the company, and the three questions you will ask each interviewer. Nothing longer than one page survives in your head to round four.
09:52ResetStand, stretch, bathroom, close the door, sign out of Slack and email. Hide your self-view now, before anyone is watching you do it.
09:58JoinTwo minutes early, camera on, mouth already warm. Never join at exactly 10:00.
10:00Round 1, codingThe round you are freshest for. If you get any say in the order, put coding first.
10:50Gap, 10 minThe protocol below. Not email.
11:00Round 2, system designThe longest round and the one where your voice does most of the work.
12:00Break, 30 minEat in the first fifteen minutes. Then get outside, or at minimum away from the desk, for ten. No screen.
12:30Round 3, behavioralThe round most people underrate, and where fatigue shows up as rambling. Watch your answer lengths.
13:20Gap, 10 minProtocol again. Same order, every time.
13:30Round 4, hiring managerAsk your three questions. This is the round where you are being sold to as well.
14:20StopWrite the debrief you have been postponing all day. Send thank-you notes tomorrow morning, not tonight.

The ten minutes between rounds, minute by minute

This is the part of the day that decides how round four goes, and it is the part nobody plans. Run it in this order every single time so that by the third repetition it needs no thought at all.

0:00 to 1:00 Stand up and leave the room

Not stand next to the chair. Walk to a different room and come back. You have held one posture and one facial expression for an hour, and the fastest way to reset both is to change what your eyes are focused on.

1:00 to 3:00 Water, then bathroom, in that order

Half a bottle, not a full one. The order matters because you want the fluid in you at the start of a round and not in the middle of it. Both bottles get refilled at lunch, never during a ten minute gap.

3:00 to 5:00 No phone

This is the rule that does the most work and gets broken the most. A text from a friend, a recruiter email, a notification about something unrelated: each one loads a second context into a head that needs to hold exactly one. The phone stays in the other room until 3pm.

5:00 to 7:00 One glance at the story bank

Read the tag list only. Eight lines like "broke production", "pushed back on a PM", "missed an estimate". Do not reread the stories themselves. You are refreshing the index, not the content, and rereading a full story at minute five is how you end up reciting it word for word.

7:00 to 9:00 Reset the desk

Close every tab from the previous round, the editor included. Open the next call link. Check your framing, and check that the light is still in front of you rather than behind. A window that was fine at 10am makes you a silhouette at 1pm.

9:00 to 10:00 Sit and speak

Two slow breaths, then say your opening sentence out loud. Your voice has been silent for ten minutes, and the first thirty seconds of a round is where a flat, croaky start does damage that is hard to undo.

Hide your self-view before round one

A five hour loop is five hours of watching your own face react in a small rectangle. That is a continuous self-evaluation loop running underneath the conversation, and it is one of the better documented contributors to video call fatigue. It also competes directly with listening, which is the thing you can least afford to lose by round three.

In Zoom, right-click your own video tile and choose Hide Self View. You disappear from your own screen and the interviewer still sees you exactly as before. Teams and Meet both have equivalent options, though menu locations move between versions and I would not trust a specific click path here, so find yours during the 08:45 tech check rather than hunting for it while someone waits. If your platform genuinely has no toggle, a sticky note over that corner of the monitor does the same job for free.

Two other display choices worth making at the same moment. Switch to speaker view rather than gallery, so you are looking at one face instead of scanning five. And drag the meeting window to the top of the monitor, directly under the webcam, so that looking at the interviewer and looking at the camera are almost the same eye line.

What the gap length changes

Ask the recruiter for the exact schedule the day before, gaps included. A five minute gap and a twenty five minute gap are different problems, and treating them the same is how people arrive at round three already spent.

GapDo thisDo not
0 to 5 min, back to backStand, water, one look at the tag list, sit. Skip everything else. If the interviewer has already said goodbye, turn your camera off for the last thirty seconds.Do not try to fit the bathroom in. You will be late and flustered, which costs more than the discomfort does.
10 minThe full protocol above, in order, unchanged.Do not check email. Ten minutes is exactly long enough to feel like there is room for it.
20 to 30 minProtocol, then leave the flat or the building. Ten minutes of daylight and different scenery does more for round three than twenty minutes of revision.Do not reopen the last problem to solve it properly. This is the single most common way a good loop turns into a bad one.
45 to 60 min lunchEat in the first fifteen. Refill both bottles. Then walk. Come back with ten minutes spare and run the normal protocol, so the restart feels identical to every other round.Do not nap, and do not eat something heavy or unfamiliar.
Unplanned 25 min, an interviewer is lateMessage the recruiter once, then treat it as a twenty minute gap. Stay dressed, stay in the room, keep the link open.Do not start anything you cannot abandon in thirty seconds.

If your story tags are not written yet and the loop is in a few hours, one page is enough. The company Q&A generator builds a bank for the company and role in a few minutes, and the company question sets will tell you the shape of what this particular loop tends to ask.

Resetting after a round that went badly

One round will go worse than the others. That is the normal shape of a four round day, not a signal about you.

Give yourself sixty seconds to be annoyed about it, on an actual timer. Then write one line in a scratch file: "R2: fumbled the sharding follow-up, never asked about write volume." Close the file. That file is the debrief and it opens at 3pm, not before. The urge you will feel is to reopen the problem and solve it properly, because solving it will feel like repair. It is not repair. It is twenty minutes of your remaining attention spent on a round that is already scored, taken straight out of the round that is not.

Two things worth knowing. Interviewers on a loop generally write their feedback before the group debrief and score their own round independently, so a weak round is one input among four rather than a verdict. That is the usual practice at larger companies, and I would not assume it at a ten person startup where the panel may simply compare notes over lunch. And the interviewer in round three has no idea what happened in round two unless you tell them, which is the whole argument for never opening with an apology or a rueful joke about how the morning went.

Then do the thing that actually resets you: say the first sentence of the next round out loud before you join. Not a pep talk, just a sentence in your normal working voice. A blank slate is a physical state more than a mental one.

Where this plan, and a copilot, stop helping

This plan assumes you own the day. If you are interviewing between meetings at a current job, from a phone booth, or from an office where you cannot close a door or control your own display settings, most of it collapses, and the honest fix is to move the loop rather than run it badly. It also assumes four rounds in one day. A loop split across a week is a different problem, closer to preparation than to stamina, and the timetable above solves nothing there.

On tooling, plainly. OfferPilot AI runs on Windows 10 and 11 only, with no macOS, Linux, mobile or browser version, so on a work-issued MacBook it is simply not an option. Its overlay is excluded from screen capture at the operating-system level, which means it does not appear in Zoom, Teams, Meet or a screenshot, but that does nothing whatsoever about a webcam watching your face, a lockdown browser, an in-person proctor, eye tracking, or a second-device camera pointed at your desk. Metering counts listening time only, so a five hour loop does not burn five hours of quota, and the free tier of five minutes a day is not a loop by any reading of it. Most relevant to this page: a copilot helps inside a technical round where a definition has gone missing under pressure. It does nothing for fatigue, it actively hurts in a behavioral round where reading drafted text sounds exactly like reading drafted text, and it has no role at all in the ten minutes between rounds, which is where the day is won or lost.

Print the timetable. Put the tag list on one page beside the keyboard. Run the same ten minutes after every round, whether it went well or badly, and you will get to round four still able to hear the question.

Related guides

Build the one page before the loop starts.

Generate a question bank for this company and role, then cut it down to the tag list you will actually glance at between rounds.