What if your English is slower than your coding?

Keep the commentary to one line per decision. Do not translate a paragraph in your head. “I will use a map. Time is linear.” is enough.

Does silence ever look like focus?

On a UK/US panel, long silence usually reads as being lost. Name the next step, then go quiet for ten seconds of typing if you need to.

Do I need an account to use this tool?

No. You get two scored recordings per hour without signing up. The clip is scored and discarded. Sign up only if you want more runs.

How to Think Out Loud in a Coding Interview in English

Think out loud in English by narrating decisions: first idea, one trade-off, why you chose this approach, and what you will check if you stall. Short sentences beat silence — interviewers cannot score reasoning they cannot hear.

The spoken order

1. First idea
Say the first solution that comes to mind.
Even if it is brute force. Silence reads as confusion. “My first instinct is …” buys you time and a score.
2. Trade-off
Name one advantage and one cost.
“This is simple but slow.” Interviewers hire the person who can see the second option, not the one who jumps to code.
3. Justify
Say why you are choosing this approach now.
Tie it to the constraint you just heard: input size, memory, or time. One sentence is enough.
4. If you are stuck
Name the blocker, then the next check.
“I am stuck on the empty-input case. I will write that first.” A bridging phrase beats a long pause.

Phrases you can steal

Opening

“Let me think out loud as I go — stop me if I am heading the wrong way.”
“My first instinct is a brute-force scan, then I will see if I can do better.”

While you work

“I am choosing a hash map so I can look up the complement in constant time.”
“The trade-off is extra memory for a faster scan.”

If you go quiet

“I am checking the empty-input case, then I will come back to the loop.”
“I am stuck on whether the array is sorted. Can I assume that?”

Practise out loud

The interviewer has just given you a coding problem. Do not solve it on paper. In 60–90 seconds, narrate how you would start: first idea, a trade-off, why you would choose that approach, and what you would say if you got stuck.

Record 60–90 seconds. Play it back, then get a scorecard. Audio is scored and discarded.

This browser cannot record audio. Type your explanation below.

0:00 / 1:30

Model spoken script

Let me think out loud as I go. My first instinct is a brute-force pair check so I can confirm the logic. That is correct but slow, so I would switch to a hash map if the input is large. I am choosing the map because I need a fast lookup, and I can afford the extra memory. If I get stuck I will write the empty-array case first, then come back to the loop.

FAQ

Questions

Narrate decisions in short sentences: first idea, trade-off, why this approach, then the next check if you stall. A bridging phrase is better than a pause.

More questions? Email us at contact@mocklyenglish.com.

Course: How to explain your thoughts · Explain a LeetCode solution

Quick answer

Think out loud in English by narrating decisions: first idea, one trade-off, why you chose this approach, and what you will check if you stall. Short sentences beat silence.

Related in this path

People like you