Video interview setup: a pre-call checklist for technical rounds

The day before

Work through this list in order. Tick each item only after you have actually tested it.

Meeting tool
[ ] Opened the meeting link from the invite; know which app it uses
[ ] Installed or updated the desktop app, or tested the browser version
[ ] Signed in with the name you want displayed (full name, not a nickname)
[ ] Allowed camera, microphone and screen-sharing permissions in the OS

Audio and video
[ ] Wired earphones or headset tested; no echo in a test call
[ ] Camera at eye level; face lit from the front, not a window behind you
[ ] Background plain or tidy; no personal documents visible

Connection
[ ] Speed test from the room you will use
[ ] Phone hotspot set up as backup and tested once
[ ] Laptop charger plugged in; power backup if outages are common in your area

Screen
[ ] Notifications off (Focus or Do Not Disturb mode)
[ ] Email, chat apps and unrelated browser tabs closed
[ ] Font size in the editor large enough to read on a shared screen

Coding environment
[ ] Editor open with a blank file in the language you will use
[ ] Python or your language runs; a hello-world executed today
[ ] If the round uses an online editor, opened the link and typed in it

Test screen sharing on the real tool

Screen sharing fails in ways a test call does not reveal: the OS blocks it, the wrong monitor is shared, or text is too small. Do one full rehearsal with a friend on the same tool: share your editor, type a few lines and ask them to read it back.

Share a single window rather than your whole screen when the tool allows. It avoids exposing notifications or other tabs.

A coding environment that is ready

Have a file already open with a working setup, so you are not installing anything live. For a Python round:

# interview_scratch.py - check the environment works before the call
import sys
import json
from collections import Counter, defaultdict

print(sys.version.split()[0])
print(Counter("interview"))
print(json.dumps({"ready": True}))

Run it the morning of the interview. If a data round may need pandas, confirm it imports too. If you rely on an AI coding assistant in your normal editor, switch it off unless the interviewer has said you may use one, and ask at the start if unsure.

Fifteen minutes before

[ ] Restart the laptop to clear background updates
[ ] Close everything except the meeting tool and editor
[ ] Water within reach; phone on silent but nearby for the fallback
[ ] The job description and your notes printed or on paper, not on screen
[ ] Join two to three minutes early

Keeping notes on paper means you are not glancing at another window, which interviewers can notice.

If something fails during the call

Agree the fallback at the start: "If my connection drops, I will rejoin immediately, and if that fails I will call you on the number in the invite." Then, if it happens:

1. 1Rejoin the same link at once.
2. 2If video fails, offer to continue on audio with screen sharing.
3. 3If the connection is unusable, switch to the phone hotspot.
4. 4If nothing works within five minutes, send a short email to the recruiter:

Subject: Interview at 3 pm - connection lost - [Your Name]

Hi Neha, my internet connection failed during the interview with Mr. Iyer at
3:10 pm and I have not been able to reconnect. I am available to continue now
by phone on 98XXXXXXXX or to reschedule at the team's convenience. Apologies for
the disruption.

Talking while you code

In a remote round, the interviewer cannot see your thinking. Say what you are about to do before typing, mention the edge cases you are considering, and say when you are testing. Silence on a video call feels longer than in person.

After the call

Note the questions you were asked while you still remember them, and send a short thank-you if appropriate; timing and drafts are in follow-up emails after an interview.

Forward-deployed roles involve a lot of screen-shared problem solving with clients, so interview habits carry straight into the job. The FDE for Freshers programme is taught in live online sessions with optional in-person labs at our Noida centre, which gives plenty of practice explaining code on a shared screen.