How to pass a technical interview in English (even when your English freezes)

To pass a technical interview in English when your English freezes, do three things: script your first 90 seconds word-for-word, answer behavioural questions with a STAR structure, and rehearse out loud daily for 15 minutes with Fluento AI. The freeze is not a knowledge problem — it is a retrieval-under-pressure problem.

Ten years of coaching Indian engineers through Infosys, TCS, Wipro, Accenture, Cognizant, and lateral interviews at Flipkart and Razorpay has taught me one thing: the people who fail are almost never the ones who don't know the answer. They are the ones who know the answer in Hindi but can't retrieve it in English fast enough. This guide fixes that.

Why smart Indian engineers freeze

Your brain runs two tracks when stressed: content retrieval (the answer) and language encoding (saying it in English). When stress is high, your brain shunts resources to retrieval and borrows from language. The result is the classic freeze: you know the answer but cannot say it.

The fix is counter-intuitive. You don't need more technical prep. You need to make the English encoding so automatic that it doesn't compete with retrieval. This is exactly what daily spoken practice with Fluento AI does — it moves English from "active effort" to "muscle memory".

Step 1 — Script the first 90 seconds

Every interview opens with "tell me about yourself". Write and memorise 120–150 words. Yes, memorise. Yes, it will sound "scripted" — that's fine, everyone's does, and it buys you 90 seconds to warm up your English circuitry.

Template (a Mumbai engineer example):

"Hi, I'm Arjun. I'm a final-year Computer Engineering student at VJTI Mumbai with a CGPA of 8.4.

Over the past two years, I've worked on three projects that shaped my interest in backend systems. My most recent one was a real-time chat app built with Node.js and Redis for 500 concurrent users — it taught me how WebSockets and pub-sub scale.

I've also interned at a fintech startup where I reduced API latency by 40% by adding Redis caching. Outside coursework, I solve DSA on LeetCode — currently 400 problems and a Knight badge.

I'm applying to Infosys because the scale of distributed systems and the mentorship culture you've built fit exactly what I want to grow into. Happy to answer any questions."

Notice: specific numbers (8.4, 500, 40%, 400), one concrete project, one internship, one outside-classroom signal, a reason for this company, a confident close. Practise this aloud 10 times before the interview. In Fluento AI, use the "Mock Interview with Rajesh" scenario — he will interrupt you exactly like a real interviewer.

Step 2 — STAR for every behavioural question

STAR = Situation, Task, Action, Result. Indian interviewees tend to jump straight to "Action", which leaves the interviewer confused about context. Force yourself through all four.

Step	What you say	Time
Situation	"In my third-semester OS project, our team of 4…"	15 sec
Task	"My job was to implement the page-replacement algorithm…"	10 sec
Action	"I chose LRU over FIFO because… I benchmarked on 3 workloads…"	45 sec
Result	"We hit 22% fewer page faults than the baseline and got an A."	15 sec

Total: ~90 seconds per answer. Longer sounds rambling, shorter sounds thin. Fluento AI measures your per-answer time and flags when you're running long.

Step 3 — The 6 common freezes and how to escape

1. "Can you repeat the question?" Always allowed. Buys 4 seconds.
2. "Let me think for a moment." Don't fill silence with "umm" — own the pause. 5 seconds of professional silence beats 5 seconds of "aah basically actually umm".
3. Mid-sentence freeze. Stop. Breathe. Say "let me rephrase that" and restart the sentence. Interviewers respect recovery more than fluency.
4. Technical word you forgot in English. Describe it: "the data structure that works like a queue but allows priority" = priority queue.
5. Switched to Hindi. Smile, say "sorry, in English", and continue. Do not apologise elaborately.
6. You don't know the answer. "Honestly, I haven't worked with that — here's how I'd approach learning it in a week." Strength, not weakness.

Step 4 — The 15-minute daily rehearsal

Starting 3 weeks before your interview, do this every day in Fluento AI:

• Monday: Mock Interview with Rajesh — full HR round, 15 minutes.
• Tuesday: Technical deep-dive — explain one project end-to-end out loud.
• Wednesday: Behavioural — "tell me about a conflict", "a failure", "a leadership moment".
• Thursday: Salary negotiation scenario (rare but critical for lateral hires).
• Friday: Replay your worst answer from Monday — redo it.
• Weekend: One day rest, one day free practice with Emily (casual) to keep your conversational English loose.

Sample answers to the 7 questions that always come up

1. "Why do you want this job?"

Two sentences: what excites you about the work, why this company specifically. "I want to work on distributed systems at scale, and Razorpay's UPI stack processes 200M transactions a day — I want to learn from the team that built that."

2. "What is your biggest weakness?"

Real weakness, real fix, small stakes. Never "I work too hard". Try: "I tend to over-engineer first drafts. I've been working on shipping a minimum version first — on my last project I set a rule to open a PR within 3 days of starting."

3. "Walk me through your resume."

Chronological, 2 minutes max. Education → internships → projects → current. Each item gets one sentence of impact.

4. "Tell me about a time you failed."

STAR it. Real failure, specific recovery, explicit learning. "I missed a deadline because I didn't flag a blocker early — now I raise blockers in daily standup within 24 hours."

5. "Why should we hire you?"

Three points: skill match, culture match, growth curve. "I've built the exact stack you use, I thrive in high-autonomy teams, and I learn fast — I went from Python to Go in 4 weeks for my last internship."

6. "Where do you see yourself in 5 years?"

Honest but ambitious. "Senior engineer, probably in a tech-lead role. I want to ship systems used by millions and mentor a team — both skills I'm building now."

7. "Do you have any questions for us?"

Always yes. Two questions minimum. Ask about the team's current challenges, the on-boarding process, or how success is measured in the first 90 days.

What Fluento AI does that YouTube prep videos can't

YouTube videos teach you theory. Fluento AI makes you rehearse out loud. In the Mock Interview scenario, Rajesh actually interrupts you, asks follow-ups, and you have to respond in real time — just like the real interview. That's the rep that builds muscle memory.

For the full 30-day language foundation that sits underneath interview prep, see our 30-day English speaking plan. For how Fluento AI compares to alternatives like Cambly (which many candidates consider for interview prep), see Fluento AI vs Cambly.

The day-of checklist

• 7 hours of sleep. Non-negotiable. Tired brains freeze.
• Warm up your voice 15 minutes before — a live Fluento AI session is perfect.
• Water, not chai, 30 minutes before. Caffeine amplifies anxiety.
• Test your mic and internet 10 minutes before.
• Smile when you say hello. It changes your voice.

You've got this

The interview freeze is not a permanent condition. It is an untrained skill. Three weeks of daily rehearsal with Fluento AI is enough to convert 80% of "I froze" outcomes into "I answered". Start today.

Rehearse your interview with Fluento AI — free.