Passing a remote technical interview

A remote technical interview is not a normal interview moved into a camera. The rules change, and those who fail are not always the least skilled. They are often the ones who did not notice the rules had changed.

What the interviewer no longer sees, and how to give it back

In person, the person assessing you picks up a mass of signals without thinking: your hesitation, where your eyes settle, the moment you understand. Remotely, all of that disappears. All they have left is your words, and a silence they cannot read as thinking or as being lost.

The practical consequence is simple: what you do not say does not exist. A candidate who thinks silently for forty seconds and then gives a correct answer leaves a worse impression than one who thinks aloud and arrives at the same place. Narrate your reasoning, including the paths you rule out, and above all why you rule them out.

The most common question is not a technical one

In nearly every interview, one question comes back in some form: tell me about a hard problem you solved. It is decisive because it cannot be recited, and because the answer reveals at once whether you have practised or only studied.

A good answer has four beats: the context in one sentence, what made it hard, what you tried that failed, then what worked. The part candidates cut out of embarrassment, the failed attempts, is exactly the part that proves you were there.

An answer with no hesitation sounds like a learned answer. That is not a compliment.

Saying « I don't know » without losing the interview

Many candidates sink themselves trying to cover a gap. The interviewer, who knows the subject, always spots it, and the doubt then spreads to everything you said before. An admitted gap costs a few points. A hidden one costs the interview.

The right phrasing does not stop at the admission. Say what you do not know, then what you know that is close, then how you would find the answer in real conditions. You turn a hole into a demonstration of method, which is exactly what is being assessed in a professional.

The setup is part of the assessment

This is the most unfair point and the easiest to fix. Choppy audio, a backlit face, a dropout in the middle of an explanation: none of it says anything about your skill, and all of it weighs on the decision, because the interviewer is imagining a year of meetings under those conditions.

• Test the link the day before, not five minutes before, with the exact tool that will be used.
• Put audio first: a decent microphone matters more than a nice picture.
• Have a fallback announced in advance, a phone number for instance, and mention it at the start.
• Put the light in front of you rather than behind, and check what the camera shows of the room.
• Keep something to write on, off screen. Taking a note while someone speaks reads better than typing.

Practising for real

Rereading your notes is not practice. The only preparation that counts is answering out loud, in real conditions, facing someone who can interrupt you and ask why. It is uncomfortable, and that discomfort is precisely what you want to have felt once before the day itself.

If nobody around you knows the trade, at least do the exercise alone, recording yourself, then listen back. Most people discover they speak too fast, that they open with detail instead of the conclusion, and that they never stop early enough.