There's a particular kind of exhaustion that doesn't show up in any project report.
It hits engineers at the end of a meeting where they understood about 70% of what was said, said half of what they meant, and spent the entire hour translating — not just words, but tone, subtext, and cultural signals — in real time.
If that sounds familiar, this one's for you.
I spoke with Candice Lee on the English for Engineers podcast about exactly this. Candice has worked in international business communication and relocation since 2011, helping executives and specialists from companies like BMW, Google, and PwC navigate life — and work — in a new country and a new language. She's seen the full picture: the anxiety, the miscommunication, the breakthroughs, and everything in between.
One thing she said has stuck with me: "Make sure your ideas shine through."
That's the whole game, really. Not perfect grammar. Not flawless pronunciation. Just get your ideas across. Below, we break down the most common communication challenges for non-native English speakers on international teams — and what both sides of the conversation can do about it.
The Challenges Non-Native Speakers Face (That Most People Don't Talk About)
Even when someone's English is genuinely good, they're dealing with a layer of cognitive load that their native-speaking colleagues simply aren't. Here's what that looks like in practice.
Jargon and Idioms
Native speakers use idioms constantly — and most of the time, they don't even realise it. Candice herself was surprised when she found out how many expressions she used that her international clients simply didn't understand (went right over their heads — which, yes, is also an idiom: it means the meaning didn't land, like something flying above someone before they can catch it). Her fix? She started asking: "Do you have this saying in your country?" — which opens a door instead of closing one. If they don't know it, they get to ask. If they do, you've found common ground.
For non-native speakers: Ask for clarification without apology. In an international setting, this is not a sign of weakness — it's a sign of professionalism.
For native speakers: Audit your own speech. You probably use more idioms than you think. Slow down, offer context, and make it normal to talk about language.
Nuance and Tone
When you're working in your second, third, or fourth language, you're already busy just finding the right words. You don't always have the bandwidth — the mental energy — to also find the kindest way to say something. The words come out functional — but not always warm.
This creates a real problem in written communication especially. Candice mentioned working with clients whose emails came across as blunt and demanding, to the point where she genuinely worried about the working relationship. Then she met them in person, and they were lovely.
The emails weren't rude. They were just written the way those clients wrote in their native language, where that register is perfectly normal.
For non-native speakers: Tone matters more than grammar. An email full of spelling mistakes that reads warmly will get you further than a perfectly structured one that sounds cold. Use greetings, use softeners ("Would it be possible to…"), use a closing line.
For native speakers: If something reads as blunt or abrupt, assume it wasn't intentional. Ask for a quick call before you assume the worst.
Finding the Right Words in Real Time
This is the one that costs the most energy. You've said this sentence a thousand times — in your own language. Now you have to reconstruct it from scratch, on the spot, while someone is waiting.
You compromise. You find a workaround. You get the point across, but not quite the way you would have in your native language. And you do this all day.
As Candice put it: "It's sometimes being a little creative and compromising to get your point across."
For non-native speakers: Give yourself grace. Getting the idea across is the win. The elegance comes with time.
For native speakers: Give non-native speakers time. Seriously — don't jump in. Don't finish sentences. Wait.
Confidence (or the Lack of It)
Here's the thing nobody says out loud: you can be a world-class engineer and still feel like a fumbling student the moment you have to speak English in a meeting. The expertise doesn't disappear — but it can feel like it does.
Candice shared an example from her work: a Korean executive she was helping with relocation who was desperately hoping she spoke Korean, just so he could finally relax. He was sharp, capable, experienced — and exhausted by the performance of communicating in a language that wasn't his.
For non-native speakers: 99% of the time, you will be understood. Especially on an international team, which expects variety and is listening for ideas — not perfection. Let the idea be the main event.
For native speakers: Don't judge someone's intelligence by how they speak. And don't interrupt, correct, or talk over them.
Writing in English
Spoken and written English are different animals. And written communication across cultures carries huge potential for misunderstanding — not because anyone is being rude, but because email norms vary wildly by culture.
I see this all the time with German engineers. A perfectly acceptable German-style email — direct, no pleasantries, straight to the point — reads as cold and almost aggressive in English. They're the nicest people. Their emails just don't know that yet.
For non-native speakers: Lead with warmth. Even one line of small talk or a polite opener changes the entire read of an email. Grammar errors are forgivable. Tone that reads as dismissive is harder to come back from.
For native speakers: If a written message seems blunt, offer to jump on a call. The relationship is probably fine.
Understanding the Culture (Not Just the Language)
Language and culture are not the same thing — and knowing one doesn't automatically give you the other. Some cultures communicate indirectly; others are extremely direct. Some avoid the word "no" entirely. Others say exactly what they mean, every time.
The fastest way to pick this up? Watch and listen. Patterns emerge quickly when you pay attention.
For non-native speakers: Cultural fluency comes with exposure. Be patient with yourself — and curious about others.
For native speakers: If you can see someone navigating a cultural norm they're not familiar with, help quietly. You don't need to make a production of it.
Finding People Who Get It
This is the one that tends to be invisible from the outside. When you're working in a second, third, or fourth language, you never fully switch off. There's no moment in the workday where you get to just exist without also translating.
That's draining in a way that's hard to explain to someone who hasn't done it. And it's exactly why finding a community — even just one colleague who's been through it — makes a significant difference.
For non-native speakers: Seek out people who understand. Not necessarily from your own country — just people who've done the bilingual work thing and get it.
For native speakers: Make the effort to include people. Show them around. Introduce them. Make the social side of work less of a puzzle.
A Practical Checklist for International Teams
If you're leading or working on an international team, here are five concrete things that make a real difference:
1. Slow down — and mean it.
Not performatively slow. Actually slow. Clear pronunciation and considered pacing help non-native speakers process what's being said — and they reduce jargon creep at the same time.
2. Make language something the team talks about.
Normalise the conversation. Ask what an expression means. Say, "I realise that's a very British phrase — let me rephrase." When language becomes a shared topic rather than a source of shame, the whole team communicates better.
3. Give people time to speak.
Non-native speakers often need a beat longer to formulate what they want to say. That pause isn't hesitation — it's precision. Let it happen.
4. Build common ground deliberately.
Candice's move — asking "do you have this saying in your country?" — is a small act with a big effect. It levels the playing field, invites curiosity, and shows that you're aware of the gap. Try it.
5. Assume good intent — always.
Different communication styles will occasionally clash. Emails will read as blunt. Phrasing will land oddly. Before assuming the worst, assume a translation is happening — because it probably is.
Idiom Glossary
You may have noticed a few idioms scattered through this article. Here's what they actually mean:
| Idiom | What it means |
| Go over someone's head | The meaning didn't land — the person didn't understand it |
| Have the bandwidth | Have the mental energy or capacity to do something |
| Open a door | Create an opportunity or make something easier to start |
| Give yourself grace | Be kind to yourself; don't expect perfection |
| Make a production of it | Overdo it; make something into a bigger deal than it needs to be |
| Get the point across | Successfully communicate your idea, even if not perfectly |
| Level the playing field | Make things more equal or fair for everyone involved |
FAQ: International Team Communication for Non-Native Speakers
It's a cognitive load issue. Speaking in a second, third, or fourth language requires constant mental effort — translating, selecting words, monitoring tone — all while trying to contribute technically. That effort is invisible to native speakers but very real to the person doing it.
Using idiomatic language without realising it. Phrases like "let's circle back," "get our ducks in a row," or "blow it out of the water" can be completely opaque to someone from another language background — and most native speakers use them constantly without even noticing.
No. Warmth and clarity matter far more in professional settings. An email with a few grammar errors that reads as kind and collaborative will land better than a grammatically perfect message that feels cold or blunt.
Make language a normal topic of conversation. Ask what expressions mean. Share your own confusion. When it's normal to say "I didn't quite follow that," everyone — native or non-native — communicates more clearly.
It varies enormously, but consistent exposure to real work situations is the fastest path. The gap isn't usually vocabulary — it's confidence, cultural fluency, and the ability to communicate under pressure. That comes with practice in the right context.
.
Want to Go Deeper?
If this resonated, the full conversation with Candice is well worth a listen — we cover idioms in real time, relocation challenges, and what it actually looks like when someone's rebuilding their professional identity in a second, third, or fourth language. And if you want to know which culinary highlight from Maryland our friendship is based on, you'll have to tune in to find out. Listen to the episode here.
And if you're an engineer wondering how to close the gap between what you know and how it comes across in English, book a free discovery call. We'll talk through where you are, what's getting in the way, and what actually helps.
Also worth reading: How to Work in an International Engineering Team: Practical Tips That Actually Work
0 Comments