What to Write Down After Every Interview Round (and What to Leave Out)

You come out of a technical round with the whole thing still loud in your head. The question you nearly solved. The follow-up you did not see coming. The thing the interviewer said about their team that told you more than the job description did.

You think: I will not forget this.

You forget it. Not all at once — the shape survives, but the detail goes. By the next morning you have "something about caching." By the following week you could not reconstruct the question if someone paid you. And the detail was the valuable part.

This is a small habit with a large return: fifteen minutes of structured notes after every round. Here is what to capture, what to deliberately leave out, and why the format you use decides what those notes are worth six months later.

Why it is worth the fifteen minutes

Three reasons, in ascending order of how much people underrate them.

• You may interview here again. Companies re-open roles, recruiters come back a year later, and rejections at the final round are often invitations to reapply. Turning up to the same loop with notes from last time is an enormous advantage, and almost nobody has them.
• Companies ask each other's questions. Interview processes converge. A system design round at one company is a decent rehearsal for the next one, but only if you can remember what was actually asked rather than that it was "about scaling."
• The pattern only shows up across rounds. One round tells you nothing. Six rounds of notes tell you that you consistently run out of time on the follow-up, or that you always fumble the same category of question. That is the diagnosis you cannot get from memory, because memory keeps the rounds that went well.

Do it the same day

Not because of any particular rule about memory, but because of a practical one: the next thing in your calendar overwrites the last one. If you have a second interview that week, the first round's detail is competing with active prep, and it loses.

The realistic version is fifteen minutes the same evening. Not a polished write-up — a structured dump while you can still hear the interviewer's phrasing.

What to actually capture

1. The questions, as close to verbatim as you can

This is the single highest-value thing on the list. Not "a graph question" — the actual question, with its constraints, because the constraints are what made it hard. If it came with a follow-up ("now do it without extra space"), that is part of the question, not a footnote.

2. What you actually answered

Including the wrong turn you took before correcting. Reviewing this later is uncomfortable and it is where the improvement is. Your future self wants to know what you said, not a flattering reconstruction of what you meant.

3. Where it went wrong

Be specific enough to act on. "Struggled with the DP question" is not actionable. "Could not identify the subproblem, spent eight minutes on a greedy approach that did not work" is a study plan.

4. The interviewer's reactions and follow-ups

Where they pushed, where they moved on quickly, what they seemed to be probing for. This is how you learn what a company actually values, which is rarely what the job description says.

5. The boring logistics

Round name, date, format, length, whether it was a shared editor or a whiteboard, whether it was recorded. Dull, and exactly what you cannot reconstruct later. It is also what makes your notes useful to anyone else.

6. Your read, while it is honest

How you thought it went, written before you know the outcome. This is the one people skip and the one that calibrates you fastest. Most people are badly wrong about how their interviews went, in both directions — and you can only find that out if you wrote the prediction down first.

What to deliberately leave out

Just as important, and rarely discussed. Notes you might one day share — or that might sit in a work account, or be seen over your shoulder — should not contain:

• The interviewer's name. Your notes are about a process, not a person. A named individual plus a critical opinion is the thing that turns useful notes into a problem.
• Anything covered by an NDA. Some processes, particularly take-homes and onsite system design, come with explicit terms. Honour them.
• Proprietary internal detail. Real architecture, real customer names, real numbers that came up in conversation. The question is shareable; their internals are not.
• Anything identifying other candidates you met in a group round or in the waiting room.

None of this reduces the value of the notes. The question, your answer and your assessment are the useful parts, and none of them require naming anybody.

A template you can copy

Structure beats prose here, because structured notes can be searched, compared and eventually shared. Prose cannot.

• Company and role
• Round — screen, technical, system design, behavioural, panel
• Date and format
• Questions — one entry each, with constraints and follow-ups
• My answer — per question, including the wrong turns
• What I would do differently
• Signals — what they pushed on, what they skipped
• My read — written before the outcome

Keep one of these per round rather than one per company. A four-round process is four documents, because merging them loses exactly the per-round detail you are trying to keep.

Where to keep them

Wherever you will actually do it — but the format has consequences.

A spreadsheet cell is the most common home and the worst one: a row is a single application, and an interview is four rounds with their own dates and questions. That is why it all ends up in one notes column as an unreadable run-on, a problem we covered in job application tracker vs. spreadsheet.

Lampzi's interview tracker exists for exactly this shape: rounds attached to the company they belong to, questions and answers as separate fields, notes with room for real detail rather than a cell limit. Rounds you log also appear on the job search calendar, so logging is not separate work from staying organised.

Four ways people get this wrong

• Only writing notes after bad rounds. Understandable, and it destroys the value. Your notes become a record of failures with no baseline, and you cannot see a pattern in a biased sample.
• Summarising instead of recording. "Standard behavioural questions" is not a note. It is the absence of one.
• Waiting for the outcome. By the time the rejection or offer arrives, the detail is gone and your memory has been rewritten by the result.
• Writing for nobody. Notes only you could parse are notes you will not parse in four months. Write them as if a stranger has to follow along, because effectively one does.

The second life of good notes

Once a process is finished — offer or rejection — well-structured notes stop being only yours.

The questions you were asked are the thing every candidate interviewing at that company next month is searching for and mostly failing to find. Glassdoor reviews are about working there. Forum threads are years stale. First-hand, structured, recent write-ups are genuinely scarce.

That is why Lampzi lets you publish a logged interview to the community interview experiences feed. It is anonymised by design rather than by request: published under a generated handle, interviewer names are never carried across, and exact dates are blurred to the month so a write-up cannot be traced back to a particular slot. You see exactly what will be public before anything is shared, and you can take it down at any time.

You do not have to publish anything. But it costs nothing once the notes already exist in the right shape — which is the real argument for taking fifteen minutes on the night rather than trusting your memory.

Final thoughts

Interview notes are one of those habits with an unfair return: fifteen minutes on an evening you are already tired, in exchange for something your future self cannot reconstruct at any price.

Start with the next round you sit. One round, the template above, written the same evening. You will know within two interviews whether it is worth continuing, and you will almost certainly find it was.

Log your next interview round on Lampzi — rounds, questions and outcomes per company, free with an account. And if the resume that got you the interview needs work, the LaTeX resume builder is in the same place.