The Notes You Take After Every Conversation
You finish a recruiter call. It went fine. You know what they said, vividly, because it happened four minutes ago.
Three weeks and two other processes later, you’re preparing for the second round and you cannot remember whether the team was six people or sixteen, whether the hybrid arrangement was two days or three, or the name of the person who’d be your manager. It was all in the call. The call is gone.
This is the cheapest fixable loss in a job search. Five minutes of writing immediately afterwards preserves the entire thing. Skip it and you are, functionally, starting each conversation from scratch — which the other side notices, and reasonably reads as not caring much.
Why memory fails here specifically
It isn’t a personal defect. Job-search conversations are unusually easy to lose because of three things happening at once.
They’re structurally similar. Four screening calls in a fortnight all cover the same ground in the same order, which is exactly the condition under which memories interfere with each other and details migrate between them. You will confidently attribute one company’s remote policy to another.
They’re spaced far apart. Weeks pass between contacts, and the gap is longer than the natural life of a detail you didn’t write down.
And you’re doing them in the margins — often between work meetings, often tired. Encoding is poor to begin with.
So: write it down. Not because your memory is bad, but because this is a case where nobody’s is good.
The eight fields
Do this within ten minutes of hanging up, before the next thing. It should take five minutes and it should be ugly — bullet fragments, not prose.
1. Date, channel, duration, and who. Full names and roles, spelled correctly. You’ll need them for follow-ups and for recognising a name in an email footer later.
2. What they said about the timeline. Verbatim if you can: “second round within two weeks, whole process usually four to five.” This is the single highest-value line in the whole note, because it’s what your follow-up anchors to. Following up against what they actually told you rather than against your anxiety is the difference described in the follow-up that is not annoying.
3. The next step, and whose move it is. “They send a panel invite” or “I send availability by Friday.” Then copy the mine-side item straight into your tracker’s next-action field.
4. Facts about the role you didn’t have before. Team size, why the role exists, who it reports to, what the first six months are meant to contain, the constraints they were unusually specific about. These are the details that make a later conversation feel continuous.
5. Constraints and conditions. Location and days on site, contract type, start date, anything stated as fixed. Record whether it was presented as firm or flexible, and record it in their words rather than your interpretation.
6. Questions you were asked that you answered badly. Not for self-flagellation — because they recur. A question that landed awkwardly in one screen will appear in the next one, and the note is what turns it into something you’ve thought about rather than something that ambushes you twice.
7. Anything they said about other roles or other teams. Recruiters mention adjacent openings constantly and candidates forget by the following week. This line occasionally produces a whole extra process.
8. Your own read, in one line. Did this sound like work you’d want? A one-line honest reaction, written before the process makes you want it by default, is surprisingly valuable eight weeks later when you’re comparing two options and everything has become abstract.
The template
Paste this at the bottom of the process page, above the previous entry so the newest is first:
--- 24 Jun, video, 30 min, Dana Okoye (recruiter) ---
TIMELINE "2nd round within 2 weeks; process usually 4-5 wks."
NEXT Me: send availability w/c 7 Jul, by Fri 27th.
Them: panel invite once slots agreed.
ROLE Team of 6. Splitting from central data next quarter.
Role open because previous holder moved internally.
Panel = Marc (would be my manager) + Sam (owns pipeline).
FIXED Hybrid 2 days on site — said "not really flexible".
Start date open.
ASKED ME Why leaving current role — answer was waffly, tighten it.
Whether I'd led a migration — I have, said it too briefly.
OTHER Mentioned a data-quality role opening in Q4, same org.
MY READ Liked the scope. Slightly worried the split means chaos.
Ten lines. It reads like nothing and it is worth an hour of preparation later.
Where the notes live
One document per process, linked from the tracker row, appended to. Not one document for the whole search, which becomes unnavigable, and not scattered notes in whatever app was open, which is the same as not writing them.
Newest entry at the top. Before any conversation, you re-read the page from the top and you’re current in ninety seconds. That ninety seconds is the entire return on the habit, and it’s what running several live processes at once depends on.
A caution about what not to write. Assume anything you type could be read by someone else eventually — a shared drive gets shared, a laptop gets returned, a screen gets glanced at. Keep the notes factual and professional. Record that the manager seemed stretched; don’t record a character assessment you’d be embarrassed to have surfaced. And keep other people’s personal details to what you actually need: a name, a work email, a role.
Also: the notes nobody takes
After a rejection. One line about what stage it ended at and anything they said about why. Over a search this accumulates into the most useful diagnostic you have — a pattern of rejections all at the same stage points at one specific problem, and you can only see the pattern if the stage was recorded. That column feeds directly into the review described in stopping rules for a job search.
After a good conversation that went nowhere. Who they were and what they seemed interested in. Roles reopen, people move companies, and a name attached to a real memory of a specific conversation is a live contact rather than a stranger.
After a call you cancelled or rescheduled, with the reason. Twice in one process is a pattern the other side is tracking even if you aren’t.
The habit, minimally
If eight fields is too much friction to sustain — and friction is what kills every tracking habit — cut it to three and keep doing it forever:
- What did they say about the timeline?
- What’s the next step and whose move is it?
- One thing I learned about the role.
Thirty seconds. That version still catches the two failures that actually cost you something: following up at the wrong time, and arriving at a conversation having visibly forgotten the last one.