Sending a hiring-loop debrief to your partner

A debrief that reads like a story forces the hiring partner to guess what you actually recommend. Separate what the candidate said from what you inferred, and close with a hire / more loop / no.

3 min read

The loop is over. Your hiring partner did not sit in the room. They ask what you thought. The draft that comes out is a recap of the hour in the order it happened, ending with "overall pretty good?" They now have to hold a meeting to recover a decision you already made in your head.

A debrief is a decision request, not a story.

Close the recommendation first

Hire. Another named loop. Or no.

If you cannot pick one, you are not ready to debrief. You are asking the partner to watch the tape with you. That can be the right next step — then ask for that, and say which thirty minutes of the loop, and what question those minutes are supposed to answer.

"I recommend no. I would flip to another loop, with Priya, if you read the system-design answers as a nerves problem rather than a missing model. I would not flip to hire on this packet alone."

The disconfirmer is the useful half. It tells them where their judgment still matters.

Quotes in one block, inferences in another

"They struggled with ownership" is a conclusion. "When I asked who decided the last outage response, they said the manager always does that" is what happened. A partner will vote differently depending on which they are reading.

State the inference as an assumption someone can reject: "I am treating that answer as a missing ownership model, not as interview nerves." If the partner has the opposite read, the rest of your packet can still stand.

Do not let an assistant merge the two. A session recap will happily turn your mood about the last ten minutes into a trait of the candidate. Provenance labels exist so a note you stand behind is marked as yours, and a guess the model made is marked as a guess. A hiring packet is a bad place for the second kind to arrive unlabelled.

Two or three quotes is enough. Pick the ones that carried the score, not the ones that were vivid.

What you were scoring

A partner who was not in the room needs the rubric in one short list. Design. Communication. The specific risk this role carries. Without that, they will score the debrief as a vibe.

Say what you did not cover, too. A glowing note on a loop that never touched the on-call path is a hole, not a yes.

Send the packet, not the chat

You do not need a shared hiring workspace. A briefing carries the ask, the quotes, the labelled reads, and the default: "If I have not heard by Wednesday 15:00 UTC I will treat this as a no and release the candidate." That default is kinder than a silent hold.

If the partner has an account, you need an accepted contact. If they do not, they get email and a page. You approve what goes out. There are no attachments, so link the score sheet and put the quotes that carry the score in the brief.

If the hour is still in a session, connect your assistant and have it pull the quotes before it writes the conclusion.

Frequently asked questions

What should a hiring debrief to a partner include?
What you were scoring, two or three quoted moments from the loop, what you inferred from those moments, and a closed recommendation: hire, another specific loop, or no. A narrative of how the hour felt is not a recommendation.
How do you keep a hunch from becoming a fact about a candidate?
Put quotes in one block and conclusions in another. A sentence like they seemed checked out is a conclusion. The quote that produced it should sit next to it, or the next reader cannot test it.
What if the partner and I used different assistants in the loop?
Send a briefing rather than a transcript. Their assistant has none of your session. The package should carry the scored moments and the ask, not the chat you had with yourself afterward.