If you’re an Indian software engineer targeting FAANG companies, you’ve probably spent months on data structures, system design, and coding practice. Your LeetCode streak is impressive. Your system design notes are comprehensive.
But here’s the question nobody prepares for: can you communicate your experience clearly in English, under pressure, to someone who’s evaluating you in real time?
This guide is a 6-week plan for the communication side of interview preparation. It assumes your technical preparation is already underway. This is the layer that sits on top.
Week 1-2: Assessment and awareness
Before you can improve, you need to know where you stand.
Record yourself
Answer these three questions out loud, on camera, with a 2-minute time limit each:
1. "Tell me about yourself and your current role."
2. "Tell me about a time you had to make a difficult technical decision."
3. "Explain a system you’ve built to someone who isn’t technical."
Watch the recordings. Be honest with yourself about:
- **Clarity**: Would someone unfamiliar with your project follow your explanation?
- **Timing**: Did any answer go over 2 minutes?
- **Fillers**: Count every "basically," "actually," "you know," "so," and "like."
- **Pronunciation**: Were there words you stumbled on or that sounded unclear?
- **Pace**: Did you speed up as you got more nervous?
This baseline recording is important. You’ll compare against it in Week 6.
Build your vocabulary list
Write down every technical term you use regularly at work. Architecture, deployment, microservices, API, scalability, latency, throughput, containerisation, CI/CD, observability, and so on.
For each word, check the correct pronunciation and stress pattern. Use an online dictionary with audio. Say each word out loud 10 times with correct stress.
Week 3: Story building
Mine your career for stories
You need five strong stories that cover these competency areas:
1. Leadership or influence
2. Conflict or disagreement
3. Failure and learning
4. Technical innovation or simplification
5. Delivering under pressure
For each story, write the STAR skeleton in bullet points:
- **Situation**: 2 sentences maximum. Set the scene with specifics (company size, team size, timeline).
- **Task**: 1 sentence. What was your specific responsibility?
- **Action**: 3-5 bullet points. What did YOU do? Use "I," not "we."
- **Result**: 1-2 sentences with at least one number (percentage improvement, revenue impact, time saved, users affected).
Timing drill
Set a timer for 90 seconds. Tell each story out loud. If you go over, cut content. The story must land in 90 seconds.
Do this daily for each story until the timing is natural.
Week 4: Pronunciation and delivery
Target your problem sounds
For most Indian English speakers, the priority sounds are:
- "th" (think, the, through, three)
- "v" vs "w" (version, variable, very)
- Word stress on multi-syllable terms (architecture, asynchronous, character)
- Past tense endings (-ed: worked, managed, deployed)
Spend 10 minutes daily drilling these specific sounds in the context of your interview stories. Not in isolation. In sentences you’ll actually say.
Filler elimination
Do the 2-minute speaking drill daily: talk about any topic, stop and pause every time you catch a filler. This is the single most impactful exercise you can do.
Week 5: Simulation
Mock interviews
Find a friend, colleague, or coach to run mock behavioural interviews. Give them a list of real FAANG behavioural questions:
- "Tell me about a time you had to convince your team to change direction."
- "Describe a situation where you disagreed with your manager. What happened?"
- "Tell me about your biggest professional failure."
- "Give me an example of when you had to learn something quickly."
- "Tell me about a time you went above and beyond for a customer or user."
Do at least 3 full mock interviews (5-6 questions each). Record them. Review them.
Pay attention to:
- Are you answering the question that was asked?
- Is your STAR structure clear?
- Are your answers under 90 seconds?
- How many fillers per answer?
- Does your pronunciation hold up under pressure?
Question adaptation
Take one story and practise answering three completely different questions with it. This builds the flexibility to handle unexpected questions without freezing.
Week 6: Polish and confidence
Compare recordings
Record yourself answering the same three questions from Week 1. Watch both recordings side by side. You will see the difference.
Interview day preparation
- Test your camera, microphone, and lighting
- Have water within reach
- Keep your STAR bullet points visible but not readable (one-word reminders only)
- Plan your energy management for a full day of interviews (5-6 rounds)
- Have a recovery routine between rounds (stand up, stretch, breathe, drink water)
The mindset shift
By Week 6, your communication will be measurably better than Week 1. Not perfect. Better. And better is what gets you the offer.
The interviewer isn’t expecting you to sound like a native speaker. They’re expecting to understand your answers without effort, to see clear thinking in how you structure your responses, and to feel confident that you can communicate effectively on their team.
That’s a trainable skill. And you’ve been training it for six weeks.
When self-preparation isn’t enough
This guide will take you a long way. But it has a ceiling. You can’t objectively hear your own pronunciation. You can’t feel the difference between a confident pause and an awkward silence from inside the conversation. You can’t replicate the pressure of a real interview alone in your room.
That’s where coaching comes in. A specialist who can hear what you can’t, push you past your comfort zone, and give you the honest feedback your friends are too polite to deliver.
Whether you work with a coach or go solo, the important thing is that you start. Six weeks from today, you could be a fundamentally different communicator. But only if you put in the work.