How to Think Out Loud in English in a Technical Interview
Think out loud in English by narrating decisions: approach, data structure choice, and trade-offs—before and while you code. Short sentences beat silence; interviewers cannot score reasoning they cannot hear.
In a technical interview, the interviewer is not only interested in whether your solution is correct. They want to understand how you got there. Thinking out loud - explaining your reasoning as you work - is one of the most important skills you can develop for technical interviews.
In a technical interview, the interviewer is not only interested in whether your solution is correct. They want to understand how you got there. Thinking out loud - explaining your reasoning as you work - is one of the most important skills you can develop for technical interviews.
What to explain
You should explain almost everything you are thinking. This feels unnatural at first, but it is essential. Explain:
- What is the first solution that comes to mind
- What other approaches you considered
- Why you chose this approach instead of another
- What trade-offs you are aware of
- If you are stuck, which part is causing the problem
- Trade-off. When you accept one disadvantage in order to get an advantage. For example: a simpler solution is easier to understand but slower.
- Brute-force. A solution that tries every possible option to find the answer, without any optimisation.
- Optimised. A solution that has been improved to be faster, use less memory, or handle more data.
- High-level. A general overview of your approach, without going into technical details.
- Approach. The method or strategy you choose to solve a problem.
- Justify. To explain why you made a particular decision.
The structure
Think-aloud structure
- Initial idea — What is the first solution that comes to mind?
- Trade-offs — What are the advantages and disadvantages of this approach? What else could you do?
- Justify — Why are you choosing this approach?
- Next steps — What will you do next?
Model answers
- Initial idea. "OK, I will walk you through my thinking. First, I would group the data by region and product and count the number of purchases."
- Trade-off. "I am deciding between SQL and Python for this. Python with pandas gives more flexibility if I need to transform the data, but it could be slower for large volumes."
- Justify. "Since the data is already clean and stored in a database, SQL will be more efficient. I can run a GROUP BY and COUNT directly on the server."
- Next steps. "My approach will be: group by region and product, count purchases, sort, and then use a window function to find the top product per region. Does that sound right?"
Useful phrases
Starting your explanation
- "I will walk you through my thinking."
- "My first thought is to use [approach]."
- "I am thinking of starting with a simple brute-force solution."
Comparing approaches
- "I am debating between [option A] and [option B]."
- "Another option would be to use [approach] - the advantage is [benefit], but the trade-off is [cost]."
- "Instead of [approach A], I could [approach B], which would be more efficient."
Justifying your choice
- "Given that [reason], I will go with [approach]."
- "Since [constraint or context], this seems like the better option."
- "I am choosing this because [reason] - the trade-off is acceptable here."
Checkpoints
- "Does that direction sound right before I go deeper?"
- "Does that make sense so far?"
- "That is the high-level view - would you like more detail on any part?"
Get started
Create a free account
Track your progress, complete exercises, and prepare your own interview answers.
No credit card needed
FAQ
Questions
More questions? Email us at contact@mocklyenglish.com.
See it in practice
All case studies →How a Java Engineer New to London Prepared System Design English
A Java backend engineer who moved from Korea to London prepared system design and live-coding English - vocabulary, phrases and structure first.
Read storyHow a Backend Engineer in Sydney Prepared for Microsoft in English
A Sydney backend engineer from China prepared Microsoft competency stories and system design in English: outages, metrics, AI agents. No offer claimed.
Read storyRelated in this path
People like you
Practise in the course
Think out loud for 90 seconds