You know the concept. You solved the problem on paper. But the moment the interviewer says
"explain your approach," your mind goes blank and the English just won't come. If this is
you, please breathe. You are not weak at the subject. You are only nervous about speaking
it. The good news is that the technical round needs simple, clear English, not fancy English.
Short sentences win here. The interviewer wants to follow your thinking. In this guide you
will get easy phrases and mini-scripts to explain code and concepts without freezing.
Quick answer: In a technical round, speak in short, plain sentences. Explain your
approach step by step before jumping to code. Say what you are doing as you do it. If you
are unsure, say so honestly and reason out loud. Clear thinking beats perfect grammar
every time. Practice talking through one problem daily, out loud.
How do I explain my approach before I start coding?
Interviewers love when you talk before you type. It shows you think first. Use a simple
three-part frame: what, how, why.
"So the problem is asking me to find duplicates in an array. (what) My approach is to use
a hash set, because lookups are fast. (how) This way I check each element only once, so
it stays efficient. (why)"
That is enough. You do not need long words. You only need order.
A ready opening template:
"Let me first understand the problem. We need to ____. I think a good approach is ____,
because ____. Let me walk you through it step by step."
Saying "step by step" is powerful. It buys you time and sets a calm pace. It also tells the
interviewer you are organised, even if your English is simple.
What do I say while I am actually writing code?
Silence feels awkward, and a blank face makes you look stuck even when you are not. So narrate
gently. You do not need to explain every line. Just mark the important moments.
"Okay, here I am creating a loop to go through the list."
"Now I am storing each value in the set."
"Finally, I am checking if the value already exists."
Useful linking phrases:
- "First, I will... then I will..."
- "The reason I am doing this is..."
- "Let me handle the edge case where the list is empty."
If you make a small error and notice it, just say it calmly:
"Oh, I think I missed a condition here. Let me fix that."
Catching your own mistake out loud is a good sign, not a bad one. It shows you can debug.
How do I answer a concept question without rambling?
For theory questions like "What is the difference between a stack and a queue?", answer
first, then give one example. Do not start with a long story.
"A stack is last-in, first-out. A queue is first-in, first-out. For example, a stack is
like a pile of plates, and a queue is like a line at a counter."
That is a full, clear answer in three short sentences. Answer-first, example-second. Keep it
tight.
Template for any concept question:
"In simple terms, ____. The main difference is ____. A real example would be ____."
What if I do not know the answer?
This happens to everyone. The wrong move is to go quiet or to guess wildly. The right move is
to stay honest and show your thinking.
"I am not fully sure about this one, but let me reason through it. I think it might work
like ____ because ____."
Or, if you truly have no idea:
"I haven't worked with that yet, but I would love to learn it. Based on what I know, I would
start by ____."
Interviewers often value honesty and reasoning more than a memorised answer. You are showing
how you handle the unknown, which is a real workplace skill.
Say this, not that
❌ "I don't know." (and then silence)
✅ "I am not certain, but let me reason it out."
❌ "Umm... actually... like... you know..." (filler while frozen)
✅ "Let me think for a second." (then pause calmly)
❌ (typing fast in total silence)
✅ "Let me walk you through what I am doing here."
❌ "It is very very simple, basically the thing is..." (vague rambling)
✅ "In short, it works like this: ____."
How do I adjust for different interviewers and rounds?
Not every technical round is the same, so tune your style a little.
- Fast, sharp interviewer: Keep narration shorter. Give the approach in one line, then
code. "My plan is a hash map. Let me code it." - Friendly, patient interviewer: Explain a bit more and invite them in. "Does this
approach sound right to you, or should I consider another one?" - Online / coding-platform round: Speak clearly and slightly slower; audio can lag.
Confirm they can hear you: "Can you see my screen clearly?" - Viva or oral round (no coding): Lean on the what–how–why frame and real examples,
since you cannot show code.
Reading the room is a soft skill that makes your English feel natural, not robotic.
Say it out loud (2-minute practice)
Pick one easy problem you already solved. Then run this drill:
- Set a timer for two minutes. Open your phone voice recorder.
- State the problem in one sentence: "This problem asks me to ____."
- Give your approach using what–how–why: "My approach is ____, because ____."
- Narrate three steps as if coding: "First... then... finally..."
- Play it back. Did you sound clear? Were sentences short? Were there long silences?
- Repeat once more, smoother this time.
Do this daily with one new problem. In two weeks, the words will start coming on their own.
For a structured plan to build this speaking habit, the
FirstWords English speaking course gives you
guided daily drills made for exactly this fear.
A quick word on the fear
That frozen feeling is not a sign you are bad at coding. It is just your brain protecting you
under pressure. Everyone feels it at first. The cure is not more grammar. The cure is more
mouth practice. Every time you explain a problem out loud, the fear gets a little smaller.
Communication matters more than perfection. You only have to be clear, not flawless.
Mini-FAQ
Should I speak in English the whole time even if I struggle?
Yes, keep going in simple English. A clear short sentence beats a perfect one you never say.
Practice makes it smooth.
What if my accent is strong?
Accent is fine. Clarity is what matters. Slow down a little and pronounce key technical words
carefully. The interviewer cares about meaning.
Is it okay to ask the interviewer to repeat the question?
Absolutely. Say "Could you please repeat that?" It shows you want to understand correctly,
which is professional, not weak.
How early should I start practising speaking?
Today. Even five minutes of out-loud explaining each day builds a huge difference by
placement season.
Your next step
You do not need perfect English for the technical round. You need clear, calm, simple
sentences and a little daily practice. Start with one problem out loud today, and build from
there. If you want a gentle, step-by-step way to practise speaking without judgment, explore
the FirstWords English speaking course and take
it one small drill at a time.
Keep going with these next: