Lost Connection During a Coding Interview? Don’t Paste Back Offline Code

If you lost connection during a coding interview, switch to another channel fast. Don’t wait for the Wi-Fi to come back. Google’s and Amazon’s candidate guides point the same way. Try to reconnect, then move to a phone line, then contact the recruiter. While the video is down, keep talking through your approach by phone. Don’t write code in a local editor to paste in later. CoderPad, a common shared pad, marks every paste from outside the pad. A reviewer then has to guess what that paste was. When you rejoin, say how many minutes you lost. Then ask the interviewer how they want to use the time left. That puts the outage in their notes as a fact. If the outage ate most of the problem, ask for a reschedule. Google’s own guide says a round with persistent technical issues may need one. This post follows one Android engineer through a seven-minute outage in a Kotlin round.

Lost connection during a coding interview? Google and Amazon both say switch channels

Google’s candidate guide for virtual interviews is a PDF last modified in May 2025. Its troubleshooting steps start with telling the interviewer. Next, it suggests turning off your camera to save bandwidth. As a last resort, it says to ask for the round to move to a phone call. It also lists a phone as required equipment for audio or video problems. And it adds a note. If technical issues persist, the interview may need to be rescheduled.

Amazon’s remote interview page gives a similar order. First, close the meeting and re-enter it. If that fails, dial the toll-free number in your interview invitation. If that fails too, email your recruiting contact right away. The page has no visible publish date.

Neither guide tells you to sit and wait for the router. Both try to keep the call going. An interviewer has nothing to write down during seven silent minutes. They can write down an approach you explain over a phone line.

The running example: seven minutes gone in a 45-minute Kotlin round

Take an Android engineer we’ll call Jordan. Jordan has a virtual onsite for a mid-level role. Round two is a 45-minute coding round in CoderPad, in Kotlin. The problem asks Jordan to merge overlapping time ranges from a list of calendar events.

By minute 14, Jordan has stated the approach. Sort the ranges by start time, then walk the list once and extend or close the current range. Jordan has written the sort and half the loop. Then the home Wi-Fi drops. The video freezes. The pad stops syncing.

Jordan is back seven minutes later, on a phone hotspot. That leaves 24 minutes. The rest of this post covers what Jordan does in those seven minutes and after them.

While you’re offline, talk through the approach by phone

Jordan’s first move takes under a minute. The interview invite has a dial-in number. Jordan saved it before the round. Jordan calls it from the phone. The interviewer is still in the meeting, so the audio connects.

Jordan says what happened in one sentence. Then Jordan keeps solving out loud. The sort is done. The loop compares each range’s start with the current range’s end. If it overlaps, extend the end with the larger of the two. If it doesn’t, close the current range and start a new one. Jordan names the edge case too. Ranges that only touch at an endpoint need a decision, so Jordan asks whether they count as overlapping.

None of that needs a screen. The interviewer can still write it down. Their notes from the minutes without video show the approach, the loop logic and an edge-case question.

Code you write offline and paste back gets marked as a paste

Jordan also has Android Studio open. Finishing the loop there and pasting it in later looks efficient.

The pad records how code arrived, though. CoderPad’s playback mode documentation says the platform tracks every keystroke of every participant. Playback marks each paste from outside the pad with a yellow dot. It also marks moments when the candidate’s browser wasn’t focused on the editor. The same page says a paste doesn’t necessarily mean cheating. But the reviewer sees a block of finished code appear at once, with no typing behind it. They have to decide what it means.

Google’s guide is stricter about the work itself. It says submitting work you didn’t produce will result in disqualification. Your own offline code is your work. But a pasted block is exactly what CoderPad’s playback markers exist to flag. Our post on HackerRank copy and paste from your own IDE covers the same trap in online assessments.

So Jordan keeps Android Studio closed. When the pad comes back, Jordan types the loop in the pad, while saying each line. The keystrokes then match what Jordan explained by phone.

On rejoin, name the minutes lost and ask how to use the rest

Jordan’s first words after rejoining put the outage on the record as a number. They also hand the next decision to the interviewer. Here’s the script.

I’m back on a hotspot. Thanks for staying on the line. We lost about seven minutes, from around 10:14 to 10:21. My plan is to type the loop we just went through, then test the touching-endpoints case. Does that work for the time we have, or would you rather I skip to something else?

Then Jordan stops talking and waits for the answer. The interviewer might say to keep going. They might also cut the follow-up question to make room. Either way, it’s their call. They also know the clock was cut.

Skip the long apology and the story about your router. One sentence of fact is enough. Every extra minute comes out of the 24 left.

Ask for a reschedule when the outage ate the core of the round

Seven minutes in a 45-minute round is survivable. Jordan finishes the loop, runs two tests and handles the edge case. There’s no time for the follow-up. The core of the problem is done, though. Jordan doesn’t ask for a redo.

Now change the numbers. Say the connection dropped twice and Jordan lost 20 minutes. The loop never ran. In that case the round didn’t measure Jordan’s coding. Google’s guide already allows for a reschedule when technical issues persist. So asking isn’t a strange request.

Ask the interviewer first, at the end of the round. Then send the recruiter a short note the same day. Our post on bombing one round of an onsite explains why that note should carry only facts. Here’s the version for a long outage.

Hi Dana, a quick note on today’s second coding round. My connection dropped twice, from about 10:14 to 10:21 and again from 10:30 to 10:43. I stayed on the dial-in for part of it. We still lost about 20 minutes of a 45-minute round. I never got to run my solution. Would a short redo of that round be possible? I can make any time this week work.

The company decides whether to grant it. The email still gives the recruiter times they can check against the interviewer’s notes. It also offers a fix they can say yes to.

Set up the fallback before the round starts

Jordan’s recovery took under a minute because the number was ready. That’s the part you can prepare. Before a virtual onsite, find the dial-in number in your invite and save it in your phone. Amazon’s page says the invitation includes one. If your invite has no number, ask the recruiter how to reach the interviewer if video fails.

Then test your phone’s hotspot with the meeting tool. Charge the phone. Know which browser tab holds the pad, so you can reopen it fast. Google’s guide also recommends testing your equipment before the interview. It says the recruiting coordinator can set up a test call if you want one.

Why each part of Jordan’s recovery works

The phone call keeps the round alive. The interviewer is scoring reasoning. Reasoning travels fine over audio.

Typing in the pad keeps the record clean. Every line has keystrokes behind it. Each one matches something Jordan already said out loud.

The rejoin script turns the outage into a number. “About seven minutes” goes into the interviewer’s notes as a fact they can check.

Asking how to use the rest makes the interviewer choose the trade-off. They won’t later wonder why the follow-up never happened.

The reschedule request only comes out when the outage stopped the round from measuring anything. Then it carries times and a fix, the two things a recruiter can act on.

Leave a Comment