McKnight Lab All articles
Lab Culture

Ninety Minutes and a Decision: Behind the Curtain of a Postdoc Interview at McKnight Lab

McKnight Lab
Ninety Minutes and a Decision: Behind the Curtain of a Postdoc Interview at McKnight Lab

Most accounts of academic hiring are written from the chair closest to the door—the candidate's chair. What follows is the other perspective. Over the past six years, our lab has interviewed twenty-three postdoctoral applicants, and we have gradually turned what was once an improvised ritual into a deliberate, documented process. We are publishing it here because we believe search committees benefit from comparison as much as applicants do.

The Ninety Minutes Before the Candidate Arrives

The formal interview begins at a scheduled time, but the real one starts an hour and a half earlier. That is when the entire lab gathers for what we informally call the huddle—a fifteen-minute meeting in the conference room with the door closed and the coffee still brewing.

The agenda is short. First, whoever hosted the candidate's dinner the previous evening reports on the conversation, scrubbed of anything the applicant would reasonably consider private. We are interested in signals: Did they ask about the science of people they had never met? Did they treat the graduate student who drove them from the hotel with the same attention they gave the PI? Second, each member of the lab states one question they intend to ask. This prevents the dreaded phenomenon of four people independently asking about five-year plans.

Finally, the PI reminds everyone of the lab's only hard rule: every voice in the debrief carries equal weight. A first-year rotation student's read on the candidate counts the same as a senior scientist's. We adopted this after realizing, in an audit of our own past hiring, that our most prescient concerns had repeatedly come from junior members who stayed quiet in mixed-rank discussions.

The Channel Nobody But Us Can See

Years ago, we created a private messaging channel that exists solely for real-time interview observations. It is deliberately anonymous—posts are made without attribution, and the channel is archived and read only after the candidate has left campus.

The channel solves a problem every search committee recognizes: the person who notices something uncomfortable but does not want to be the one to say it in a room where the candidate might one day sit. A note that the applicant interrupted the same undergraduate three times during the tour. A genuinely elegant answer to a technical question about cryo-EM sample preparation. Both go into the same stream, unattributed, and both resurface in the debrief.

We are candid that this system could be abused in the wrong hands, so it comes with guardrails. No comments on appearance, accent, or family status—ever. Observations must be behavioral and job-relevant. The PI reviews the archive before the debrief and strikes anything that violates those terms.

The Dinner Is Part of the Interview, and We Say So

We have stopped pretending the pre-visit dinner is casual. Our candidates are told plainly, in the invitation email, that the dinner is informal in setting but not in purpose, that no one is evaluating their restaurant manners, and that the point is for both sides to ask the questions a seminar room does not permit.

This honesty changes the dynamic. Applicants relax. They ask about funding timelines, parenting during a postdoc, what happened to the last two people who held the position. We would rather answer those questions before an offer than after a resignation.

Red Flags We Have Learned to Spot

Six years of debrief notes have taught us to watch for a handful of patterns, none of which appear on any CV:

None of these is disqualifying alone. Two or more, consistently, has historically predicted a rough postdoc.

The Debrief Happens Within Twenty-Four Hours

We do not let interviews linger. The morning after the visit, the lab meets for thirty minutes. The channel archive is read aloud, the huddle questions are revisited, and every member submits a one-line assessment before discussion begins—written first, so early speakers do not anchor the room.

The output is a decision or, failing that, a specific list of what additional information would produce one. "We should think about it more" is banned. Vagueness, we have learned, is how excellent candidates end up in someone else's lab while a committee deliberates.

Why We Bother Writing This Down

Applicants deserve to know what the other side of the table is doing, and committees deserve better than inherited habit. Our process is not the only defensible one, but it is ours, it is written, and it improves every year—usually because a candidate taught us something we did not know to ask.

All Articles

Related Articles

Fifteen Years, One Bench: The Case for Building a Career Where the Science Lives

Fifteen Years, One Bench: The Case for Building a Career Where the Science Lives

Reading Our Own Rejections Out Loud: The Lab Meeting Where Nobody Wins

Reading Our Own Rejections Out Loud: The Lab Meeting Where Nobody Wins

The Person Behind the Pipette: Why Our Sequencing Rescue Belongs in the Acknowledgments—and the Author List

The Person Behind the Pipette: Why Our Sequencing Rescue Belongs in the Acknowledgments—and the Author List