Video Interviews From Here: Power, Bandwidth, and the Backup Nobody Sees
Nobody is rejected for a power cut. They are rejected for how the next ninety seconds are handled — and that part is entirely preparable, days before the call.
The fear is common enough to keep people from applying: the light goes, or the network drops, in the middle of the interview that mattered.
It does happen. What decides the outcome is not whether it happens but what the interviewer watches you do in the ninety seconds afterwards — and that is prepared days in advance, not improvised.
Two connections, always
Your main line, and your phone's mobile data as a hotspot, tested before the call rather than during it.
Test it properly: switch to the hotspot, run a video call on it, and confirm it actually carries video rather than merely showing bars. Two different networks if you can — the outage that takes down one rarely takes down both.
Then leave the phone charged and beside the laptop, not in another room.
Power
Laptop at 100% before the call, plugged in, on an inverter or power bank if you have one. Know your machine's real battery life under video, which is usually far shorter than the number the operating system claims.
Room lit by something that does not depend on mains power, even if that is a window. A candidate in the dark reads badly regardless of the reason.
The message you write before the call
This is the piece almost nobody prepares, and it is the one that saves the interview.
Before the call starts, have the interviewer's email — or the meeting chat — open in a tab, and have a sentence already drafted:
"Lost power/connection — switching to my backup now, back in two minutes. Apologies."
Then, if it happens, you send it within seconds rather than reappearing after four silent minutes of them wondering whether you left.
The silence is what damages you. A candidate who vanishes looks disorganised. A candidate whose message arrives before the interviewer has finished being confused looks like someone who plans for failure — which, for a remote role, is a genuine and relevant credential.
Say it once, at the start
Some candidates mention their setup pre-emptively. Done briefly, it works well.
"Quick note before we start — I've got a backup connection running in case anything drops. If I disappear I'll be back within two minutes."
One sentence, said calmly, never returned to. It answers the question the interviewer was too polite to ask, and it answers it as competence rather than apology.
What not to do
Do not over-explain the national grid. Do not apologise three times. Do not narrate the outage while it is happening.
Handle it, mention it once, carry on with the answer you were giving. The recovery is the whole message.
The wider point
Every remote employer knows infrastructure varies. What they are trying to work out is whether a problem at your end becomes a problem at theirs.
A candidate with two connections, a charged phone and a pre-written message has already answered that. And they answered it under pressure, live, which is worth more than any sentence on a CV.