Shadow Interviewer in Your Coding Interview? Who the Silent Second Person Is

A shadow interviewer is usually someone learning to interview. They sit in on a real round, often with the camera off. There are two setups. They flip who the quiet person is. In a shadow, a trainee watches an experienced lead. In a reverse shadow, the trainee leads and the experienced interviewer watches. So the silent person may be the most senior person on the call. Companies don’t agree on whether that person’s opinion counts. One vendor guide tells shadows to score the candidate on their own. Another says observers shouldn’t influence the decision. You can’t tell from the call which rule applies. So treat both people as scoring. Speak so the quiet one could write notes from your words alone. If the lead seems new, run the clock and pin down the constraints yourself. Below, one Android engineer’s coding round shows both setups, with a script you can adapt.

The silent person can be a trainee or the senior interviewer

Evidenced’s guide to interview shadowing defines both forms. Shadowing means attending a round led by someone more experienced, to learn. Reverse shadowing means attending a round led by a trainee, to support them. The guide was updated in October 2024. Evidenced sells interview recording software, so it has an interest in more shadowing.

A new interviewer usually does both in order. They watch a few rounds first. Then they lead a few while someone experienced watches. Then they interview alone. GitLab publishes one version of this in its handbook page on hiring technical writers. A writer who wants to interview must shadow two interviews and be shadowed in one. They can ask for more until they feel ready.

Technical interviewers may need more practice than that. Metaview’s October 2025 post on shadowing suggests five to seven live shadows for technical roles. Metaview also sells interview recording tools. Either way, a growing team trains many new interviewers. Each one sits through several real rounds. So a second face on your call is a normal part of how hiring teams grow.

Nobody can tell you from the call whether the shadow interviewer scores you

The two vendor guides disagree on this point. Evidenced tells shadows to practice note taking and scoring. It tells them to reach their own decision before hearing the lead’s rating. It also says shadowing gives a team more opinions on the candidate. That reads like a second assessment.

Metaview’s FAQ goes the other way. It tells teams to warn the candidate in advance. It says to explain that the observer is training and won’t influence the decision.

Large tech companies don’t publish their rule. A shadow’s notes might be ignored, read as context or weighed fully. The rule might also differ between a shadow and a reverse shadow. In a reverse shadow, the silent person is the experienced one. Their view of the round may carry real weight.

So plan for the stricter case. Assume two people write notes. Those notes are what the later hiring decision is made from.

A reverse shadow puts the clock in your hands

A trainee lead changes the round in practical ways. They may answer clarifying questions slowly or vaguely. They may give a hint that is bigger or smaller than intended. They may lose track of time.

The experienced interviewer usually won’t rescue the round fast. Evidenced tells reverse shadows to let the trainee find their own way. It says to step in only once the trainee has exhausted a line of questioning. The guide warns that interrupting early can leave the candidate with a poor impression.

So a reverse shadow can drift for ten minutes before anyone corrects it. That time comes out of your 45 minutes. The fix is to run three things yourself. Write the constraints down where both can see them. Say your time plan out loud. Ask small questions when stuck, so the size of any hint stays clear.

One coding round with a quiet second interviewer

Take an Android engineer in a 45-minute virtual coding round. The lead introduces themselves. A second person, camera off, says they’re just shadowing today.

The prompt is about an app’s crash log. The entries are sorted by timestamp. Several entries can share one timestamp. Return the first and last index of a given timestamp, or minus one for both if it’s missing.

The lead reads the prompt from a document. The engineer asks whether the log can be empty. The lead pauses, then says they’ll check. That pause could mean a new interviewer. It could also mean nothing. Either way, the engineer can run the round the same way.

A script for the first two minutes, the middle and the end

Here is the opening, said right after the prompt.

Thanks, both of you. I’ll think out loud so you can each follow along. Let me write the constraints at the top of the file first. The log is sorted by timestamp. Timestamps can repeat. I’ll return minus one for both indexes if the timestamp is missing. I’ll assume the log can be empty and handle that. Tell me if any of that is wrong.

Then the engineer states a plan and a time budget.

A linear scan works. It’s O(n), though. Since the log is sorted, I’ll use two binary searches. One finds the leftmost match. The other finds the rightmost. That’s O(log n). I’m aiming for working code by about minute 25. That leaves ten minutes to test duplicates, a missing value and an empty log. Does that fit what you need to cover?

Around minute 18, the right-side search never ends on the sample log. The engineer says so before asking anything.

My right search never ends once low and high sit next to each other. My midpoint rounds down, so low never moves. I’ll round the midpoint up for this search. Or would you rather I keep one search and pass a flag?

Near the end, the shadow speaks for the first time. They ask what happens if the log has a million entries.

Two binary searches stay at about 40 comparisons for a million entries. The bigger cost would be loading the log into memory at all. On Android, I’d page it from disk instead. Should I sketch that, or stay with the in-memory version?

The engineer then saves two minutes for questions. They ask the lead one question about the team’s work. They ask the second person one too.

Why each part of the script works in either setup

The constraints at the top of the file fix the answer to the empty-log question in writing. If the lead’s answers shift, both interviewers can see what was agreed. A trainee’s notes and a senior’s notes then describe the same problem.

The time budget does the lead’s job without saying so. An experienced lead will just confirm it. A trainee lead gets a plan to follow. The silent senior hears a candidate who manages the round.

The stuck moment names the bug and the likely cause first. That keeps any hint small, whoever gives it. Our post on taking a hint in a coding interview covers why hint size matters.

The answer to the shadow’s question treats it as a real follow-up. In a reverse shadow, that question may be the senior filling a gap the trainee left. Answering it fully, then handing back to the lead, keeps the round with the lead.

The two closing questions cost nothing. The second person may be writing a note too. Now they also have a conversation to remember.

What to ask the recruiter before and after the round

Before the loop, one question removes the surprise. Ask it by email so the answer is in writing.

Will each round be one-on-one, or might some include a second interviewer who is training? If so, does that person’s feedback go into the decision?

The recruiter may not know, or may not say. You prepare the same way either way. The point is that a quiet second face won’t throw you on the day.

Metaview’s FAQ says teams should let a candidate ask for the observer to leave. That is advice to hiring teams. It doesn’t bind any company. Asking can also start the round on a strained note. Our advice is to keep the observer and run the round as above.

After the round, speak up only if the setup cost you something concrete. Maybe the prompt changed halfway, or a clarifying question never got an answer. Tell the recruiter within a day, in two or three plain sentences. Describe what happened. Leave out guesses about who was new. You can’t know whether the round will be discounted. But the recruiter is the only channel that reaches the people who decide.

Leave a Comment