After the loop: the debrief

Most candidates lose the same offer twice, because a rejection with no written record teaches nothing. Fill this in within a couple of hours of any loop, pass or fail, and it turns what you remember into the next thing to study.

How to use it

Write it within two hours of the loop, while you can still quote the questions. After a day you will remember your feelings and not the wording.
Copy the questions down verbatim, even the ones you answered well, because the set of questions tells you what the company is actually scoring.
Guess the reason before you hear any feedback. The guess you make cold is more useful than the sanitised summary a recruiter gives you a week later.
When feedback does arrive, paste it in without editing it. Softening it is how the same gap survives three loops.
Do the same for a rejection with no feedback at all. The pattern across three of these is the feedback.

Cues that the room changed

Interviewers rarely say anything is wrong. These are the tells, and the point of writing one down is that the moment before it is usually the answer that cost you.

The interviewer stopped taking notes.
They asked the same question a second time in different words.
They moved on before you finished an answer.
They started filling your silences for you.
They stopped asking follow-ups and went to their next scripted question.
They asked how many engineers reported to you, and then asked again about the structure.
They ended ten minutes early.

Your entries

Everything here is stored in this browser only. Nothing is uploaded, and clearing your browser data clears it, so export anything you want to keep.