A software engineer with five years of experience clears the coding round at Google. Then enters the behavioural interview. Forty-five minutes later, the offer slips away. The rejection email says "culture fit." The engineer goes back to LeetCode. Six months later, the same thing happens. The problem was never the code.
There is a pattern that plays out thousands of times a year across Bangalore, Hyderabad, Pune, and Mumbai. Engineers at TCS, Infosys, and Wipro spend three months preparing for FAANG interviews. They clear the online assessment. They pass the phone screen. They solve the coding round. Then the behavioural interview happens, and the offer disappears.
The communication gap nobody prepares for
Indian engineers preparing for FAANG interviews spend an average of 200 to 400 hours on data structures, algorithms, and system design. Most spend zero hours on how they communicate their answers.
This is not a language problem in the traditional sense. These engineers speak English fluently. They use it every day at work, in emails, in meetings, in documentation. They passed English exams in school and university.
The problem is specific to high-pressure, time-constrained, one-on-one verbal evaluation. A FAANG behavioural interview is not a conversation. It is a performance. The interviewer is scoring the candidate on how clearly, concisely, and confidently they articulate their experience. Every word matters. Every pause matters. Every filler word counts against you.
Six things that go wrong in the room
Indian software engineers face a specific set of communication challenges in FAANG behavioural interviews that are distinct from the challenges faced by native English speakers.
Pronunciation under pressure
In relaxed conversation, pronunciation is rarely an issue. Under interview stress, pronunciation degrades. Multi-syllable technical words like "asynchronous," "architecture," and "idempotent" become harder to articulate cleanly. The interviewer starts working to understand the words rather than evaluating the content.
Filler word density
The most common filler words in Indian English are "basically," "actually," and "you know." In casual conversation, these are invisible. In a scored behavioural interview, they signal uncertainty. One candidate counted 47 filler words in a single 30-minute practice recording. They had no idea until they listened back.
The rambling answer
Indian education emphasises thoroughness. In an exam, a longer answer typically scores higher. In a FAANG behavioural interview, the opposite is true. Answers longer than 90 seconds lose the interviewer. The candidate who takes four minutes to describe a project they led is not being thorough. They are losing the room.
Speed escalation
Nervous candidates speak faster. As the interview progresses and anxiety builds, the pace increases. Words start blending together. The interviewer misses key points. The candidate interprets the confusion as a sign that their answer is wrong, which increases anxiety further. It becomes a spiral.
Statement-as-question
A pattern specific to Indian English is ending declarative statements with a rising intonation, turning them into implicit questions. "I decided to refactor the service?" "We reduced latency by 40%?" This speech pattern makes confident decisions sound uncertain. The interviewer hears hesitation where the candidate feels conviction.
The missing "I"
Indian professionals are often trained to credit the team. "We did this" and "the team achieved that" are respectful and culturally appropriate. In a behavioural interview, they are a problem. The interviewer needs to know what the candidate specifically did, decided, and contributed. Using "we" for personal actions obscures individual capability.
Why standard interview prep does not fix this
Interview preparation courses like Interview Kickstart, AlgoExpert, and Pramp focus entirely on what to say. Data structures. System design frameworks. STAR method templates. None of them address how to say it.
The communication gap requires a different kind of preparation. It requires working with someone who can hear the pronunciation issues, identify the filler patterns, restructure the answer flow, and build the muscle memory of clear, confident speech under pressure.
This is the domain of English as a Second Language coaching, applied specifically to the technical interview context. Not generic English tutoring. Not accent elimination. Targeted communication coaching that addresses the exact skills FAANG behavioural interviewers evaluate.
The ROI calculation most engineers miss
A mid-career software engineer in India earning ₹15-20 lakhs per annum can expect a FAANG offer in the range of ₹40-80 lakhs or more, depending on level and location. The salary difference in the first year alone is ₹20-60 lakhs.
Communication coaching for FAANG interview preparation typically costs between ₹25,000 and ₹75,000 for a structured programme. That represents less than 1% of the first-year salary increase.
Engineers routinely invest ₹50,000 to ₹2,00,000 in technical interview preparation courses without hesitation. The communication side of the interview, which accounts for roughly half of the hiring decision at companies like Google, Amazon, and Meta, receives almost no investment.
What effective FAANG communication coaching covers
A structured communication coaching programme for Indian software engineers targeting FAANG roles typically addresses the following areas across 6 to 10 sessions.
Pronunciation clarity on technical vocabulary, with specific focus on sounds that Indian English speakers find most challenging: the "th" sound, "v" versus "w" distinction, and stress patterns on multi-syllable words.
Answer structure for behavioural questions, moving beyond rigid STAR method recitation to natural storytelling with a hook, concise context, decision-based actions, and quantified results.
Filler word elimination through awareness exercises and replacement techniques, building the habit of confident pauses instead of verbal fillers.
Pacing and rhythm control, including physical techniques for managing anxiety so that English fluency does not deteriorate under pressure.
Technical explanation clarity, teaching engineers to explain complex systems to both technical and non-technical interviewers without jargon-dumping.
The shift that makes the difference
The engineers who successfully bridge the communication gap do not become different people. They do not adopt an American accent or memorise scripts. They learn to do what they already do well in writing, but verbally, under pressure, in real time.
They learn to pause instead of filling. To structure instead of rambling. To quantify instead of generalising. To say "I decided" instead of "we decided."
The code was always good enough. The voice catches up.