Skip to main content
9 min read

How to Ace an English-Language Phone Screen as a Non-Native Speaker

The phone screen is the worst-performing stage for non-native English speakers in Tashkent. Not the technical interview — that one is forgiving, because the work speaks for itself. The phone screen is forgiving of nothing. It is 30 minutes with a non-technical recruiter who has no way to evaluate you except by how you sound. They are not listening for vocabulary. They are listening for whether you will be hard to put in front of their engineering managers.

Most candidates fail this stage with a strong CV and a real technical foundation. The fix is structural, not linguistic. Here is what to actually do.

What the recruiter is really evaluating

Three things, in this order:

  • Can you carry the conversation without me having to repeat questions?If they have to rephrase even one question because you did not understand, your bar shifts up for the rest of the call.
  • Do you sound confident, or do you sound like you are guessing? Confidence in a phone screen is not loud or fast. It is steady pace, no apologies, finishing your sentences.
  • Will I have to coach you before each interview? Recruiters have a fixed amount of time per candidate. If you sound like a high-effort candidate, you lose to someone who sounds like a low-effort one even if you are technically stronger.

The five mistakes that kill phone screens

Mistake 1: filler words

“Uh,” “like,” “basically,” “ya'ni,” “in fact.” Once a sentence is fine. Once every six words is a red flag. The cure is recording yourself answering five common questions and listening back. You will hear them. The first time you do this is unpleasant. Do it anyway.

Mistake 2: starting answers with “so”

“So, my last project was…” sounds like you are building up. Strong answers start with the noun. “My last project was a payments service for a fintech in Tashkent.” Cut the “so.” You will hear yourself reach for it on every question. Catch it.

Mistake 3: apologizing for your English

Never. Not even once. “Sorry, my English is not perfect” is the single fastest way to cap your offer. The recruiter is fluent. They know your English is not perfect. By naming it, you make it the topic of the call. Skip the apology. Let your answers do the work.

Mistake 4: trying to translate from your native language

If you are mentally composing in Russian or Uzbek and translating word-by-word, your pace collapses and your sentences come out twice as long as they need to be. The fix is tonot startwith the translation. Pick three or four phrases you know cold in English — “the goal of the project was…,” “I owned the…,” “the result was…” — and use them as launch points. Compose the rest in English from there.

Mistake 5: not asking the recruiter to repeat

Counter-intuitive: candidates who never ask “sorry, could you repeat that?” do worse, not better. Recruiters expect a non-native speaker to clarify occasionally. The candidate who never clarifies is the candidate who answered the wrong question.

Use this exact phrase: “Sorry, could you say that one more time, just to make sure I understand?” It signals you care about the answer, not that you missed it.

The four questions that come up in 90% of phone screens

Practice these out loud until they come without effort. Each should land in 60–90 seconds.

  1. “Tell me about yourself.” Three parts: where you are now, the most relevant project, what you are looking for next. Do not narrate your CV. Two minutes maximum.
  2. “Why are you leaving your current role?”Frame as a pull, not a push. “I want to work on consumer-scale products,” not “my team is disorganized.” Never criticize. The recruiter is taking notes.
  3. “What are you looking for in your next role?”Two specific things, connected to what you have heard about the company. “Working with a strong frontend team on a product that ships to real users in Europe” beats “learning new tech.”
  4. “What is your salary expectation?” A specific number, in their currency, not a range. Anchor high but not absurd. Practice saying it out loud once without your voice changing. That is the exam.

The thirty-minute warm-up before the call

One hour before the call:

  • Read aloud for ten minutes from any English source — a recent tech article, someone's blog, anything. This warms up the muscles for English pacing.
  • Watch five minutes of a native speaker on YouTube at 1x speed. Do not pause. Just listen.
  • Drink water. A dry throat changes how you sound by more than you think.
  • Stand up for the call if you can. Pacing is shorter when you stand.
  • Have your CV in front of you, plus three numbers you might need (current comp, target comp, notice period).

What good sounds like

A successful phone screen feels disappointingly normal. Short answers. Specific numbers. One or two clarifying questions from you at the end. The recruiter says “great, the next step is a 60-minute call with our hiring manager next week.”

That is the win. No fireworks, no eloquent speeches, no killer technical detail. Just a calm 30 minutes that ended with a calendar invite.

The one thing that beats every other tactic

Practice phone screens out loud, in English, with someone or something that asks unpredictable follow-ups. Reading this article is not practice. Watching a YouTube mock is not practice. Sitting down, hearing a question, and answering it out loud is the only thing that counts.

NextSuhbat runs phone-screen-style mock interviews in English with real-time feedback on filler words, pace, and answer structure. Twenty minutes once is more useful than ten articles like this one.