The interview ends, the relief hits, and most people do nothing with the next thirty minutes.
That is the window where your memory of the conversation is at its sharpest it will ever be. An hour later it is already blurring. A week later, when you are prepping for the next round with the same company, it is mostly gone.
The debrief, within thirty minutes
Five minutes, written down:
- Every question I was asked, as close to verbatim as I can manage
- Which answers landed and which did not — usually obvious from their reaction
- Anything I said I would follow up on
- What I learned about the role that I did not know before
- Names and roles of everyone I spoke to This pays off three ways. It preps you for the next round with the same company, where questions frequently build on the last. It surfaces patterns across companies — if three interviewers have now asked about a gap in your experience, that is data. And if this one does not work out, you have a rehearsal record for the next one.
I keep these in one file per company. It has never once felt like wasted effort.
The follow-up note
Send it within twenty-four hours. Short. And make it carry something.
A generic thank-you note is fine and forgettable. A note that adds a piece of information is a second, smaller impression.
Hi [Name],
Thanks for the conversation today — the detail about the pipeline migration being mid-flight was genuinely useful context.
One thing I did not mention: you asked about handling schema changes across services, and I gave you the versioning answer. The fuller version is that we also ran a two-week dual-write period before cutting over, which is what actually made it safe. Happy to walk through it if useful.
Looking forward to hearing about next steps.
[You]
What that does: references something specific from the conversation, repairs an answer that was thinner than it should have been, and closes without pressure.
The middle paragraph is the valuable part. Everyone leaves an interview knowing one answer they gave badly. The note is a free second attempt at exactly one of them. Pick the one that mattered most and fix it in three sentences.
Send it to each interviewer separately if you have their addresses. Do not send an identical block of text to four people who will compare notes.
Then you wait, and it takes longer than they said
Hiring timelines slip. Almost always. Usually for reasons that have nothing to do with you — a competing candidate is mid-process, the hiring manager is on leave, the panel cannot get a slot to sync.
What silence rarely means is rejection. Companies are generally faster at rejecting than at approving.
My cadence:
| When | Action |
|---|---|
| They gave a date | Wait until two days past it |
| No date given | Wait one week |
| First follow-up | Short, warm, one line asking about timeline |
| Second follow-up | One week later, and that is the last one |
| After that | Assume no, keep applying, be delighted if wrong |
Two follow-ups is the ceiling. Beyond that you are not demonstrating enthusiasm, you are demonstrating that you do not read signals.
Critically: keep interviewing while you wait. A pipeline of one is the single worst negotiating position available, and it also makes waiting unbearable in a way that leaks into how you behave.
When money comes up
The question arrives early, often in the first screening call, and it is genuinely awkward.
If you can avoid naming a number first, do. The first number anchors the entire negotiation. Deflect once, politely:
"I'd rather understand the scope of the role first. What's the range you've budgeted for this position?"
Many companies will answer — in some places they are legally required to publish it. If they push back and you have to give something, give a researched range with a reason attached:
"Based on what I'm seeing for similar roles in this market, I'd be looking at somewhere between X and Y, depending on the overall package."
Do your homework before this conversation, not during it. Levels.fyi, Glassdoor, AmbitionBox, and people you know in similar roles — triangulate rather than trusting one source.
Negotiating the offer
An offer means they have chosen you. Internally, the decision is made, approvals are done, and restarting the search is expensive for them. A polite negotiation does not lose you an offer. Rudeness or bad faith might; asking will not.
What works:
- Ask once, clearly, with a number. "Would you be able to do X?" is far better than hinting at dissatisfaction and hoping.
- Give a reason. Market data, a competing offer, the scope of the role. Reasons make it a discussion instead of a demand.
- Negotiate the whole package. If base salary is genuinely capped, joining bonus, equity, notice period, start date, remote days, and title are all real currency.
- Do not invent a competing offer. Sometimes it gets called, and the offer does not survive being called.
- Get it in writing before you resign anything. Verbal agreements evaporate when the person who made them changes jobs. Then say yes or no properly. If you decline, decline warmly and specifically — the industry is small, and the person you turn down this year is on a panel somewhere in three years.
And if it is a no
Ask for feedback once. Most companies decline to give it for legal reasons, but the ones that do provide it hand you something genuinely valuable.
Then go back to your debrief notes and read what you wrote about the answers that did not land. That file is the most useful preparation material you own, and it only exists if you spent five minutes writing it while it was fresh.
The rest of the loop starts again from the top — the checklist, and, if the pipeline is thin, the part where recruiters find you before you apply.