You have the certificate. You read technical documentation in English all day, you write your reports in English, and nobody has ever complained about your emails.

Then the colleague from the Dublin office joins the call. Forty minutes later, you have caught maybe half of what was said, and you are not sure which half.

That gap is not a sign that your English collapsed. It is a sign that nobody ever tested the skill you are now being asked to use.

The exam did not test this

Noelia Gozalo is an engineer with more than 10 years of experience in automotive and renewable energy. In 2010 she moved from Spain to Ireland to do her full engineering degree in English, and she did not arrive unprepared. She had studied for years at the official School of Languages in Spain. She had passed the English exams required for the move, including the speaking test.

Then she sat down in a strength of materials lecture and understood nothing.

She was not an Erasmus student. There was no softer version of the course waiting for her. She had to follow the lectures, pass the assignments and sit the same exams as everyone else, and for the first three months she could not reliably follow a conversation with the people sitting next to her.

Nothing had gone wrong with her English. She had trained and tested one set of skills, and the lecture theatre asked for a different one. Grammar, reading and writing can all be excellent while listening lags years behind. The CEFR describes listening and reading as separate competences with their own scales, which is why "my English is B2" was never really one number.

You may already know the feeling from the other direction. If you have ever worried that your own accent is the problem, that is a separate question with a separate answer: does your accent hold you back at work? This article is about the opposite situation: understanding everyone else.

It is not your vocabulary

When I asked Noelia whether the problem was her English level or the Irish accent, her answer was "a bit of both." The accent was strong. And people talked fast.

That combination is the whole problem, and neither half is about how many words you know.

Think about the English you were trained on. One speaker at a time. Careful pronunciation. A script, or something close to it. No background noise, no interruptions, nobody finishing somebody else's sentence. Recordings you could play twice.

Now think about a project call. Three people talking over each other, one of them on a bad connection, somebody eating lunch, and a decision being made in the four seconds before the next topic starts.

Same language. Completely different listening task.

Two things are doing the damage:

• Speed and connected speech. Fluent speakers do not say words one at a time. They run them together, drop sounds and swallow whole syllables. "What do you want to do" comes out closer to "whaddaya wanna do." You know every one of those words. You would recognise all of them written on a page. You just never hear them in that shape.
• Regional variation. There is no single native accent to prepare for. Irish, Scottish, Australian and Texan English are four different listening problems, and the version you studied is probably a fifth. Add your international colleagues, because a French engineer and a Japanese engineer speaking English will each challenge your ear in a different way: international team communication.

This is why the advice to "learn more vocabulary" misses. You are not missing the words. You are being asked to recognise words you already know, at a speed and in a shape you have never practised.

The good news is that this is a trainable skill and not a fixed limit. Exposure does most of the work, which is why watching things in English does more for your ear than another vocabulary app: TV shows to learn English.

The bad news is what most of us do while we wait for our ear to catch up.

The yes trap

Noelia's colleagues in Ireland would try to talk to her, and she could barely follow. So she said yes.

Yes to everything, for months. She calls it funny now. It was not funny at the time.

Almost every engineer working in a second language has done some version of this. You miss a chunk of what was said, the speaker looks at you, and you have about one second to decide. Ask them to repeat it and admit in front of the room that you were lost. Or nod.

Nodding is faster. Nodding costs nothing right now. That is exactly the problem: the cost arrives later, and it lands somewhere else.

Here is what you actually agreed to when you nodded:

• A deadline you did not hear correctly
• A scope change nobody wrote down
• An action item that is now yours
• A number you will use in a calculation next week

And you often will not find out on the day. You find out when you sit down with the meeting notes the next morning, read the line with your name next to it, and realise that is not what you thought you were agreeing to.

By then the thing has moved. The client has been told. Somebody has started ordering. Two other people have planned their week around it. Walking it back now means explaining that you agreed to something you did not understand, twenty-four hours after the room watched you nod, so most people do the arithmetic and decide it is cheaper to absorb it and say nothing.

That is how a one second decision in a meeting turns into a week of unplanned work.

And nobody in that meeting knows. From the outside, a nod is a nod. The person speaking has no reason to slow down, rephrase or check, because you have just told them everything landed. The yes trap is not a language problem. It is a data problem, and you are the one introducing the error.

On a construction site or a commissioning floor, that stops being an administrative annoyance. A misunderstood instruction is a hazard. This is the same reason I keep arguing that clarity in technical communication is a safety requirement rather than a style preference, and it works in both directions: clear writing protects the reader, and honest listening protects everyone downstream.

There is a second cost, quieter than the first. Every nod trains you to stay silent. You get slightly better at hiding that you are lost and no better at not being lost, and after a year of that you are the person who never asks anything in meetings. That is a hard reputation to shed, and it has very little to do with your actual English: when you are fluent on paper but stuck in the room.

So the fix is not to understand more. Not immediately. The fix is to stop pretending.

What to say when you lose the thread

The one second decision is not really "to nod or to admit failure." It only feels that way because you have never had the words ready.

So have them ready. Not one panic phrase, but a few, sorted by what you actually missed. That distinction matters more than the politeness of the wording, because "sorry, can you repeat that?" makes the speaker start the whole thing again from the top, and by the time they reach the part you missed, you have lost the new bit too.

When you missed one specific thing:

• "Sorry, which date was that?"
• "Can you give me that number again?"
• "Who is taking that one?"

Name the gap. You get a five second answer instead of a two minute replay, and you sound like someone tracking the detail closely rather than someone drowning.

When you followed the words but not the meaning:

• "Just so I have it right, you want the report before the review, not after?"
• "So we are changing the scope, or only the deadline?"

This is the most useful move in the whole list. You repeat back what you think you heard and let the other person correct it. Nobody hears this as weak English. They hear it as someone confirming requirements, which is what careful engineers do in every language.

When they are simply going too fast:

• "Can we slow down for a second, I want to get this exactly right."

Note what that sentence does not say. It does not say your English is the problem. It says accuracy is the priority, and that is not an excuse, it is true.

When it is over and you are still unsure:

• "Can you put that in a message so I have the numbers?"

Written confirmation is not a defeat. Half your colleagues are asking for the same thing for their own reasons.

If you are in the room rather than on a call, you have more help than you think. Noelia made the point that even imperfect English lands fine in person, because your face is doing half the work. A smile and open body language keep a blunt question from sounding rude, which is a reasonable trade for the risk of getting a number wrong. Politeness matters far more than perfect grammar, as tone and word choice do the real work in international teams.

One last thing worth saying plainly. Asking a speaker to repeat a figure is a completely normal thing for a native speaker to do. Nobody assumes their English is poor. They assume they were not listening properly for a moment, which happens to everyone, in every language, in every meeting.

You are allowed the same assumption.

Nobody teaches engineers this

You did not learn it at university, where the group projects meant to teach communication mostly taught you how to divide a task into five. You probably did not learn it in your first job either, because the person who was supposed to show you the ropes had their own deadlines. Some engineers get a good mentor early and pick it up by watching. Most do not, and end up working it out alone, years later, usually after something has gone wrong in a meeting.

If nobody is going to hand you that, you choose your own development instead. And communication is the piece worth choosing first, because everything else you do at work moves through it. The calculation is only as good as the version of it that reaches the client.

That is the part I teach. Grammar and vocabulary are in there too, because one engineer needs a grammar top-up and the next one needs the words for their field. But that is decided by what you actually need, not by a syllabus. What every engineer I work with needs is the confidence to speak and to ask, in real meetings, with real colleagues, at real speed.

If you recognised yourself somewhere in this article, book a free 15-minute call. Tell me what happens in your meetings and I will tell you honestly whether I can help, and what that would look like.

No preparation needed. Come as you are.

Frequently asked questions