Remote Technical Interview Setup Guide: Camera, Code Editor, and Environment

Let me tell you about the worst twelve minutes of my professional life.

It was a Tuesday morning. I had a remote interview with a company I’d been chasing for months. Senior backend role. I’d studied for weeks — algorithms, system design, the whole playbook. Walked into my home office feeling ready.

Then everything fell apart.

My Wi-Fi dropped during the intro. Not fully — just enough to freeze my face mid-sentence while my audio kept going. According to the interviewer, I looked like a haunted portrait that was also discussing database sharding. When the connection stabilized, I shared my screen. Wrong screen. The one with my personal Slack open. With a message to my friend that said, and I quote, “about to do this interview, pray for me.” I scrambled to switch. Then realized my camera was angled so low it was basically filming my chin and the ceiling behind me. I looked like I was FaceTiming someone from a hospital bed.

I did not get that job.

And look — my coding skills were fine. My prep was solid. But none of that mattered because the interviewer spent the first ten minutes watching me fight my own setup like it was my first time using a computer. First impressions are cruel like that.

I swore I’d never let it happen again. Since then, I’ve done probably forty remote interviews from both sides of the screen, and I’ve developed what my partner lovingly calls “the ritual.” It takes thirty minutes. It’s saved me every time.

Here’s everything I’ve learned.

Your hardware setup matters more than you think

Camera position. Put your camera at eye level. I cannot stress this enough. If you’re using a laptop on a desk, you’re looking down at the camera, and the interviewer is staring up your nostrils. Grab a stack of books, an old Amazon box, a monitor stand — whatever gets the lens roughly level with your eyes.

I use a cheap laptop riser I got for twenty bucks. Best interview investment I’ve ever made. When your camera is at eye level, you look engaged and professional. When it’s below you, you look like you’re judging the interviewer from a throne.

Lighting. Face a window. That’s it. That’s the tip. Natural light hitting your face from the front is better than any ring light. If you can’t face a window, put a desk lamp behind your monitor aimed at your face — not at the ceiling, not at the wall. At you.

The worst lighting setup: a bright window behind you. You become a silhouette. I once interviewed a candidate who looked like they were in witness protection the entire time. I could see their screen share perfectly but their face was just… darkness with occasional teeth.

Microphone. Your laptop mic picks up everything — keyboard, fan, that neighbor who mows his lawn at 9am on weekdays (I hate that guy). Use a headset or an external mic. AirPods work. Those gaming headphones you’re embarrassed about work. Anything that puts the mic closer to your mouth and farther from the noise.

Quick test: record yourself typing while talking. If the keystrokes are louder than your voice, fix your mic situation.

Dual monitors. If you have two screens, decide beforehand which one you’ll share. I made the mistake once of sharing my primary monitor while my notes were on the secondary. Spent the whole interview visibly looking away from the camera to read things the interviewer couldn’t see. It looked like I was cheating. I wasn’t. But it looked like it, and that’s what matters.

My rule: share the screen directly below/behind your camera. That way, when you look at your code, you’re also roughly looking at the camera. Geometry works in your favor for once.

Software setup: the boring stuff that saves you

Before interview day, make sure you’ve tested the platform they’re using. Zoom, Google Meet, Microsoft Teams — they all behave slightly differently with screen sharing. And then there are the coding platforms: CoderPad, HackerRank, CodeSignal, LiveCode. Each one has its quirks.

Here’s my prep list:

• Install the app version of whatever video platform they’re using. Browser versions are buggier, especially for screen sharing. I learned this when Chrome decided my “entire screen” share should include only the top-left quarter of my screen. Thanks, Chrome.
• Test screen sharing at least once. Share your screen with a friend, your partner, your mom. Anyone who can tell you “I can see your screen and it’s not tiny.”
• Close everything you don’t need. Slack, email, messaging apps. Not minimize — close. macOS is especially fun because notifications slide in from the corner right when you’re explaining a recursive function. “As you can see, the base case— oh, that’s a message from my dentist.”
• Disable notifications. On Mac: Focus mode. On Windows: Focus assist. Do this thirty minutes before, not thirty seconds before.
• Log into the coding platform early. Some require account creation. Some need browser permissions. HackerRank once asked me to grant camera AND mic access separately from the video call, and it took three minutes of clicking “allow” on various browser prompts.

One more thing: if they send a link, click it the day before. Not to join the call — just to make sure it opens. I’ve had links that required a VPN I didn’t have, a browser I didn’t have, and once, a Windows-only desktop app. (I use a Mac. That was a fun email to send.)

Code editor setup: the details interviewers actually notice

When you’re sharing your screen and writing code, the interviewer is staring at your editor for thirty to forty-five minutes straight. Make it comfortable for them.

Font size. Bump it up. Way up. What looks fine on your 27-inch monitor looks like ant footprints on the interviewer’s 13-inch laptop. I go to at least 16px, sometimes 18. Yes, you’ll see fewer lines. That’s fine. Readability beats density.

Theme. Controversial take: use a light theme. I know, I know. We all love our dark themes. But light backgrounds with dark text have better readability on compressed video calls. Dark themes can look muddy when the video quality dips. I switch to a light theme for interviews and switch back immediately after. My colleagues don’t need to know.

Tab key conflicts. This one bites people constantly. In browser-based coding environments (CoderPad, HackerRank), pressing Tab might switch focus to the next UI element instead of indenting your code. Test this before the interview. Most platforms have a setting to “capture tab key” — find it, enable it, and save yourself the moment of pressing Tab and watching your cursor teleport to the “Submit” button.

Auto-complete and linters. If you’re using your own IDE for a take-home or shared-screen session, disable aggressive auto-complete. It’s distracting for the interviewer when suggestions keep popping up, and you’ll look like you’re relying on your tools instead of your knowledge. Keep basic syntax highlighting. Kill the rest.

Your environment: what’s behind you and around you

Background. A blank wall is perfect. A bookshelf is fine. Your bed with yesterday’s clothes on it is not fine. Virtual backgrounds are risky — they glitch at the edges, they eat CPU, and they make you look like a floating head in a stock photo of an office.

If your space is messy, just reposition the camera to frame a cleaner angle. I once did an interview from my kitchen because it had the cleanest wall in my apartment. The interviewer didn’t know. Or care.

Noise. Close the window. Tell your roommates. Put a sign on the door. I have a small whiteboard sign that says “INTERVIEW - DO NOT ENTER OR I WILL END YOU” which my partner finds dramatic but effective.

If you have a dog, put them in another room with a toy. If you have a cat… well, good luck. Cats don’t read signs. If the cat walks across your keyboard mid-interview, own it with a quick “sorry about that” and move on. Every interviewer has seen it. Most find it charming. Once.

Backup plan. What if your Wi-Fi dies? Have your phone ready as a mobile hotspot. Know the password. Test it once.

What if your power goes out? Have a backup location in mind — a nearby cafe, a friend’s place, a coworking space. You probably won’t need it. But knowing you have a plan B removes a layer of anxiety, and you don’t need extra anxiety before an interview.

The 30-minute pre-interview checklist

This is the ritual. I do this every single time.

T-minus 30 minutes:

• Close all apps except the ones you need
• Enable Do Not Disturb / Focus mode
• Plug in your laptop (battery anxiety is real)
• Open the video platform, test audio and video
• Check your camera angle and lighting

T-minus 20 minutes:

• Open the coding platform, log in, check tab key behavior
• Set your editor font size and theme
• Open a blank file and type a few lines to make sure everything feels right
• Have a glass of water within reach (talking for an hour dries you out)

T-minus 10 minutes:

• Do a final screen share test (share with yourself if needed — Zoom lets you do this)
• Check your background in the camera preview
• Put your phone on silent (not vibrate — silent)
• Close the door

T-minus 2 minutes:

• Take three deep breaths
• Remind yourself you prepared for this
• Join the call

I wrote this checklist on a sticky note after my disaster interview. It lives on my monitor permanently now. My partner thinks it’s overkill. My partner has also never had to explain to an interviewer why their Slack messages were visible on screen.

During the interview: screen sharing like a professional

Once you’re in the call and coding, a few things make a huge difference.

Share a specific window, not your entire screen. If you share your whole screen, every notification, every app switch, every accidental click is visible. Share just the code editor or just the browser tab with the coding platform.

Picture-in-picture. Most video platforms let you pop out the video feed into a small floating window. Do this. It lets you see the interviewer’s face while you’re coding. Their reactions are useful information — a nod means you’re on track, a slight frown means you might want to explain your thinking more. And maintaining that visual connection makes the conversation feel more natural, even when you’re staring at code.

Narrate what you’re doing. “I’m going to start by writing a helper function for…” This is good practice for any interview, but it’s especially important remotely because the interviewer can’t see your body language. They can’t tell if you’re thinking or stuck. Words are the only signal they get.

If something breaks, say so immediately. “I think my audio just cut out — can you hear me?” is so much better than three minutes of the interviewer wondering if you’re ignoring them. Technical issues happen. How you handle them is part of the interview whether anyone admits it or not.

Stuff people always ask me

Do I really need an external camera or mic? No. A recent laptop with a decent built-in camera and headphones with a mic (even basic earbuds) will get you 90% of the way there. The key is positioning and testing, not expensive gear. I did my best interview ever on a three-year-old ThinkPad with ten-dollar earbuds.

What if the interviewer’s setup is terrible? It happens. If you can’t hear them, say so politely and early. “I’m having a bit of trouble hearing you — would you mind checking your mic?” Better to fix it in minute one than to nod along for thirty minutes pretending you understood the question.

Should I use my own IDE or the platform’s editor? Use whatever they provide unless they explicitly say otherwise. Some companies monitor the coding environment for integrity. If they say “feel free to use your own editor,” then go for it — but test screen sharing with that editor first.

Is it okay to have notes visible? Brief notes about the company, the role, and your own questions — sure. A cheat sheet of algorithms — no. If you need to glance at something, be transparent about it. “I jotted down a few questions I wanted to ask about the team” is fine. Suspiciously reading off-screen while solving a binary tree problem is not.

If you’re still building your overall interview prep strategy, I’d start with how to prepare for a technical interview for the study plan and the technical interview checklist for what to do in the final 48 hours.

Ready to nail your next remote interview? Join the early access community —>