What the Interviewer Is Actually Writing Down While You Talk
A Look Behind the Notepad at What Interviewers Are Really Recording During a System Design Interview, and Why It Is Not Your Whole Design
During a system design interview, there is a quiet activity happening on the other side of the table.
While the candidate talks and draws, the interviewer is taking notes. Most candidates never think about what those notes contain. They assume the interviewer is simply recording the design, capturing the boxes and arrows being drawn.
This assumption is wrong, and it leads candidates to focus on the wrong things. Interviewers are not transcribing the diagram.
They are collecting evidence. Each note is a small piece of a case they are building toward a final recommendation, and that case is about how the candidate thinks, communicates, and decides, far more than about the specific architecture produced.
Understanding what actually goes on the page changes how a candidate approaches the entire interview.
Once it is clear that the interviewer is looking for specific signals and recording specific moments, the candidate can deliberately produce those signals instead of guessing.
The interview stops being a mystery and becomes a process with visible rules.
This guide reveals what the interviewer is actually writing down while a candidate talks. It covers the signals they watch for, the moments they capture, and how those scattered notes turn into a score.
It is written to demystify the evaluation so that candidates can leave behind the kind of evidence that earns a strong rating.
They Are Building a Case, Not Copying a Diagram
The first thing to understand is the purpose of the notes.
The interviewer has to justify a recommendation after the interview ends, often to a hiring committee that was not in the room.
To do that, they need evidence. Their notes are that evidence.
This means they are not trying to capture the whole design. They are capturing the moments that reveal something about the candidate.
A clever architectural choice matters less than the reasoning that produced it.
A clean diagram matters less than the thinking that the candidate showed while building it.
So while a candidate worries about getting the design perfect, the interviewer is recording something different: the signals that show what kind of engineer this person is. Knowing this shifts the focus from the artifact to the thinking behind it.
They Note Whether You Clarified Before Designing
One of the first things an interviewer records is how the candidate started.
Did they ask clarifying questions and establish scope, or did they immediately start drawing boxes? This single behavior is a strong early signal.