A reader asks: I'm the only non-native English speaker on my team

The question (paraphrased):

I joined a tech company in the US six months ago and I’m the only non-native English speaker on my team. My English is fine — I interviewed in English, I can do my job — but in meetings I feel like I’m always half a beat behind. By the time I’ve figured out what I want to say, the conversation has moved on. Then I either stay quiet or jump in awkwardly. What do I do?

First: this is one of the most common experiences for foreign professionals in the US, and the fact that nobody’s talking about it at work doesn’t mean nobody on your team has noticed it. They probably have. Which is part of why it feels like something is wrong.

Second: the solution isn’t “improve your English.” Your English is fine. The bottleneck isn’t language. It’s meeting tempo.

What’s actually happening

Native speakers in an American meeting are doing three things at once: listening to what’s being said, watching for their moment to jump in, and constructing their sentence as the moment approaches. When you’re native, these happen in parallel with very little cognitive cost.

When English is your second or third language, construction takes real effort. It’s not that you don’t know what to say. It’s that by the time the sentence is fully built in your head, the topic has moved. This is exhausting in ways that your native-speaker colleagues genuinely can’t feel.

Here are the techniques that help — roughly ordered by how quickly they pay off.

1. Prepare two sentences before the meeting

If you know what the meeting is about, write down two things you want to say before it starts. Literally two sentences, on a notepad.

• One sentence that’s about the work. “I think the Q3 drop is mostly driven by the pricing change, not the channel.”
• One sentence that’s about the people. “Nice to have Priya back — how’s the new role?”

You don’t have to use them. But having them pre-built removes the construction step for the moments you’d otherwise miss. They’re your on-ramp.

Senior native speakers do versions of this too. The difference is you need to be more deliberate about it.

2. Use “I want to come back to something” as a reset

The biggest unfairness in a live meeting is that once a topic has moved past, you can’t really go back. American meetings respect whoever has the floor right now.

Except: there’s one phrase that resets the stack, and senior people use it all the time.

“I want to come back to something Sarah said a minute ago — she mentioned the pricing change, and I think that’s actually the core issue. Can I say one thing about it?”

That sentence buys you back the airtime you missed. It’s a senior move — it takes the meeting backward on purpose — and it works for everyone. But it works disproportionately well for people whose construction time is longer, because it removes the “it has to be right now” pressure.

Use this phrase. Twice a meeting, if needed. Nobody minds.

3. Write more where writing beats speaking

If your job has a written layer — docs, status updates, post-meeting summaries, Slack threads — lean into it. Written communication removes the tempo problem entirely. You can draft, re-read, edit.

Many of the most impactful contributors on distributed teams are the strong writers, not the strong talkers. If you’re a better writer than speaker in English, that is an asset, not a weakness. A tight written proposal that lands a decision is worth more than a fluent meeting comment that doesn’t.

This is also the move for the follow-up. Say one thing in the meeting. Then send a two-paragraph follow-up Slack message with the full thought. “Wanted to build on what I said in the meeting — here’s the fuller version.” You get credit for both.

4. Ask, specifically, for a pre-read

If your team is running meetings with no documents in advance, push for pre-reads. Not because of your English — because pre-reads make meetings better for everyone. Ask your manager: “Could we try doing a one-page pre-read before these reviews? I find the conversations get to the substance faster.”

Pre-reads are a 10x multiplier for a non-native speaker. You get to process the argument before the room does. You come in knowing what you want to say.

5. Stop apologizing for your English

This is the one I’d fix first if I were you. If you open any comment with “sorry, my English is not perfect” or “excuse my accent,” you are pre-telling the room to discount what you’re about to say. They will. Not consciously. But they will.

Your English is fine. You interviewed in English. You got hired. You don’t have to defend it. Say your thing, stop, let people respond. If someone needs you to repeat something, they’ll ask.

The one thing that is fine to say, and actually helps, is: “one second — I’m finding the word.” That’s a specific, one-off callout, and it buys you three seconds without lowering anyone’s opinion of you. The blanket apology does the opposite.

What doesn’t help

• “Pretending to be native.” Don’t force idioms you’re not sure about. Don’t slang. You’ll hit a note that lands wrong, and you’ll be less yourself. Speak formally if that’s more natural. Formal registers are always acceptable in an American office.
• “Staying quiet and hoping to speak up later.” The later doesn’t come. Meetings end, and the people who didn’t speak are, quietly, filed as people who didn’t speak. Say one thing, even if it’s small.
• “Taking an English class when the issue is tempo, not vocabulary.” Classes are fine, but if your problem is meeting rhythm and not grammar, a class won’t fix it. Practice meetings will.

What a good month looks like

By the end of month one of practicing this:

• You’ve prepped two sentences before every meeting.
• You’ve used the “I want to come back to” reset at least once a week.
• You’ve sent one written follow-up after a meeting where you said less than you wanted to.
• You’ve stopped apologizing for your English entirely.

You won’t feel like a different person. You’ll feel like a slightly more deliberate version of the same person. That’s the right change.

Edge cases

• If your accent is a real comprehension issue for some colleagues: ask one trusted peer to tell you the three words people most often mishear. Practice those. Do not try to overhaul your accent. The specific high-frequency misses are the 80/20.
• If you’re the only foreign hire on a small team: find a peer in another team, or another company, who’s been through the same transition. The conversations are different when the other person has lived it. Culturally-adjacent peers are one of the most underrated resources you have.

Do this today

For your next meeting, write two sentences on a piece of paper before you join. One about the work, one about the people. Use at least one of them in the first fifteen minutes. Watch what happens.

For the broader set of week-one adjustments that affect how foreign hires are read, see three things every foreign hire should do in week one. For the baseline communication rules, see should you send an email or a Slack?.

—

If you have a question like this, send it in and it may become a Reader Q column. Anonymity guaranteed.