Phone and Video Case Interviews: How to Verbalize When Notes Are Invisible

Phone and video case interviews test the same consulting skills as in-person cases: structured thinking, quantitative analysis, clear communication, and practical judgment. The format does not make the case easier. It makes weak communication more visible. When the interviewer cannot see your scratch paper, read your body language, or follow your pen across an issue tree, everything has to travel through your voice.

The scoring bar and the clock are nearly identical to an in-person session: a typical virtual case runs 45 to 55 minutes total, with 25 to 35 minutes of actual casework and the rest on fit and logistics. No calculator. The medium is the only real variable. This guide is about winning that variable: how to verbalize structure, math, and exhibits so a remote interviewer can audit your reasoning in real time.

If you need the technical depth (microphone and webcam recommendations, eye-contact mechanics, Zoom whiteboard alternatives, and the AI-note-taker rules firms now enforce), read the dedicated virtual case interview setup guide. This page is the communication operating manual that sits on top of that setup, with a specific focus on the phone format where you get no video signal at all.

How is a phone or video case different from in-person?

The casework is familiar: clarify the objective, build a structure, request data, run the numbers, interpret exhibits, and recommend an action. What changes is the channel. Crafting Cases frames three differences between remote and in-person cases: the technical setup (audio and video quality), the communication burden (the interviewer cannot see your written work), and the harder job of building human connection through a screen.

The practical rule: make your thinking inspectable. A virtual case should sound like a well-run problem-solving meeting, not a candidate silently filling in a worksheet. On a phone case, where there is no video at all, this is the entire game. Your voice is the only instrument the interviewer has.

What should I test before the call?

Your technical setup should disappear into the background. Reboot your computer beforehand, test the exact link a full day early, and confirm audio and screen share so the first five minutes are not spent negotiating connection issues.

Checklist

Virtual case setup checklist

• Open the interview link 10 minutes early

  Confirms the platform loads before the interviewer joins

• Use wired earphones or a dedicated microphone

  Crafting Cases recommends wired earphones; mic proximity to your mouth matters more than camera polish

• Keep a charged phone nearby as a 4G backup

  A backup device prevents a small technical issue from ending the interview

• Prepare blank paper with large, legible handwriting

  Structure, math, and exhibits need separate space, and big ink stays readable if you hold it to the lens

• Close notifications, tabs, and distracting apps

  Interruptions break concentration and look avoidable

• Write down the recruiter backup contact details

  If the link fails, you can recover quickly without searching email

• Disable AI meeting assistants before joining

  An uninvited Otter.ai or Fireflies bot reads as an unauthorized recording and an integrity flag

Do not over-optimize the camera. A clean background, a straight-on eye line (stack books under your laptop), and reliable audio matter more than looking polished. Interviewers care whether they can follow your thinking, and bad audio is penalized harder than a soft webcam image.

How should I open the case?

Your opening should slow the conversation down and align on the business question before you build anything. Use this sequence:

1. Restate the objective in plain business language.
2. Ask one or two clarifying questions that affect the structure.
3. Ask for time to organize your thoughts.
4. Present a short issue tree with two or three branches.
5. Name the branch you want to test first and why.

Example:

"I want to confirm the objective. The client wants to decide whether to enter the premium pet-food market in Germany, and success means an attractive profit opportunity within three years. I have two clarifying questions before I structure this."

That opening signals control without sounding scripted, and it gives the interviewer an easy moment to correct your understanding before you build the wrong framework. For the full structuring method, see case structure vs. case framework, which explains why a tailored structure beats a memorized template.

How do I communicate math when my notes are invisible?

Silent math is the single biggest phone-case failure mode. The interviewer does not need every arithmetic step, but they do need to know what you are solving and why before you go quiet. Use this five-step script:

1. "I am calculating [business quantity]."
2. "The formula is [formula]."
3. "I will use [assumptions] and keep units in [units]."
4. "The result is approximately [answer]."
5. "The implication is [business meaning]."

Example:

"I am calculating annual revenue. Revenue equals customers times purchase frequency times average order value. Using 2 million customers, 6 purchases per year, and $25 per order, that gives about $300 million in annual revenue. That is large enough to be material, so I would next check margin and acquisition cost."

The five-step script does two things at once: it lets the interviewer catch a wrong assumption before you waste 90 seconds computing, and it converts a number into a recommendation rather than a dead end. For the underlying patterns, work through case interview formulas and drill speed with mental math for case interviews.

How do I handle exhibits on video (and on the phone)?

Video exhibits create two risks: reading too quickly and describing a chart without a conclusion. Treat every exhibit like a short client slide. The clean flow:

1. Ask for 20 to 30 seconds to read the exhibit.
2. Name what the exhibit shows.
3. Identify the most important pattern.
4. Translate the pattern into a business implication.
5. Ask or answer the next question.

Example:

"This chart compares revenue growth and margin by customer segment. The key pattern is that enterprise customers have slower growth but much higher margin. That suggests the client should not optimize for growth alone. I would test whether enterprise acquisition costs are low enough to justify prioritizing that segment."

Do not narrate every cell. The interviewer is testing judgment, not recitation. For the full reading method, see reading graphs and charts in case interviews.

When you need to show your own work (a structure or a calculation), there is a clear hierarchy of options. Victor Cheng ranks them from best to worst: a clipboard you describe verbally and hold up periodically; a digital whiteboard for the issue tree with paper kept for computations; a document camera ($100 to $300) mounted over your notepad; and screen sharing, which he calls the least preferred because it splits the interviewer's attention. On a phone case none of these exist, so explicit verbal signposting is the only tool you have.

How do I make my structure audible without showing it?

Two habits make an invisible structure easy to follow. First, declare the count before you list: "I have three branches I want to look at," then name each. Second, use explicit language instead of implicit references: say "let's move on to the second branch, customer acquisition cost" rather than just "the second bucket." Crafting Cases calls this the difference between speaking explicitly and forcing the interviewer to reconstruct your map from memory.

If you are on video with a high-resolution webcam, you can briefly hold your paper structure to the lens, or offer to send a photo of it. On the phone, lean entirely on numbered signposting and frequent alignment checks: "Does that structure make sense before I dig into the first branch?" These check-ins replace the body-language confirmation you would get in a room. For more on this, see case interview communication tips.

What does virtual presence actually require?

Presence in a virtual case is mostly about reducing friction for the listener. On video, flat delivery reads as disengagement even when the content is strong, so add vocal variety and slow down.

Do:

• Speak 10-15% slower than feels natural.
• Pause after each branch before moving on.
• Use numbered transitions: "first," "second," "third."
• Check alignment after major pivots.
• Look at the camera lens when delivering the final recommendation.

Avoid:

• Talking while typing loudly.
• Filling every pause with "so" or "um."
• Apologizing repeatedly for normal thinking time.
• Looking at a second monitor while the interviewer is speaking.
• Turning a recommendation into a long recap.

If you need a pause, say it directly: "Let me take 30 seconds to structure that." That sounds composed. Rushing to avoid silence usually sounds less confident. Research on conversation memory suggests the first and last couple of minutes are the most memorable, so invest your warmth there: a genuine greeting at the start and a confident, answer-first recommendation at the close.

What if the connection drops mid-case?

Connection trouble is not a disaster if you handle it like a consultant. Victor Cheng's guidance: when you detect packet loss or jitter, slow your speech so more of each sentence actually reaches the interviewer, and repeat key points ("as I mentioned earlier, my hypothesis is X"). For latency, pause deliberately and confirm the interviewer has finished speaking before you respond, so you do not talk over each other. If audio fails entirely, switch to your charged phone and dial in. One calm sentence ("I lost you for a moment, let me repeat my last point") is far better than pretending nothing happened.

How should I practice for phone and video cases?

Practicing a case over the phone with a friend is not the same as replicating your real remote environment. Use your actual interview setup: same room, same lighting, same audio, same note layout. Notre Dame's career office is blunt about this. Practice walking through your math out loud and explaining frameworks verbally without leaning on visual aids, because the interviewer will not have your notes.

Use full mock cases only after the component habits are stable.

Record two practice cases and review only the first eight minutes. Most virtual-case issues show up early: unclear objective, rambling structure, weak branch prioritization, or silent math. Fix one behavior per session. If you want unlimited reps without scheduling a partner, Road to Offer's interactive case practice drills let you rehearse the opening, structure, and math narration aloud and get feedback on whether your reasoning was followable, which is exactly what a remote interviewer is grading.

What are the most common phone and video case mistakes?

Treating virtual as easier. The format is more convenient, not easier. Your verbal structure has to be cleaner than it would be in a room.

Doing math silently. Short stretches of silence are fine, but the interviewer needs the formula and units before you go quiet, or your answer arrives with no audit trail.

Reading exhibits like a transcript. Name the chart, isolate the pattern, and state the implication. Skip the cell-by-cell readout.

Implicit signposting. "The second one" forces the interviewer to rebuild your structure from memory. Name each branch every time you reference it.

Over-apologizing for setup issues. If something breaks, solve it calmly and move on. One concise apology is enough.

Forgetting the recommendation. End with the answer first, then the two or three supporting reasons, then the risk or next step.

For a broader checklist of what trips candidates up, see common case interview mistakes.

Sources and Further Reading (checked June 17, 2026)

• Crafting Cases - A guide to video conference case interviews
• Caseinterview.com - Case Interviews via Video Conference (Victor Cheng)
• My Consulting Offer - Virtual Case Interview
• University of Notre Dame - Virtual Case Tips
• McKinsey & Company - Interviewing
• Road to Offer - Virtual Case Interview Setup Guide