Communication Skills — Round 1, Section 6 (Training Plan)¶

This file covers Round 1, Section 6: Communication Skills for the Candescent SDET/Automation interview. It is a real do-the-work training plan to improve your spoken English and interview talk — not just a list of tips. Read it once fully, then come back to do the daily drills.

1. Why this is scored & what "good" sounds like¶

In this interview, one part of your score is how you speak — not what you know, but how clearly you say it.

The interviewer is a person (often US-based). They will pass your interview notes to a hiring manager who never met you. So the interviewer is silently asking: "If I put this person on a call with our US client or product team, will they be understood the first time, without me explaining again?"

That is the whole game. Be understood the first time.

What "good" sounds like (the 5 things they listen for)¶

They want	Plain meaning	What it sounds like
Clear	Easy to hear and understand	Words come out fully, not mumbled or rushed
Structured	Organized, has a beginning–middle–end	"There are three reasons. First… Second… Finally…"
Concise	Short and to the point, no rambling	Answer fits in 30–60 seconds, not 4 minutes
Confident	Calm, steady, sure of yourself	Steady tone, no shaking voice, few "um"s
No repetition	You don't say the same thing 3 times	You make a point once, then move on

The JD red flag — DO NOT repeat the question slowly¶

Some candidates repeat the interviewer's question back, word for word, slowly:

Interviewer: "How do you handle flaky tests?" ❌ Candidate: "So… how… do… I… handle… flaky… tests… okay so…"

This looks very bad in a remote interview. It looks like you are reading the question out loud so an AI assistant or a person off-camera can feed you the answer. Interviewers are trained to catch this and it can get you rejected on the spot.

✅ Instead, answer naturally, in your own words, right away:

"Good question. Flaky tests usually come from timing or shared state, so the first thing I check is the waits…"

A short natural lead-in ("Good question," "Sure,") is fine. Repeating the whole question slowly is the trap. Avoid it.

2. The 5 most common problems for Indian English speakers — and the fix¶

These are the most common things that lower a communication score. Each one has a fix and a 1-line drill you can do today.

(a) Filler words — "um, basically, actually, like, you know, only, na"¶

Fillers are sounds you make while your brain catches up. A few are normal. Too many make you sound unsure.

❌ "So basically, um, what I actually did was, like, you know, I just only added a wait." ✅ "What I did was add an explicit wait." (pause) "That fixed the timing issue."

The fix: Replace the filler with silence. A 1-second pause sounds smarter than "um." Silence feels long to you but sounds confident to the listener.

Drill (1 line): Speak for 30 seconds about your last project. Every time you say a filler, snap your fingers. Goal: zero snaps by day 5.

(b) Speaking too fast / mumbling¶

When nervous, many speakers speed up and swallow the ends of words. The listener then has to guess, and that kills your score.

❌ (fast, run together) "yeahsoIwrotetheframeworkinPlaywrightitusesPOMandwerunitinCI" ✅ (slower, clear) "I built the framework in Playwright." (small pause) "It uses the Page Object Model." (pause) "And we run it in CI."

The fix: Aim for about 130–140 words a minute — slower than your normal Hindi/Kannada speed. Finish the last sound of every word ("framework", "CI", "tests"). Put a tiny pause at every comma and full stop.

Drill (1 line): Read one paragraph aloud at "news anchor" speed — slow, with full stops. Record it. It should feel too slow to you.

(c) Rambling / no structure¶

This is the biggest one. You start answering, keep adding points, and never stop — so the interviewer loses the thread.

❌ "So testing, there's many types, like we do API and UI and also sometimes performance and I also did some security and the framework, it depends on the project actually, like in my last one we used…" (still going)

✅ "I focus on three test layers." (pause) "API, UI, and a small set of end-to-end checks. On my last project, the API layer caught most bugs early." (stop)

The fix: Use a framework (Section 3). Decide the shape of your answer before you start: headline first, then 2–3 points, then stop.

Drill (1 line): Before answering any practice question, say in your head: "Headline, then three points, then stop." Then speak.

(d) Tense and grammar slips¶

A few specific patterns trip up almost everyone. Fix these four and you will sound noticeably more polished.

❌ Common slip	✅ Correct version	Rule (plain)
"I am working here since 2 years."	"I have been working here for 2 years."	Ongoing-since-the-past → have been …ing + for (a length) / since (a start point)
"Yesterday I go to office and fix the bug."	"Yesterday I went to the office and fixed the bug."	Past time → past tense verbs
"I didn't wrote the test."	"I didn't write the test."	After didn't, use the base verb
"He is having good knowledge of Java."	"He has good knowledge of Java."	Have for owning a thing → no -ing
"I will revert back to you."	"I will get back to you."	"Revert" means undo; use "get back to you"

The fix: Just drill these five sentences out loud until the correct one feels automatic.

Drill (1 line): Say out loud 3 times: "I have been working on automation for four years." Then: "Yesterday I went and fixed it."

(e) Flat tone / low confidence¶

A flat, quiet, monotone voice makes you sound bored or unsure — even when your answer is great.

❌ (flat, no energy) "yeah i think automation is good it saves time it is useful" ✅ (with stress on key words) "Automation is a big win — it saves time and catches bugs before release."

The fix: Stress the important word in each sentence (say it a little louder/longer), and let your voice go slightly up at exciting parts. Smile a little — it changes your sound.

Drill (1 line): Say "This is the most important part of my framework." Hit the word "most" hard. Feel the difference vs. saying it flat.

3. Answer-structuring frameworks (so you never ramble)¶

Pick one of these before you start talking. They give your answer a clean shape.

Headline-first (BLUF — "Bottom Line Up Front")¶

Give the answer in one sentence first, then explain. Don't make the listener wait.

Q: "Did the migration to Playwright help?"

❌ Weak (makes them wait): "So we had Selenium, and it was slow, and there were flaky tests, and we discussed, and after some time we decided, and then we tried Playwright and…"

✅ Strong (headline first): "Yes, it helped a lot." (pause) "Our test suite got about 40% faster and far less flaky. The main reason was Playwright's auto-waiting, which removed most of our timing failures."

PREP — for opinion questions (Point, Reason, Example, Point)¶

Use this when asked "What do you prefer / what do you think?"

Q: "Selenium or Playwright — which do you prefer?"

P (Point): "For new projects, I prefer Playwright."

R (Reason): "Mainly because of its built-in auto-waiting, which cuts down on flaky tests."

E (Example): "On my last project, switching a flaky login suite to Playwright took our failure rate from about 1 in 5 runs to almost zero."

P (Point again): "So for greenfield work, Playwright is my default — though I'd still pick Selenium if the team's whole ecosystem is built around it."

(Notice: clear opinion, one reason, one real example, clean close. ~25 seconds.)

STAR — for experience questions (Situation, Task, Action, Result)¶

Use this for "Tell me about a time when…"

Q: "Tell me about a hard bug you found."

S (Situation): "On a banking app, payments were randomly failing in production but never in test."

T (Task): "I was asked to reproduce it and find the root cause."

A (Action): "I added detailed logging, compared the test and prod configs, and found a race condition — two services updating the same balance at once. I wrote a concurrent test that reproduced it reliably."

R (Result): "The team added a lock, the failures stopped, and my concurrent test is now part of the regression suite."

(End on the Result — it's the part they remember.)

Signposting — tell them the map before the journey¶

Say how many points are coming. The listener relaxes because they know when you'll finish.

✅ "There are three things I check for flaky tests. First, the waits. Second, shared test data. And finally, the test order." (Then explain each in one line.)

The "rule of three" — group points in threes¶

Three is the magic number — easy to say, easy to remember. Not two (sounds thin), not five (you'll forget one).

✅ "A good test is fast, reliable, and easy to read." ✅ "I'd improve this in three ways: better waits, isolated data, and parallel runs."

4. Phrase bank (memorize these)¶

These are ready-made sentences. Memorize them so they come out automatically under pressure. When you have a phrase ready, you stop saying "um."

Buying thinking time (instead of "um…")¶

"That's a good question — let me think for a second."
"Let me take a moment to give you a proper answer."
"Good question. Give me a second to organize my thoughts."

Clarifying the question¶

"Just to make sure I understand — are you asking about X or Y?"
"When you say scale, do you mean number of tests or number of users?"
"Do you want a high-level answer, or should I go deep into the code?"

Structuring your answer¶

"I'll cover this in three parts."
"Let me start with the short answer, then explain."
"There are a few angles here — let me take the most important one first."

Disagreeing politely¶

"I see it a bit differently, and here's why…"
"That's one valid approach. In my experience, though, I've found that…"
"I'd push back gently on that — mainly because…"

Admitting you don't know (the RIGHT way — never just "I don't know")¶

"I haven't used that directly, but here's how I'd approach it…"
"I'm not 100% sure of the exact syntax, but the concept is… and I'd confirm it in the docs."
"That's outside my hands-on experience, but my best guess would be… — happy to be corrected."

Recovering from a stumble¶

"Let me restart that thought."
"Sorry, let me say that more clearly."
"Actually, the cleaner way to put it is…"

Closing an answer (so they know you're done)¶

"So in short, …"
"So that's the main reason I'd go with that approach."
"That's how I'd handle it."

5. Pronunciation & word-stress mini-guide¶

These tech/interview words are commonly mispronounced. The CAPITAL part is the stressed (louder/longer) syllable. Say each one out loud 3 times.

Word	Say it like	Note
data	DAY-tuh	Not "DA-ta"; US prefers "DAY-tuh"
query	KWEER-ee	Not "KEW-ree"
schema	SKEE-muh	Not "SHEE-ma" or "SKAY-ma"
suite	sweet	Like the candy. NOT "soot". "Test sweet."
cache	cash	Like money. NOT "ka-shay".
niche	neesh	Rhymes with "leash"
parameter	puh-RAM-uh-ter	Stress the RAM
variable	VAIR-ee-uh-bul	4 sounds, not "var-EE-able"
deque	deck (or "D-Q")	Double-ended queue
Gherkin	GUR-kin	Like the pickle
idempotent	eye-DEM-puh-tunt	Stress the DEM
asynchronous	ay-SING-kruh-nus	Stress the SING
architecture	AR-ki-tek-cher	Starts "AR-ki", not "arsh"
available	uh-VAY-luh-bul	Stress the VAY
development	dih-VEL-up-munt	Stress the VEL
environment	en-VY-run-munt	Don't drop the "n": en-VY-RON-ment
specific	spuh-SIF-ik	NOT "pacific"
focus	FOH-kus	Not "fokas"

Tip: pick 3 words a day from this table and use them in a real sentence out loud. By the end of the table you'll own all of them.

6. Daily practice drills (each ~10–15 min)¶

Do these every day. Each one fixes a specific problem.

(a) Read-aloud from a tech article¶

How: Pick one paragraph from a tech blog (e.g. a Playwright or testing article). Read it out loud slowly and clearly, finishing every word. Fixes: Mumbling, swallowed word-endings, pace. Warms up your mouth for English.

(b) Shadowing (this is the most powerful one)¶

What it is: You play a video of a native English speaker (a tech talk, a YouTube tutorial, a news clip). You repeat what they say, 1–2 seconds behind them, copying their rhythm and tone — like an echo. You're not translating, you're copying the music of their speech. How: Play 2 minutes. Talk along with them, matching their stress and pauses. Replay tricky bits. Fixes: Tone, rhythm, stress, natural pausing, accent clarity — all at once. Do this daily and your spoken English transforms.

(c) Record-and-review a 1-minute answer¶

How: Pick one interview question. Record yourself answering for 1 minute on your phone. Then listen back. Count your fillers. Note where you rambled. Fixes: Self-awareness. You can't fix what you can't hear. This is uncomfortable but it works fastest.

(d) The "60-second topic" drill¶

How: Pick a random topic (e.g. "my morning routine," "REST APIs," "Bengaluru traffic"). Speak for a full 60 seconds with zero filler words. If you say "um," restart the clock. Fixes: Filler words and thinking on your feet without panicking.

(e) Explain a concept to a 10-year-old¶

How: Pick a tech concept (CI/CD, an API, a flaky test). Explain it out loud as if to a 10-year-old — no jargon. Fixes: Clarity and conciseness. If you can make it simple, you truly understand it — and simple, clear answers score highest.

7. Two-week communication improvement plan (~30–45 min/day)¶

Build from drills to full mock answers. Don't skip the recording — it's where the real growth happens.

Day	Focus	Do this (~30–45 min)
1	Baseline	Record a 2-min "Tell me about yourself." Save it. Count fillers + note slips. This is your "before."
2	Pace + clarity	Read-aloud drill (10 min). Shadowing (10 min). Re-record "Tell me about yourself" slower.
3	Fillers	60-second topic drill x3, zero fillers (15 min). Shadowing (10 min).
4	Grammar	Drill the 5 tense fixes from §2(d) out loud (10 min). 60-sec drill x2.
5	Headline-first	Answer 4 questions using BLUF (headline first). Record one. Shadowing (10 min).
6	PREP	Do 3 opinion questions with PREP (Selenium vs Playwright, manual vs auto, etc). Record one.
7	Rest / light	Just shadowing (15 min) + explain-to-a-10-year-old x2. Review your Day 1 recording — hear your progress.
8	STAR	Write + speak 3 STAR stories (hard bug, conflict, missed deadline). Record one.
9	Phrase bank	Memorize §4 phrases. Do a mock where you force in 5 of them naturally.
10	Pronunciation	Drill the full §5 table. Re-record any answer focusing on clear word-endings.
11	Full mock #1	Have a friend (or AI voice) ask 5 mixed questions. Record the whole thing. Review.
12	Fix weak spots	Listen to mock #1. Pick your 2 worst habits. Drill only those.
13	Full mock #2	Another 5-question mock, on camera, with video etiquette (§8). Review.
14	Polish + confidence	Re-record "Tell me about yourself." Compare to Day 1. Light shadowing. Rest your voice before interview.

8. Video-call etiquette & body language¶

How you look and sound on the call is part of the impression. Simple rules:

Look at the camera, not the screen. When you talk, look at the little camera dot, not at the interviewer's face on screen. To them, it feels like eye contact. Glancing at your own face or notes looks shifty.
Sit up straight. Slouching makes your voice weak. Sitting up opens your chest and your voice gets stronger.
Smile slightly. A small smile changes your tone to warm and friendly. You can hear a smile.
Good light in front of you. Face a window or a lamp. Never sit with a bright window behind you (you become a dark shadow).
Slow down on video. Internet adds tiny delays. Speak a bit slower than in person and pause before answering so you don't talk over them.
Camera at eye level. Raise your laptop on some books so the camera is level with your eyes, not looking up your chin.
The "show your room" / no-second-screen request: Some interviewers ask you to share your screen, show your room with your phone, or confirm no one else is helping. This is normal anti-cheating. Stay relaxed and comply happily. Have a clean, quiet space and no second monitor with answers. Looking calm here builds trust.
If the internet glitches: Don't panic. Say calmly: "Sorry, you cut out for a second — could you repeat the last part?" or "My connection glitched — let me say that again." Everyone understands tech issues; handling it calmly looks professional.

9. Handling tough moments (short scripts)¶

Memorize these one-liners. They turn a panic moment into a smooth one.

Moment	What to say (script)
You blank out / mind goes empty	"Let me take a second to gather my thoughts." (pause, breathe, start with a headline)
You didn't understand the question	"I want to make sure I answer the right thing — could you rephrase that, or give me an example?"
You got interrupted	(Let them finish.) Then: "Sure — and to close my earlier point, …"
A question you genuinely can't answer	"I haven't worked with that directly. But based on what I know, I'd approach it by… — and I'd verify the details in the docs." (Never just say "I don't know" and stop.)
You realize you're rambling	"Let me tighten that up — the key point is…"
You made a factual mistake	"Actually, let me correct myself — the right answer is…" (Self-correcting looks honest and sharp, not weak.)

Golden rule for tough moments: Pause and breathe before you speak. A 2-second silence feels huge to you but normal to them, and it stops the panic-rambling.

10. Two example mock dialogues¶

Mock (a): "Tell me about yourself"¶

Interviewer: "So, tell me about yourself."

❌ Weak answer: "Yeah so basically my name is Rohan and I am from Bengaluru and I did my engineering and then I joined as a tester and I am working since like 4 years and I know Selenium and also Playwright and TestNG and I have done API testing also and security testing and um yeah I like automation and that's it about me." (no structure, fillers, "working since 4 years," trails off weakly)

✅ Strong answer: "Sure." (small pause) "I'm an SDET with about four years of experience in test automation, mostly in banking and finance apps." (pause) "I'll give you three quick points. First, my core stack — I build UI automation with Selenium and Playwright, and API tests with Rest Assured. Second, the impact — on my last project I cut our flaky failures by around 80% by fixing waits and isolating test data. And third, what I enjoy — I like building frameworks that the whole team can use, not just running tests." (pause) "That's me in short — and I'm drawn to Candescent because it's solving real problems in digital banking, which is exactly where my experience is."

Notice: headline → rule of three → signposting → confident close → ties to the company. Around 40 seconds. Correct tense: "I have… experience," "I cut.")

Mock (b): A technical question¶

Interviewer: "How do you deal with flaky tests in your automation suite?"

❌ Weak answer: "So flaky tests, um, they are very common actually, and it happens because of many reasons like the waits and sometimes the data and sometimes the environment is also slow and we add Thread.sleep sometimes and basically we just rerun it and if it passes then okay…" (rambling, no structure, admits a bad practice, no clear close)

✅ Strong answer: "Good question." (pause) "Flakiness almost always comes from one of three things, so I check them in order. First, timing — I replace any fixed sleeps with explicit waits on a specific condition. Second, shared state — I make sure each test creates and cleans up its own data, so tests don't affect each other. And third, test order — I run them in parallel and randomized to catch hidden dependencies." (pause) "So in short: fix the waits, isolate the data, and randomize the order. Rerunning is a last resort, not a fix."

Notice: short lead-in (not repeating the question), signposting, rule of three, headline close with "So in short," and a sharp final line.

11. One-page "Say it like this" cheat-sheet¶

Glance at this 10 minutes before the interview.

The 3 frameworks¶

Headline first (BLUF): Answer in ONE sentence, then explain.
PREP (opinions): Point → Reason → Example → Point.
STAR (stories): Situation → Task → Action → Result (end on Result).
Always: signpost ("Three things…") + rule of three.

Top phrases (memorize)¶

Buy time: "That's a good question — let me think for a second."
Clarify: "Just to make sure I understand — are you asking about X or Y?"
Structure: "I'll cover this in three parts."
Don't know: "I haven't used that directly, but here's how I'd approach it…"
Recover: "Let me restart that thought."
Close: "So in short, …"

Top fixes¶

❌ Don't	✅ Do
"um, basically, like, actually"	Pause silently instead
Talk fast / mumble	Slow to ~130 wpm, finish every word-ending
Ramble forever	Headline + 3 points + stop
"working since 4 years"	"have been working for 4 years"
"yesterday I go"	"yesterday I went"
Repeat the whole question slowly	Short lead-in, then answer naturally
Flat monotone	Stress the key word; slight smile
Just say "I don't know"	"I haven't used it, but I'd approach it by…"

Final 3 reminders¶

Pause and breathe before answering — silence sounds confident.
Look at the camera, sit up, slight smile, good light.
Be understood the first time — that's the whole score.

You've got the technical skills. This is just about packaging them clearly. Do the drills, trust the frameworks, and speak slowly. You'll be great.