You cleared the coding round. Your system design was solid. The recruiter sounded excited on the follow-up call.
Then you sat down for the behavioural round, and forty-five minutes later, you knew it was over.
This happens to thousands of Indian software engineers every year. Not because they lack the experience. Because they can’t communicate it under pressure in a way that lands with the interviewer.
Why the behavioural round is different
Technical rounds have right answers. You either solve the problem or you don’t. The behavioural round is subjective. The interviewer is evaluating how you think, how you communicate, and whether they’d want to work with you.
For native English speakers, this is mostly about content. Pick the right story, structure it well, land the point.
For Indian engineers, there’s an extra layer. You’re doing all of that while simultaneously translating thoughts from your native language, managing pronunciation, controlling your pace, and fighting the urge to fill every silence with "basically."
That’s not a level playing field. But it’s the field you’re on.
The three things that actually matter
After coaching dozens of Indian engineers through FAANG behavioural rounds, the same three issues come up almost every time.
1. Your answer takes too long
Most candidates take 3-4 minutes to answer a single behavioural question. The interviewer checked out at the 90-second mark. They’re not rude. They have six competencies to evaluate in 45 minutes. They need you to be concise.
The fix: every answer should land in under 90 seconds. That means your Situation is two sentences. Your Task is one sentence. Your Action is the bulk. Your Result has a number in it.
If you’ve been practising the STAR method by writing out full paragraphs, stop. Start practising with a timer.
2. Your pronunciation costs you credibility
This is the one nobody wants to talk about. Your accent is not the problem. The problem is when specific pronunciation patterns make your answer harder to follow than it needs to be.
Words like "architecture," "asynchronous," "deployment," and "scalability" come up in every technical behavioural answer. If the interviewer has to work to understand these words, they’re spending cognitive effort on decoding instead of evaluating your experience.
The fix is targeted, not wholesale. You don’t need to sound British or American. You need the 50 technical terms you use most to be instantly clear.
3. You freeze on unexpected questions
You’ve prepared five stories. You’ve rehearsed them. Then the interviewer asks something you didn’t prepare for, and your mind goes blank.
This happens because most preparation is about memorising answers, not building the skill of answering. There’s a difference.
The fix: instead of memorising 20 stories, build 5 stories that you can adapt to different angles. Learn to listen to the actual question, confirm what’s being asked, and flex your story to fit. That’s a trainable skill.
What good actually sounds like
A strong behavioural answer from an Indian engineer doesn’t sound like a native speaker. It sounds like someone who is clear, structured, and confident. The pronunciation is clean on the words that matter. The pace is controlled. The answer has a beginning, middle, and end. And it takes 60-90 seconds, not four minutes.
That’s not natural talent. That’s preparation.
The timeline
If you’re 6-8 weeks from your first FAANG application, that’s the right time to start working on communication. Not the week before. These are habits, and habits take repetition to change.
If you’re already in the interview pipeline and your behavioural round is in two weeks, you can still make meaningful improvements. Focus on answer structure and timing first. Those have the fastest payoff.