When a Coffee Chat Becomes an Interview

I've had hundreds of coffee chats. The vast majority unfolded exactly the way you'd expect: small talk, my introduction, their introduction, a back-and-forth conversation, a few recruiting questions at the end. Pleasant, low-stakes, forgettable in the best way.

And then there were three that weren't.

One was with UBS, where I was grilled on LBOs for the fifteen minutes following the "tell me about yourself" exchange. Another was with BofA, where an employee asked me about the three deals on my resume. The last was with KKR, where I was networking for a position within their Reinsurance Private Equity group and ended up discussing a deal on my resume with an Associate for about ten minutes. None of those three gave me any warning. I signed up for what I thought was a casual conversation and walked into something that was quietly grading me from the first sentence.

That's what this piece is about: the coffee chat that turns out to be an interview. How to recognize when it's happening, how to read the signs correctly (because the most important one is the opposite of scary), and how to handle the moment without unraveling. If you take one thing away, let it be this: being tested in a coffee chat is not a threat. It usually means you're being taken seriously.

What an "Evaluative" Coffee Chat Actually Is

Most coffee chats are exactly what they look like. You're networking, the other person is sharing their experience, and the real evaluation happens later, in a structured first round. But for ultra-competitive processes, where more candidates are networking than there are first-round interview slots, firms will often conduct "evaluative" coffee chats that double as interviews.

Think about the logic from the firm's side. If forty strong applicants have all networked their way into the funnel and there are only fifteen first-round slots, the firm needs a way to cut the field before the official process even begins. The coffee chat is a convenient place to do it. It's already on the calendar. It already involves a real employee talking to a real candidate. So they let that conversation carry weight. The chat stops being a chat and starts being a filter.

You'll never see this on a schedule. No one emails you to say "by the way, this one counts." That's precisely what makes evaluative chats unnerving, and it's why preparation can't be selective.

You Can't Tell in Advance, So You Prepare for Every One

Here is the central, slightly uncomfortable truth: it's impossible to determine whether a chat will be evaluative until you're already on the call. There's no reliable tell in the invitation, the calendar slot, or the person's title. The UBS chat looked identical to a dozen others I'd had that week, right up until the LBO questions started.

The good news is that this doesn't actually demand anything exotic from you, because there isn't any difference in preparing for these chats versus preparing for interviews. You've heard this advice a hundred times and it's still true: the best way to make sure you don't get caught flat-footed in an evaluative coffee chat is to prepare early. If you walk into every single chat interview-ready, the evaluative ones lose their power to ambush you. You don't need to predict which chats are tests. You need to make the question irrelevant.

The Signals: How an Evaluative Chat Reveals Itself

You can't predict an evaluative chat, but you can recognize one once you're inside it. There are two main flavors, and they feel quite different.

A technical question gets thrown your way

The first signal is the one that scares people most and should scare them least. It's very rare that you'll get asked technicals on a coffee chat, and if you do, take it as a good sign. They only evaluate candidates who look like they deserve to get a first-round interview.

I chose the word "look" deliberately a moment ago. There are two conditions a candidate has to satisfy. One is to look like they deserve a first-round interview, which is mostly your resume doing the talking before you ever speak. The other is to sound like they deserve it, and that second condition is exactly what the coffee chat is testing. The technical question is just the firm collecting evidence on whether the way you actually think and talk matches the candidate your resume promised.

HR is driving, questioning, and evaluating you

The second flavor is structural rather than accidental. Some firms lean heavily on HR for their first round. Bank of America, for example, runs its first-round interviews as group coffee chats conducted by someone from HR. That stands in contrast to a firm like Moelis, whose first rounds are always carried out by Analysts and Associates.

The reason this matters for our subject is that an HR-run chat is evaluative by design, not by surprise. If you discover (usually from an Analyst or past intern) that HR is integral to a firm's process, you should absolutely still reach out for that chat. But go in clear-eyed: they will drive the conversation, actively ask you questions, and, most worryingly, evaluate your candidacy from start to finish. It's relatively easy to get one of these chats. Impressing your way to a referral through one is a different story. The whole thing is a screen wearing the clothes of a conversation.

The Reframe That Makes This Land: Look vs. Sound

Let me make the "look versus sound" distinction concrete, because it's the idea that should be sitting underneath everything else here.

Your resume gets you in the door. It's what makes you look like someone who belongs in a first round. But a resume is a static document, and the firm has learned the hard way that an impressive piece of paper doesn't always come attached to an impressive person. So they use a live conversation to check the second condition: do you sound like the candidate this resume describes? Can you talk about your own deals coherently? Do you fold under a mild technical question? Do you carry yourself like a future colleague or like a nervous applicant who memorized some lines?

What "Ready" Actually Means

So what do you keep within arm's reach, given that any chat might quietly become an interview? Here's the short, interview-question-specific set of materials I'd have open before any coffee chat:

• Pre-written Behavioral Answers (TMAY, Why this role?, S & W, etc.)

• Scripted Deal Walkthroughs & Stock Pitches (the ones on your resume)

• Your Resume

• Ibvine.io (select "ALL" and put on "List View" for Ctrl + F accessibility)

A line on each, since the goal here is readiness, not a full prep course.

Behavioral. Have your core answers written and rehearsed, not improvised. "Tell me about yourself," "Why this role," strengths and weaknesses, and the usual variations should already exist as polished scripts you can deliver without reaching. The deep work of constructing these answers belongs to your broader behavioral prep, but for our purposes, the point is simply that they should already be done before you ever dial in.

Technical. This is what ibvine.io is for. I used it instead of a combined PDF of all the BIWS guides, because when I tried searching one giant PDF, there were too many mentions of any given keyword to allow for effective Ctrl+F-ing. Keeping a clean, searchable technical reference open in List view means you can stay focused on the chat itself rather than listening anxiously for a technical question to surface. The reference is there if you need it. Most chats, you won't.

Resume and deals. Know every line of your own resume cold, especially the deals. The BofA and KKR chats I mentioned were both, at bottom, resume conversations. An employee picked something off my resume and went deep. If you can't walk through your own experience fluently, no amount of technical study will save you, because the most natural question any evaluator asks is simply, "Tell me about this deal."

Handling the Moment

Let's say it happens. You're ten minutes into what felt like a friendly conversation and the person asks, out of nowhere, "Quick one for you, can you walk me through how you'd think about an LBO?" Or, "Take me through the second deal on your resume."

The single most useful thing you can do is also the simplest: don't fret, and breathe. If they ask you a behavioral, technical, or other unexpected question, whether it's because they genuinely want to know you or because they're evaluating you, it's a good sign that they did. You'll feel an enormous pull to get an answer out immediately, to fill the silence. Resist it. Take one to three seconds to breathe before you speak. Any "awkward" pause that results from this won't actually register as awkward unless you stretch it past four seconds, and the gain in coherence and clarity is well worth those couple of beats.

Here's roughly how that plays out (a hypothetical, to show the shape of it):

Them: "Actually, before we move on, walk me through the third deal on your resume."

You: [one or two seconds, a breath] "Sure, happy to. So this was a sell-side process for a mid-market industrials business..."

That pause did real work. It bought you a moment to recall the deal's structure, decide where to start, and deliver a clean answer instead of a frantic one. Then, once you've given an interview-grade response, you let the conversation settle back into chat mode. You don't keep performing. You answer well, and you return to being a person having a conversation.

A note on what this section is not. If you freeze up entirely, or you flub a question and need to recover mid-chat, those are real situations with their own playbooks, and I cover them elsewhere. Here, the point is narrower and more hopeful: a single unexpected question is not a freeze. It's a beat. Breathe, answer, continue.

The Proof

I want to come back to where we started, because those three chats are the entire case for taking this seriously. Across all my recruiting, these evaluative chats were genuinely rare. Personally, I've only had three chats where I was asked interview questions.

Three out of hundreds. The odds that any given chat flips into an interview are low. But "rare" is not "never," and you don't get to know in advance which one it'll be. The UBS chat didn't announce itself. It just quietly turned into fifteen minutes of LBO questions, and if I hadn't been ready, that conversation, and probably that opportunity, would have ended very differently.

That's the whole game. Prepare for every chat as though it might be the one that counts, recognize the signals when they appear, read a technical question as the compliment it usually is, and when the moment comes, breathe before you answer. Do that, and the chat that becomes an interview stops being the thing you fear and becomes the thing you were quietly hoping for all along.