Interview-day protocol (remote): test your setup the evening before, warm up on what you know, and start each round fresh
Test your setup the evening before, warm up on what you know, and start each round fresh.
Predict first
Before you read: predict
A video-streaming engineer is in her Meta onsite. In the first coding round she missed an edge case in the second question and ran out of time. She has 15 minutes before her system design round.
Going by interviewing.io's Meta guide (read 2026-10-16), how does she use them?
The 30-second version
Logistics fail in boring ways, and each failure costs minutes and composure. The evening before, try all seven checks, the round's own tool included. On the day, a short warm-up card and nothing new. Between rounds, reset: each interviewer writes up their own round.
Test your setup the evening before, warm up on what you know, and start each round fresh.
How it works
Step 1 of 13
Analogy: A decathlete's two days
The evening before, a decathlete laces her spikes and jogs a lap in them, tries the spare pair, and confirms her call-room times on paper with the team manager. On the morning, a short warm-up of drills she knows, nothing new. Each event is scored on its own points table. After a bad high jump she sits for five minutes, drinks, and reads her notes for the 400 m; the high jump is over. (The meet and its schedule are the scene's own.)
| At the meet | On interview day |
|---|---|
| Spikes run in, the spare pair tried | Checks tried, a backup connection used |
| Call-room times confirmed on paper | The time confirmed in writing |
| A warm-up of drills she knows | The warm-up card, nothing new |
| A points table per event | Each interviewer's own write-up |
| Five minutes and the next event's notes | The reset between rounds |
Breaks down when: a decathlon adds its points by a table, while a loop's rounds are weighed by people, and one account has a single round decide alone. Wrong inference: “each round counts equally”: ask what each round decides.
In real terms: test it all the evening before, warm up on what you know, and walk into each round as if it were the first.
Examples, run for real
EXH-4560 is a synthetic candidate for ExamHall's senior backend round (an invented process), on Thursday 19 November 2026 at 10:00 Berlin. ExamHall runs a pre-exam system check on its candidates; she runs this lesson's seven on herself.
EXH-4560 first take · ExamHall senior backend round, Thursday 19 November 2026 10:00 Berlin (invented) · check model
checks run Thursday 09:35, 25 min before the round
done 3 of 7: camera, microphone, bandwidth
open 4: entire screen with notifications off, interview tool, backup connection, time in writing
MR !4860 second take, same round
checks run Wednesday 18:00, 16 h before the round
done 7 of 7
reply "Confirmed: Thursday 19 November 2026, 10:00 Berlin, 09:00 London." · Thursday matches the date · both clocks 09:00 UTC (tz 2026c)The first take is ExamHall's own system check run on the morning: camera, microphone and a speed test pass, and four checks are still open with 25 minutes left.
The second take runs the evening before and tries every check. Its reply names one instant on both clocks.
The model is this lesson's reading of a log: it counts what was tried; it cannot say how a round would go.
Try it
Answer first, then check. Nothing is saved.
Question 1 of 7
The evening before a remote design round with a video-streaming company, an engineer logs her checks: “Call with a friend: he saw and heard me clearly. Speed test: 120 Mbps down. Shared my browser window on that call to show him a diagram. Drew a practice design on excalidraw.com, the tool the invite names. Joined the same call again over my phone's hotspot with the Wi-Fi off. The recruiter said on the phone it's 15:00 my time.” She applies this curriculum's plan, not a cited finding: seven checks (camera, microphone, bandwidth, the entire screen shared with notifications off, the tool the invite names, a backup connection, the time confirmed in writing with the weekday, the date and both clocks), each counted once the log shows it tried the way the round will use it.
On this lesson's check model, which checks are still open?
Question 2 of 7
A video-streaming engineer's Meta phone screen opens with her interviewer asking about her recent work. She gives the wrong year for her last launch and hears herself do it. The coding questions come next.
Going by interviewing.io's Meta guide (read 2026-10-16), how does she take the slip into them?
Question 3 of 7
A video-streaming engineer's Meta onsite is in three days and includes the AI-assisted coding round. None of her recruiter's emails mentions a practice environment; she has practised in CoderPad's public sandbox.
Going by interviewing.io's Meta guide (read 2026-10-16), what does she do next?
Question 4 of 7
The morning of a 14:00 remote round at a video-streaming company, an engineer reads her review log, giving each item, its minutes and her results in her last three reviews, oldest first: “rate limiter, 3 min: right, right, right; cache stampede, 2 min: wrong, right, right; idempotency keys, 3 min: right, right, right; consistent hashing, 3 min: right, wrong, wrong; outbox pattern, 2 min: right, right, right.” She applies this curriculum's plan, not a cited finding: the warm-up card holds only items she got right in each of her last three reviews, ten minutes of them at most, then her outlines.
On this lesson's warm-up model, which items go on her card?
Question 5 of 7
The invite for a video-streaming company's remote round reads: “Thursday 19 November 2026, 10:00 New York time.” You live in Lisbon. Write the one-line reply that confirms it in writing, starting with Confirmed: and giving the weekday, the date, and the time on the interviewer's clock and on yours, each with its city.
Answer in one or two lines.
Question 6 of 7
The evening before her remote round, a video-streaming engineer logs: “Call with my brother: camera and microphone fine. Speed test: 60 Mbps down. Shared my entire screen on that call with Do Not Disturb on. Solved one problem in CoderPad's sandbox, the pad the invite names, with Run switched off. Backup: my phone has a hotspot. I replied to the invite ‘Confirmed: Wednesday 18 November 2026, 10:00 London, 11:00 for me in Berlin.’” She applies this curriculum's plan, not a cited finding: seven checks (camera, microphone, bandwidth, the entire screen shared with notifications off, the tool the invite names, a backup connection, the time confirmed in writing with the weekday, the date and both clocks), each counted once the log shows it tried the way the round will use it.
On this lesson's check model, which checks are still open?
Question 7 of 7
A video-streaming engineer's remote round is at 14:00 on Thursday. Her checks would find three problems, each with what its fix takes: her browser needs an update, 15 minutes; her phone plan has no hotspot until her carrier adds it, up to 12 hours; the invite says only “2 pm”, so she must ask the recruiter, who answers email within 4 hours.
On this lesson's lead-time model, which of the three can she still fix if she runs her checks at 13:30 on Thursday?
Go deeper
Pro tip
Keep the interviewer's or recruiter's email open on your phone during the round. If the call drops, one line, “Lost the connection, rejoining in two minutes”, tells them you are coming back (the plan).
Where the steps come from: steps 7, 8, 11 and 12 rest on one platform's guide to Meta's process (interviewing.io's, read 2026-10-16); steps 1–6, 9, 10 and 13 are this curriculum's plan, not findings.
Related lessons
- Read first: The final two weeks: review more of what you know, add nothing new at the end, and sleep
- Related: Remote-hire logistics: a start date, how you can be hired, the right to work, and your overlap in CET hours
- Related: Loop format recon: one sheet per company, settled by the recruiter
- Related: AI-free fluency (Bare mode)
- Related: Running a noisy, parallel pipeline: one round is one sample, so run several and log each one
- Related: Buying time and repairing misunderstandings: pause out loud, ask for what you lost, correct at once
Checked against the tools and docs as of 2026-10-16.