Assume the clock kept running. On HackerRank, CodeSignal and Codility the countdown is drawn in your browser, but the deadline it counts towards is a timestamp fixed on the server when you started, so a dead router, a frozen tab and a shut laptop lid all spend the same minutes. Your code is usually not what you lose: reconnect, refresh the same tab, and the last autosave is normally sitting there. The minutes are what you recover by hand, with one timestamped email sent today.
The first five minutes, in order
Order matters, because the two instinctive moves, closing the browser and reopening the link elsewhere, cost the most.
Photograph the screen before you touch it
Phone camera, one shot, with the error text and the timer reading in the same frame. A refresh destroys both, and that photo turns a claim into evidence with a clock in it.
Fix the network, not the page
A reconnecting banner means the page is alive and waiting, and many editors re-sync on their own once the link returns. Toggle wifi, or switch to the hotspot you paired yesterday. Do not close the tab.
Refresh that same tab
If the banner has not cleared in 30 seconds, press F5 in the tab already open. That re-fetches your saved code and the true remaining time from the server, which is where the state you care about lives.
Reopen the original link, same browser, same profile
Only if the tab or browser itself is gone, and from the invite email rather than a bookmark. A private window or a second browser carries none of your session cookies, so it can land you on a login wall rather than your attempt.
Audit before you type a character
Thirty seconds, three checks. Does the timer match what you expected minus the outage. Is your code at the newest version you remember writing. Do the finished problems still show as submitted.
Send the email today, not tonight
If you are back in with time on the clock this waits until you finish, but it goes today. An email at 14:22 saying you dropped at 14:07 corroborates itself. Tomorrow it is a story.
Restart on the highest-value problem, not the one you were on
Re-price the work against the time you actually have. A half-finished hard problem you were losing anyway is worth less than the easy one you never opened, and a run is also a forced save.
What comes back and what does not
| Item | After you reopen | Why |
|---|---|---|
| Problems already submitted | Intact | A submit writes to the server, the most durable event in the test |
| Editor code since the last save | Back to the last autosave | Saves fire on an interval and on every run, so you lose the gap, not the file |
| A run whose result never returned | Gone | The job may have executed, but the result had nowhere to arrive |
| The countdown | Still running | Fixed server-side at the start, and a refresh only re-reads it |
| Unsaved multiple-choice selections | Often lost | Many question screens save on next or submit, not on selection |
| A timed section that expired offline | Stays closed | Section timers are server-side too and are rarely reopened |
No platform publishes its autosave interval, so treat it as tens of seconds and treat a run as your save button. Check the invite for whether the test is single attempt: if it is, fix the network and refresh the live tab rather than closing anything.
Why the clock does not pause
This is deliberate. If the timer lived in the browser, anyone could stop it by closing the tab, so the server stores a start and an end, the page renders the difference, and offline time is spent time. Some employers enable a pause or a resume window, but you cannot tell from inside the test.
A drop also leaves marks in the proctoring block of your report: a visibility or focus gap, a full-screen exit and a re-prompt for the camera, and a different IP address for the second half if you failed over to a hotspot. That is not an accusation. It is an unexplained gap, and your email turns it into an explained one.
The email, with the actual wording
Subject: Connection loss during [Company] online assessment, [Your name]. Send it from the address the invite went to, so it threads with the original.
Hi [Name], I lost my internet connection during the [role] HackerRank assessment today at 14:07 BST, about 38 minutes into the 90. The page showed a connection lost banner and stopped accepting input, so I switched to a phone hotspot and was back in at 14:11, which cost roughly four minutes of the clock. My saved code was intact and I finished in the time that was left, so I am flagging this only for context, in case the proctoring log shows a gap or a change of IP address around that point. Happy to walk through any of my solutions live. Thanks, [Name]
Four sentences, and every number in it is checkable. If you never got back in, replace the last two with a direct ask: what you completed, what you never opened, and a request for a reset. Skip the long apology and the photo of your router, attach the error screen only, and if you did finish, do not ask to redo it.
When the link will not let you back in
A message about the test already being attempted, or the link having expired, is not something you or platform support can fix on a candidate's word. The employer owns the invite, so the reset request goes to the recruiter with the test name, the time and time zone of the drop, and one line on what you completed. Plenty of companies reset a first outage that arrives with a timestamp attached, though none are obliged to.
The checklist that prevents most of this
- Ethernet if you have it, and pair the hotspot the day before. Connect to it once and load a page, so failing over mid-test is two taps, not five minutes of pairing while a timer runs.
- Quit sync clients, do not minimise them. OneDrive, Drive, Dropbox, iCloud and backup software saturate a home upstream link, and an editor holding a websocket open feels it first. This causes more connection lost banners than real outages.
- Charger in, sleep and screen lock off. A lock screen at minute 50 can kill the socket and log a focus-loss event in the same instant.
- Disable page-injecting extensions on that domain. Ad blockers, VPN extensions and Grammarly rewrite pages, and a code editor is exactly the kind of page they break.
- Open the link five minutes early for the system check and camera prompt. The invite says whether the clock starts there or at the first problem, and that varies.
- Park an escape kit in a second window: the recruiter's address, the test name, the invite link. The panic email should take 60 seconds to write.
Where OfferPilot AI is no help at all
Being blunt on a page published by a company that sells an interview assistant: nothing we make recovers a crashed assessment. It cannot restore an editor buffer or pause a server-side timer. The property people know us for, an overlay excluded from screen capture at the operating-system level so it stays out of Zoom, Teams, Meet and recordings, is irrelevant to a network drop, and it does nothing against webcam monitoring, a lockdown browser, eye tracking, a second-device camera or a human proctor. On a proctored assessment whose rules say no outside assistance, it is the wrong tool.
Transcription in the Interview Copilot runs on-device, but the drafted answers come from Grok, DeepSeek and Gemini over the internet, so the outage that killed your test would have taken the copilot down with it. Where it earns its place is the untimed side, working through problem archetypes with Code Copilot until the format holds no surprises.
OfferPilot AI is a Windows 10 and 11 desktop app for live rounds and coding practice, not a safety net for a timed test. If your next stage is a conversation, the free tier on the pricing page gives five minutes a day, no card.