Tonight is a setup night, not a study night. Between 6pm and 9pm you test the exact video app the invite names, check that the interviewer's voice actually reaches the headphones you plan to wear, and open the coding pad link to confirm it loads and lets you type. Then a hard 9pm cutoff, one page of your own notes re-read once, and sleep. The single worst use of the 10pm hour is opening a hard problem you have never seen.
The evening, 6pm to lights out
Times assume a morning round. Shift them for an afternoon slot, but keep the cutoff ninety minutes clear of sleep.
| Time | What you actually do | Why this and not revision |
|---|---|---|
| 6:00 to 6:30 | Eat, away from the desk. Not at the keyboard with a problem open. | Eating over a pad is how 6pm quietly becomes midnight. |
| 6:30 to 7:15 | The machine check below, in one uninterrupted pass. | Every failure here is silent, cheap tonight, expensive at 09:59 tomorrow. |
| 7:15 to 7:45 | A two-minute live call with a friend or a second device, same app, same headphones. | Settings panels lie. Only a real call tests the whole path. |
| 7:45 to 8:45 | Re-solve one problem you know cold, out loud, in a plain editor. The only code tonight. | To prove retrieval works, not to find a gap you cannot close. |
| 8:45 to 9:00 | Re-read your one page. Once. Do not rewrite or extend it. | Familiar material ends the day on a success, not a struggle. |
| 9:00 | Hard cutoff. Laptop shut, pad closed, tabs gone. | A cutoff you can negotiate with is not a cutoff. Alarm it. |
| 9:00 to 10:15 | Anything unrelated. Lay out clothes, fill a water glass, set two alarms. | The only tomorrow-facing tasks allowed in this block. |
| 10:15 onward | Phone charging in another room. Lights out. | Eight hours protects the working memory the round tests. |
The machine check, in the order things break
Forty-five minutes, in this order. Each step assumes the one above it passed.
Read the invite and name the app
Zoom, Teams, Meet, Webex and a plain dial-in all behave differently, and the invite often carries two links, the call and a separate coding pad. Note which needs a desktop client. If the invite says Teams and you spent the week testing Zoom, you have tested nothing.
Test the audio inside that app, not in system settings
Zoom has a speaker and microphone test under Settings, Audio, playing a tone through the device Zoom itself picked. Teams has a test call under Settings, Devices that records you and plays it back, the strongest single test on offer. Meet has a speaker test in its audio settings. Your Windows sound panel passing says nothing about what the app chose.
Connect the headphones first, then re-check the output device
Pair or plug in before opening the call app, then check the output dropdown inside it, because apps remember devices you no longer wear. The Windows failure to know: picking a Bluetooth headset as your microphone flips it into hands-free mode, so quality collapses and the headset appears twice, once as "Headset" and once as "Headphones". Wired earbuds plus a laptop microphone removes the category.
Grant browser permissions if the call runs in a tab
Meet and browser pads need per-site microphone and camera permission. If you once clicked block there, no prompt appears tomorrow, it just fails. Fix it from the icon left of the address bar.
Open the pad link and type in it
Click the real link. Most pads open early into a waiting state, a few refuse until the scheduled time, and both answers are useful now. What you must not discover at the top of the hour is that the link wants an account you do not have. If it opens, pick your language, type a loop, press run. Note whether a run button exists at all, and what autocomplete does, because a pad that closes brackets for you changes how you type.
The boring physical layer
Charger in. Notifications off, phone silent rather than vibrating. Settle the second monitor question tonight, because 09:58 mid screen-share is a bad moment to learn which display the pad opens on. If your connection is fragile, check your phone hotspots and how to switch to it.
Tonight is also when you test the audio path any assistive tool depends on. Interview Copilot captures system playback rather than your microphone, which is why interviewer audio reaches it through headphones. Play a video through that headset and watch the transcript arrive.
Why the failed hard problem at 10pm is the worst hour of your week
It feels like the responsible choice, which is why it keeps happening. Three things go wrong at once.
The bet is bad in both directions. Solving tonight's problem buys almost nothing, because the chance it is tomorrow's problem is close to zero. Failing it costs an hour of sleep, then something worse than the hour.
A late failure is the most available memory you own tomorrow. Twenty minutes stuck at 10:40pm, alone and tired, is vivid and emotionally loaded. It is what surfaces the second tomorrow's prompt does not resolve instantly, so you spend the first four minutes of a forty-five minute round managing a feeling you made last night.
Nothing learned that late is retrievable anyway. A pattern first met at 10pm lands in recognition memory, not retrieval memory. Tomorrow you get the flicker of "I saw this last night", then burn twelve minutes rebuilding a structure you never owned while the cursor sits still on a shared screen.
If you cannot leave the code alone, re-solve something you already know, out loud, and stop the moment it works. You are testing that retrieval fires, not hunting for something that breaks it.
One narrow exception: if tomorrow's pad forces a language you rarely write, spend twenty minutes before the cutoff on its counting map, its custom-comparator sort, and its string split. Syntax you cannot recall is a tonight-sized problem. A new algorithm is not.
The one page you re-read, and what belongs on it
One side of one sheet, in your handwriting, written days ago and only re-read tonight. The compression did the work, which is why someone else's page is worth nothing to you. About seven lines:
- Your opening sentence: "Let me restate that and walk one small example before I write anything."
- Your three most-used patterns, each with its trigger words and your first move.
- Your language's counting-map idiom, and the sort signature you always look up.
- The two edge cases you personally forget. Usually empty input and a single element.
- The stuck line: "Let me state the brute force, get it correct, then optimise."
- The closing line: "Time is O(...), space is O(...), and the case I would test next is ..."
- Two lines on the company: what they actually build, and one question you will ask.
If those last two lines are blank, tonight is too late to research a company properly, though not too late to re-read a bank you built earlier in the week. The company Q&A generator builds one for a named firm and role, a Tuesday task rather than a 9pm one.
Where this evening cannot help, and what not to install tonight
A good evening cannot repair a month of not practising, fix a weak connection, or make an unfamiliar pattern retrievable. If you are three patterns short, its only job is to stop something mechanical costing you the problems you can already do.
It is also the wrong night to install anything new, ours included. A first run of Code Copilot means learning a capture shortcut, an overlay toggle and an audio route you have never tested, at the hour your attention is worth most. Software you have not rehearsed in a mock is a liability, so learn it this week or leave it closed. Two limits worth stating plainly. OfferPilot AI is Windows 10 and 11 only, no macOS, Linux or mobile, so on a Mac the question is moot. And the overlay's exclusion from screen capture, enforced by the operating system so it stays out of Zoom, Teams, Meet, OBS and screenshots, is a fact about screen sharing and nothing else: it does not affect a webcam, a lockdown browser, a proctor watching in person, or a phone camera pointed at your desk. Where an assessment forbids outside help, the honest window is the preparation before the round, not the round.
What reliably pays tonight is dull: right app, audio in your ears, pad open and taking typing, page read once, asleep by eleven.