Taking Interview Notes & Getting Feedback

The candidates who improve fastest aren't the most talented — they're the ones who take notes. After every interview, while it's fresh, they capture what was asked, how they answered, and how it landed. Ten minutes of writing turns one interview into training data for the next one. Skip it, and you'll repeat the same stumble in company after company.

The key idea: an interview you don't debrief is experience wasted. Memory edits itself within hours — capture the raw version before your brain starts telling you a nicer story.

The ten-minute debrief template

Do this immediately after every interview — in the parking lot, on the train, wherever. Don't wait until evening.

1. Questions asked. List every question you can remember, verbatim if possible. These are gold for future prep and for spotting patterns across companies.
2. My answers, honestly graded. For each question: strong, okay, or weak? One line on why. "Weak — rambled, never landed the result."
3. Moments that shifted the room. What made them lean in? What made them check the clock? Energy changes are feedback even when nobody says a word.
4. What I'd do differently. Exactly one or two items. More than that and you'll fix none of them.
5. Follow-ups owed. Names, promised materials, anything to include in your thank-you email.

Handling explicit feedback

Sometimes you get actual feedback — from a recruiter, a rejection email, or a kind interviewer. Treat it as a gift, even when it stings. Write it down verbatim, then translate it into an action: "wanted more technical depth" becomes "add architecture detail to my scaling story." Vague feedback like "not the right fit" still yields something if you cross-reference your own notes from that day.

The debrief only pays off when it feeds forward, so build the bridge: the day before your next interview, skim the last few entries and extract two things — the question that tripped you most recently (rehearse a better answer, out loud, once) and the fix you committed to last time (check whether you actually applied it). That ten-minute review is what turns a pile of notes into a learning loop. Without it you're keeping a diary; with it you're running a system that tightens every round, and after a handful of loops the improvement stops being subtle.

What to avoid

• Only noting the disasters. Your wins are data too — double down on what worked.
• Rewriting history. If an answer flopped, record the flop. A polished memory teaches nothing.
• Letting notes pile up unread. Review them before every new interview; that's the entire point.

FAQ

Where should I keep all this? Anywhere searchable and tied to each application — a notes app works, and the job tracker keeps debriefs attached to the right company automatically.

Is it okay to take notes during the interview itself? Yes — briefly. Jotting a keyword or a follow-up is professional. Transcribing the conversation is not. Eye contact beats stenography.

One last nudge: set the bar at "done," not "perfect." A rough debrief written in the car beats an elegant one you never get to. Ten interviews from now, that scrappy stack of notes will be the most valuable document in your entire search — a personal map of what companies actually ask and how you actually answer. Start tonight, while the most recent conversation is still warm in your memory.