Setting Up for a Remote or Virtual Interview

The setup is part of the interview

In a video interview, your camera, audio, and surroundings are the channel through which everything you say has to travel. A frozen screen, a muffled microphone, or constant background noise makes you harder to follow and quietly costs you, even when your answers are good. Interviewers rarely write down "bad audio" as a reason to pass, but they do remember that a candidate was tiring to listen to, and that impression colours the rest of the scorecard. The good news is that this part is almost entirely within your control, and an hour of preparation removes most of the risk.

It helps to think about why setup carries weight at all. An interviewer is forming two judgements in parallel: can this person do the job, and what would it be like to work with them. In a remote-first company, your ability to run a clean video call is not a side issue, it is a small live demonstration of how you will show up to every standup, design review, and incident call for the next few years. A candidate who joins on time, with clear sound and a calm frame, has already answered a question the interviewer was going to ask anyway.

This guide covers the practical setup. It will not change how you answer questions, but it will make sure your answers actually reach the person on the other end clearly, and it will stop the avoidable failures that derail otherwise strong candidates.

The bar is not a studio. The bar is that nothing about your setup makes the interviewer work harder to understand you. Clear beats impressive every time.

What good and weak setups actually look like

Before the step by step, it helps to picture the two ends of the range. Most candidates sit somewhere in the middle and can move up with very little effort.

The jump from weak to good enough is the one that matters. You do not need the strong column to do well. You need to clear the weak column so that nothing about the channel works against you.

Sort the technology first

Find out which platform the interview uses, Zoom, Google Meet, Microsoft Teams, or something else, and install it ahead of time rather than during the joining countdown. Some platforms run in the browser and some want a desktop app, and corporate setups often behave differently from the consumer version you may have used socially. Knowing which one you face removes a common last-minute scramble. If the invite is ambiguous, reply to the recruiter and ask. That is a sensible question, not a needy one.

Then do a real test rather than assuming it will work:

• Join a test call or use the platform's built-in device check to confirm your camera and microphone work. Google Meet has a green-room self-check before you join, and Microsoft Teams has a test-call bot that records a short message and plays it straight back, so you hear exactly what the interviewer will.
• Test the exact device you will use on the day, since a laptop and a phone behave differently, and a personal laptop differs from a locked-down work one.
• Check that screen sharing works if the interview is technical, and know exactly where the share button lives in that platform.
• Confirm your internet connection is stable, and if you can, use a wired connection or sit close to the router on the 5GHz band.
• Update the app the day before, not five minutes before. Forced updates are a classic way to be late to your own interview.

If a coding tool or shared editor is involved, open it in advance, log in, and try a quick run-through so you are not learning the interface live. CoderPad, HackerRank, CodeSignal, and a plain shared Google Doc all behave differently. Knowing whether you can run code, whether autocomplete is on, and how to switch language saves you from fumbling in the first five minutes when first impressions are forming. For more on the technical screen itself, see the technical phone screen prep guide.

A quick connection sanity check

If you want to know whether your connection is genuinely up to a video call rather than just feeling fine for browsing, a short command line check tells you more than a speed test website. On macOS or Linux:

# Is the connection stable, or does it spike and drop packets?
ping -c 20 8.8.8.8

# Look at the summary line: low average latency and 0% packet loss is what you want.
# Latency under ~60ms and no packet loss means video will hold up.
# Spikes into the hundreds, or any loss, means move closer to the router or go wired.

Run this a few times across the day if you work from home, because contention from other devices is what usually breaks a call, not raw bandwidth. Zoom recommends only about 1.2 Mbps up and down for 720p one-to-one video, which almost any modern connection clears with room to spare. That is the point: a call breaks on jitter and packet loss from a congested link, not on a low headline speed. A 50 megabit line with two flatmates streaming can be worse for a call than a 20 megabit line with nobody else on it.

Get your environment right

Choose a quiet, private space where you will not be interrupted. A plain background is easier on the eye than a cluttered one, and you do not need a fancy office, just a tidy, neutral spot. If you share your home, tell the people you live with the time and ask them to keep noise down, and put pets somewhere they cannot interrupt. Booking a quiet meeting room, a library room, or simply a slot when the flat is empty is often the single highest-value thing you can do.

A note on virtual backgrounds, since they tempt everyone with a messy room. They work against you more often than for you. On a modest webcam the edge detection smears, your head develops a green halo, and your hands vanish when you gesture. A real, plain wall always reads better than a fake beach. If your only option is a virtual background, keep still, sit against a contrasting backdrop, and test it on a recorded call first so you can see the artefacts the interviewer will see.

Lighting matters more than people expect. Face a window or a lamp so the light falls on your face, and avoid sitting with a bright window behind you, which turns you into a silhouette. A simple desk lamp angled toward you, ideally bounced off a wall or through a sheet of paper to soften it, can transform how you come across on a cheap webcam. The aim is even light on your face, not a spotlight.

Reduce the things that can derail you:

• Silence phone notifications and close noisy apps on the computer you are using, especially Slack, email, and calendar pop-ups that can flash on screen during a share.
• Mute other devices that might ring or buzz nearby, including a second phone or a smart speaker.
• Have a glass of water within reach so you do not need to leave the frame.
• Keep the room at a comfortable temperature, since you may be sitting still for an hour and a stuffy room makes you flustered.

Camera and audio basics

Position the camera at roughly eye level. A laptop on the desk often points up at you unflatteringly, so raise it on a stand or a stack of books until the lens is level with your eyes. Sit far enough back that your head and shoulders are in frame rather than filling it, with a little space above your head. Centre yourself horizontally. These are small adjustments that make you look composed and attentive rather than looming or off to one side.

Audio is the part most worth investing in, and the part most candidates neglect. Built-in laptop microphones pick up room echo and key clatter, so a basic wired headset or earphones with a mic usually sounds noticeably clearer and also stops feedback. Wired beats wireless for interviews, because a Bluetooth earpiece that dies or drops mid-answer is one more thing to manage. Test the audio in your platform check and listen back to a recording if you can, because what sounds fine to you can be muddy to the listener. Turn off any aggressive noise suppression that chops the start of your words.

When the call starts, look at the camera lens rather than at the person's face on screen when you are speaking. It feels unnatural at first, but it is what creates the sense of eye contact for the other person. Glancing at their image when they speak is fine and natural. A useful trick is to move the video window up near your webcam so the gap between the two is small.

Match the setup to the format of the round

Setup is not one size fits all. The format of the round decides which part of the channel carries the weight, so put your preparation where that round will actually test you. Find out the format when you accept the slot, then rehearse the exact tool it uses.

• A conversational or behavioral round rides almost entirely on audio and presence. Clean sound and a steady eye line matter more than anything on your screen. A wired headset and a tidy frame clear the bar; there is nothing to install and nothing to demo.
• A live coding round happens inside a shared editor, so rehearse the tool, not just the call. Open CoderPad, HackerRank, or CodeSignal in advance, confirm you can run code and switch language, and check that screen sharing works in that specific platform. Fumbling the share button in the first minute is a self-inflicted wound.
• A system design round runs on a shared whiteboard such as Excalidraw or a Miro board. Draw a few boxes and arrows with your trackpad before the call, because learning the canvas live burns the minutes you need for the design itself. This is where a second screen for your notes, while you share the canvas, first earns its place.
• A panel round puts the load on presenting to several faces at once. Rehearse switching between a shared screen and your camera, and confirm the platform keeps every panelist visible so you are not talking into a wall of black tiles.

The common thread is that "test your setup" means test the setup for this round, on this tool. A behavioral round forgives a rough screen share; a live coding round does not. When the recruiter tells you the format, that is your instruction for what to rehearse.

Have your materials to hand

One genuine advantage of a remote interview is that you can keep notes nearby without anyone seeing them. Use it sensibly. A single page with your key points, the questions you want to ask, and a couple of reminders is genuinely helpful. Reading long scripted answers off the screen is not, because it shows in your delivery, your eyes drift and your voice flattens into a recital. The interviewer can tell instantly when someone is reading.

Keep open and ready:

• A short note of your main talking points and the questions you want to ask them.
• Your CV and the job description, in case you want to reference a specific detail. If your CV needs work first, the resume templates are a good starting point.
• Any portfolio or project links the interviewer might ask you to show, already loaded in a browser tab.
• A pen and paper for jotting names and follow-ups, which is quieter than typing and keeps your eyes up.

Position any notes directly beneath your webcam rather than off to the side, so that glancing at them does not swing your eyes away from the lens.

A worked example: the first ninety seconds

It helps to rehearse the opening, because it is where nerves and setup problems collide. Here is how a composed start sounds when a small glitch appears, which is realistic rather than idealised.

Interviewer: Hi, can you hear me okay?

You: Hi, yes, loud and clear. Can you hear me alright? I'm on a headset so it should be clean.

Interviewer: Perfect. Sounds great.

You: Brilliant. Before we start, I've got a notepad here for jotting down anything I want to come back to, just so you know what I'm glancing at.

Interviewer: No problem at all. So, tell me a bit about your recent work.

You: Sure. (your audio briefly cuts) ...sorry, I think I dropped out for a second there. Did you catch the start of that, or shall I take it from the top?

Interviewer: From the top, please.

You: No problem. So over the last two years I've been working on...

Notice what happened. You confirmed audio in both directions, you pre-empted the "why are they looking away" question by naming the notepad, and when the connection hiccupped you named it plainly and offered to repeat. None of that is impressive on its own. Together it tells the interviewer you are calm and easy to work with, before you have said a single thing about engineering.

The setup failures that quietly cost offers

These come up again and again, and every one is preventable.

1. Testing the wrong device. You check the call on your phone, then join on a laptop whose mic is broken. Always test the exact machine, in the exact app, that you will use on the day.
2. The bright window behind you. It feels well lit to you and turns you into a silhouette to them. Turn to face the light instead.
3. Reading answers off the screen. Your eyes track left to right and your voice goes flat. Keep notes to bullet prompts, never full sentences.
4. Forgetting to mute notifications. A Slack ping that flashes a colleague's message across your shared screen is at best distracting and at worst a confidentiality problem.
5. No backup plan. When the WiFi drops you freeze, fumble, and lose two minutes of composure. Have the recruiter's number and a charged phone ready.
6. Joining at the exact minute. Aim to be in the waiting room two to three minutes early. Joining late, or joining flustered after a last-minute update, sets the wrong tone before you speak.
7. Over-engineering the look. Spending an hour on lighting rigs while neglecting the audio. Sound clarity outranks visual polish almost every time.

When something goes wrong

Technical problems happen to everyone, and how you handle them says more than the problem itself. If your connection drops, do not panic. Rejoin calmly, and if it keeps happening, suggest switching to a phone call or audio only. Interviewers deal with this constantly and a composed response reads well. In a remote-first company it is genuinely part of what they are assessing.

A few recovery habits worth having ready:

• Keep the recruiter's phone number or email open in case you are knocked offline entirely, so you can message "lost connection, rejoining now" within seconds.
• If the video freezes but audio holds, say so and carry on rather than going silent. Silence reads as confusion, a quick "my video has frozen but I can still hear you" reads as competence.
• If background noise erupts, apologise briefly, mute if needed, and continue without making a drama of it.
• Have a backup device nearby, such as your phone with the app installed and you already signed in, in case the laptop fails entirely.
• If a coding tool stops responding, narrate your thinking out loud while you reload, so the interviewer sees your reasoning continue even when the screen does not.

Naming a problem plainly and moving on quickly is far better than pretending it is not happening or letting silence stretch. The recovery is the message.

A quick pre-call checklist

- Platform installed, updated, and tested on the right device
- Camera at eye level, head and shoulders in frame, centred
- Headset or earphones tested for clear, echo-free audio
- Light on your face, no bright window behind you
- Notifications silenced, household and pets briefed
- Notes, CV, and links open; water within reach
- Recruiter contact details and a backup device accessible
- Joined the waiting room two to three minutes early

Run through it ten minutes before you join, take a breath, and then treat it like any other conversation. With the setup handled, you are free to focus entirely on what you say.

Frequently asked questions

Do I need to buy a dedicated microphone or webcam? No. A pair of wired earphones with an inline mic, decent front lighting, and a stable connection clears the bar for nearly every interview. Buy a dedicated USB mic only if you interview often or your room has bad acoustics.

Should I use a virtual or blurred background? Prefer a real, plain wall. A blur is acceptable and reads better than a beach scene, but it still smears your edges when you move. If you must use one, test it on a recording first so you see what the interviewer sees.

Is it acceptable to keep notes on screen? Yes, and it is one of the few real advantages of remote interviews. Keep them to short bullet prompts placed just below your webcam, never full scripted answers, which always show in your delivery.

What if I am interviewing from a noisy or shared space entirely? Book a library or co-working room, or ask the recruiter whether the slot can move to a quieter time. Most will accommodate this if you ask in advance. A clear ask beats a noisy call.

How early should I join? Two to three minutes before the start. Early enough to handle a last-second prompt or permission dialog, not so early that you are sitting awkwardly in an empty room.

My connection is unreliable. What is my fallback? Tell the recruiter beforehand, keep your phone charged with the app installed and signed in, and be ready to suggest switching to audio only. Proactively flagging a known risk is far better than going dark mid-answer.

Sources

• Zoom system requirements and recommended bandwidth
• Connect your video and audio in Google Meet
• Make a test call and manage devices in Microsoft Teams

Where to go next

With the channel handled, put the hours into what you actually say:

• Technical phone screen prep for the round most remote setups are built around
• Remote job search in 2026 for the wider search that leads to these calls
• Mock interview practice plan to rehearse the substance out loud before the real thing