Skip to content
Vera
Interview Prep

Silence is what fails coding interviews.

Practice narrating your approach, asking clarifying questions, and recovering from a wrong start.

You solve it, quietly, and the interviewer writes "poor communication."

What Vera actually is

A phone call with someone who is not there. You say the thing out loud, they answer the way a real person would, and you get to do it again — as many times as it takes, with nobody listening.

1She calls youA real phone call, about ten seconds after you tap. Lock screen, headphones, car — wherever you take calls.
2She plays the other personNot a coach reading tips. Thinking Out Loud in Coding Interviews, with someone on the other end who answers back.
3She pushes when you are vagueFollow-up questions, interruptions when you ramble, and a straight read at the end on what landed.
Practice Thinking Aloud

15 minutes free · no card needed

Practice Thinking Aloud

15 minutes free · no card needed

“What if I am bad at it?”Everyone is, on the first one. That is the entire reason it happens here and not there.
“What if I do not know what to say?”She asks first and follows up on whatever you answer. You never start from a blank page.
“What if it is awkward?”It is, for about twenty seconds. Then it is a conversation, and nobody heard the twenty seconds.

Not practising doesn’t save you anything.

The ticket, the evening, the weeks of applying — all of it is spent before anyone says a word. The practice is the only cheap part, and the only part that changes how the rest goes.

Practice Thinking Aloud

15 minutes free · no card needed

What she'll actually ask

She asks these the way a real person would, then follows up on whatever you say.

  1. Before you code, what would you ask me about this problem?
  2. Talk me through your approach before you write anything.
  3. That approach will not work for this input. What now?
  4. What is the complexity, and where is the bottleneck?
  5. How would you test this?
More about this one

Plenty of candidates solve the problem and still fail the round, because coding interviews grade whether the interviewer could follow your reasoning. Narrating while thinking is a separate skill from solving, and grinding problems alone actively trains the opposite habit. Vera runs verbal practice: you talk through an approach, get interrupted, hit a dead end, and practice saying so out loud instead of going quiet for four minutes.

What she listens for

Silence gapsLong pauses where the interviewer cannot tell if you are stuck or thinking.
Clarification before codeWhether you establish constraints or assume them.
Graceful dead ends"This does not handle duplicates, let me reconsider" scores better than quiet backtracking.
  • time complexity
  • edge case
  • brute force baseline
  • clarifying question
  • dry run
  • test case
  • optimization pass
  • interviewer hint
“Vera cut in with 'what are you thinking?' and I realized I had been silent for most of a minute. That was the whole problem.”
Dev A., New Grad Engineer

Related practice

Common questions

Can I actually write code on the call?

No, and that is deliberate. This page trains the narration half; use a coding platform for the editor half.

Does this help with pair programming interviews?

Considerably. Pair rounds are graded almost entirely on collaboration and narration.

What if I go blank?

Practice saying that out loud. "I need a second to think" is a legitimate move and it sounds far better than silence.

What if I am bad at it?

Everyone is, on the first one. That is the entire reason it happens here and not there.

What if I do not know what to say?

She asks the first question and follows up on whatever you answer. You never start from a blank page.

What if it is awkward?

It is, for about twenty seconds. Then it is a conversation, and nobody heard the twenty seconds.

Ready to try it?

Your first 15 minutes are free. No card required.