In a remote coding or screen-share session, how do you keep the interviewer with you when they can't see your face clearly or read the room?
culture-fit · Junior level · general
What the interviewer is really asking
Reveals whether you can communicate your thinking and collaborate in a remote format, since over a screen share the interviewer loses the in-person cues and relies on you narrating your reasoning rather than just watching your code.
What to say
- Say you'd narrate your thinking out loud, stating your plan before you type and explaining trade-offs as you go, so the interviewer follows your reasoning and not just your keystrokes.
- Treat it as collaboration: check in at decision points, invite hints, and confirm you understood the problem before diving in, rather than going heads-down and silent.
- Handle the screen-share basics smoothly, like sharing the right window, using a readable font size, and pausing if you need to think instead of typing in tense silence.
What to avoid
- Don't say you'd just code quietly and explain at the end, which leaves the interviewer guessing whether you're stuck or thinking.
- Avoid ignoring the interviewer entirely once you start typing, since remote sessions are meant to be two-way.
- Don't let a long silent pause sit there when you're stuck instead of saying what you're weighing or asking a question.
Example answers
Strong: Because they can't lean over and see my screen the way they could in person, I make my thinking the thing they hear. I restate the problem first to confirm I've got it, then say my plan before I write anything, like 'I'll start with a brute-force pass to get it correct, then look at the time complexity.' As I code I flag decisions out loud and check in, and if I go quiet to think I say so rather than leaving dead air. I also bump the font size and confirm they can see the right window before I start.
Weak: I focus on getting the code working and then walk them through it once it's done, so I'm not distracted while I think.