Practice explaining and answering
The first client call where I forgot what useEffect does taught me more than any tutorial. Here is how I practice now so it does not happen again.
What You'll Learn
- Learn to explain technical concepts in clear, simple English
- Practice recording and reviewing your own answers
- Simulate interview Q&A sessions with AI or peers
- Build confidence through iterative improvement
- Improve English fluency if you are not a native speaker
Why did the senior nail it and you froze?
The first time a client asked me to walk through my own PR on a call, I forgot what useEffect does. Not the edge cases. The base thing. I had shipped the code two days earlier.
I am from Romania, and my English is the second language I am juggling on those calls. The freeze was not really about React. It was about searching for the word "side effect" while six people on a Google Meet waited. That is the muscle this lesson trains. Fluency under mild pressure, in English, about code you already know.
Step 1: Practice out loud
Pick the concept that scares you most on a call. For me last year it was useEffect. For a colleague of mine it was CSS specificity (she could write it, she could not say it).
Talk through it like the junior on your team is sitting across the desk. Out loud. Not in your head. The mouth is slower than the brain, and that gap is exactly where the freeze lives.
Watch for the giveaways. Do you reach for "basically" three times in one sentence? (I do, every single time I am tired.) Do you skip the example because it feels too obvious, then realise the example was the whole point? Do you actually know the thing, or are you orbiting it?
Step 2: Record yourself
Phone on the desk, voice memo, five to ten minutes. Two or three questions, answered like the recruiter is on the other side.
Then play it back. This is the awkward part. The first time I did it, I counted eleven "so basically" fillers in four minutes, and a "you know" tic I had no idea I owned. I almost deleted the file out of secondhand embarrassment.
Do not delete it. The fillers are the actual data. The grammar slips you hear (mine: dropping articles when I get tired, "send it on slack" instead of "send it on Slack") are the things that will leak into the real call if you do not catch them in private first.
Reviewing yourself on video is uncomfortable but it's the fastest way to see how you really come across, both technically and in English.
Step 3: Simulate Q&A
Solo practice has a ceiling. You answer the questions you already know are coming. The real call has a follow-up you did not plan for.
Grab a colleague over coffee, or open Claude or ChatGPT and ask: "Give me 5 random front-end interview questions about CSS and JavaScript, and then ask me one nasty follow-up after each." Answer them out loud, no pausing to look anything up. The follow-up is the whole point. That is where the freeze lives, and that is where you train it out.
Step 4: Improve iteratively
You are not chasing a TED talk. You are chasing the next session being slightly less embarrassing than this one.
The session that actually broke something for me was a Tuesday evening in February, explaining event delegation. I had practiced it three times that week and still rambled for two minutes before I said the word "bubble". On the playback I noticed I had been describing the symptom (one listener on the parent) and never the mechanism (events walk up the DOM). I rewrote my answer around the mechanism, recorded again, and it landed in forty seconds. That one swap, naming the mechanism before the symptom, is now how I open every explanation. (Senior devs reading this will recognise the pattern. It took me embarrassingly long to find it on my own.)
Every recording is practice. Don't delete the "bad" ones, they show you how far you've come.
Closing reminder
None of this is about memorizing perfect answers. It is about training the gap between "I know this" and "I can say this in English, on a Meet call, while five strangers nod."
Try one tonight. Pick the concept you would least want to be asked about, record three minutes on it, and play it back. Send me the thing you noticed about your own voice that surprised you, I will probably recognise it from my own recordings. Next lesson we move from explaining to the harder thing, the question you do not know the answer to, and how to not freeze when it lands.