Last updated: 2026-06-26
Read time: ~7 minutes
Summary: Interpreting is not moving words from one language to another. It is carrying meaning, intent, and relationship from one world to another. After around 100 engagements inside the room doing this work, here is what interpreting actually is — explained through the specific moments where it happens.
A four-word sentence at a negotiation table
We were at a negotiation table in Seoul. The US side finished walking through their proposal. The Korean executive across from them paused, let a beat pass, and said four words: "We'll review it internally."
That sentence had two possible meanings, and they were opposites.
One was genuine. There was real interest, the proposal was worth taking back to the table internally, and this was a signal that a second meeting would follow.
The other was a refusal. In Korean business, saying "we'll review it" is one of the most common ways to decline without ever saying "no" in the room. It keeps the air polite and lets everyone leave with their footing intact.
Same four words. Opposite meanings. And which one it was did not live in the words. It lived in the executive's tone, in the length of the pause before he spoke, in whether his eyes dropped to the documents or stayed on the other side's face, in the temperature of the room.
What I carried into Korean that afternoon was not the dictionary sentence. It was a refusal. I delivered it as a refusal — courteous, but unmistakably closed — so the visiting team would not spend the next quarter waiting on a yes that was never coming.
That is interpreting. It is not moving words.
Interpreting and translation are different jobs
Let me clear up the most common confusion first. Interpreting and translation are not two versions of the same skill.
Translation works with text. It has time. You look things up, you rewrite a sentence, and if a better phrase comes to you the next morning, you go back and fix it. A translator is someone who refines a finished thing.
Interpreting has no time. The moment the speaker finishes — sometimes before they finish — you have to carry it across. There is no undo. Everyone in the room hears your version and immediately acts on it. An interpreter is not refining a finished thing. An interpreter is standing between two worlds in real time, deciding under pressure.
That pressure is the part the word "translate" hides. On an IR call, when a CFO says guidance was "set conservatively," the interpreter has half a second to decide: is this a plain accounting note, or a deliberate signal of caution being sent to analysts? In an M&A session, when one side says a point "isn't a dealbreaker," you have to read whether that is a concession or bait, and load your delivery with the right weight. No dictionary holds that judgment.
Translation is finding the right word. Interpreting is delivering the right meaning — in the moment it is needed.
Modality: carrying the weight of a promise
The place interpreters slip most often is modality — the fine gradations between possibility, intention, and commitment.
English carries these gradations in its words. "We will," "we should," "we might," "we could," "we'd be open to" — each is a different weight of promise, and an English speaker hears the difference instantly. Korean carries that same weight differently: not so much in separate words as in verb endings and context. To an English ear several Korean phrases sound interchangeable, but inside Korean they are almost contractually distinct — the difference between "I will meet the deadline" and "I'll try to meet the deadline."
A real scene. In a supply agreement meeting, the Korean manager said the equivalent of "we'll try to make the delivery date." A careless interpreter renders that as "We will meet the deadline." But "we'll try to make it" is not "we will make it." It is effort offered, not a guarantee given. I carried it as "We'll do our best to meet it." That one-word gap decides whether, weeks later when the date slips, the conversation is a dispute — "you broke your promise" — or an understanding — "you did what you said you'd try to do."
Get modality wrong and you have produced a lie. You have either invented a promise the speaker never made, or blurred one they did. Good interpreting carries not just the meaning of the words but the weight of the commitment riding on them.
Silence has to be interpreted too
Some of what an interpreter carries is not words at all. Silence is the clearest example.
It was a meeting with a Japanese partner. The Korean side put a pricing condition on the table, and the lead on the Japanese side said nothing — just sat with it for three full seconds. The Korean executive couldn't bear the gap and was about to jump in with "we can adjust that."
I held my interpretation for a moment. That silence was not a rejection. In Japanese business, a pause often signals that something is being weighed seriously, and not answering immediately is a form of respect, not resistance. If I had rushed to fill those three seconds as "the other side is hesitating," the Korean team would have offered a concession nobody had asked for.
This is what people mean when they say an interpreter has to "read the room." It is knowing not only what to say but what not to say, and when to let a pause stand. It is knowing that silence means different things in different cultures, and carrying that silence into the other world's language — sometimes by leaving it exactly as it is.
An interpreter who only moves words misses this moment entirely. They hurry to fill the empty space, or mistake a meaningful pause for an awkward one.
Register: the same words, a different distance
Register is the level of formality in how something is said. The same content lands differently depending on who is saying it to whom, and an interpreter has to carry not just the content but that level.
In a room of senior executives, an American principal said, almost tossing it off, "Look, this isn't going to work." Word for word, that is simply "this won't work." But the "Look" carries an easy, almost peer-to-peer bluntness. Carry that exact register straight into a Korean meeting addressed to senior executives and it lands as rude. I kept the firmness and adjusted the register to fit the room: the Korean equivalent of "To be candid, this won't work as it stands."
It runs the other direction too. When the Korean side speaks in highly elevated, formal language and you carry that formality literally into English, it can read to the other side as cold and distant. Korean politeness and English politeness sit on different coordinates; matching the words can miss the relationship.
To carry register is to carry the distance the speaker intended — neither too familiar nor too cold. That is not a vocabulary problem. It is something only a person who holds the social grain of both cultures at once can do.
Why this has to be verified
If you have read this far, one thing has probably become clear. The core abilities of interpreting — the weight of modality, the meaning of silence, the calibration of register, the sense for reading a room — do not appear on a résumé.
"Fluent in English." "Ten years of interpreting experience." "Studied abroad." None of that tells you whether a person can hear "we'll review it internally" and know it was a refusal. A business card can't tell you. A degree can't tell you. A referral from someone you trust can't tell you. The only way to know is to watch the person actually do the work.
This is why I built MetaPret. Interpreting is a job where skill is the whole thing, and yet the interpreting market has matched people without ever checking that skill — by connection, by price, by what the résumé claimed. The one thing that matters most — can this person read the room — only showed up after the job had already started.
I believe that order has to change. When language matters, skill should be the proof. Before the match is made, it should already be clear that the person can carry meaning across, not just words.
If interpreting is not the moving of words — and it isn't — then choosing an interpreter cannot be the comparing of words on a résumé either. Can this person actually carry the meaning? That has to be the standard.
FAQ
Q: What's the difference between interpreting and translation?
A: Translation works with text and has time — you can revise and refine. Interpreting works with live speech and cannot be undone; the room acts on your version immediately. Beyond finding the right word, interpreting means judging the speaker's intent and tone under pressure and delivering it in the moment.
Q: What separates good interpreting from adequate interpreting?
A: The difference between moving words and carrying meaning. Good interpreting carries the weight of modality ("we will" vs "we'll try"), the meaning of silence, the level of register, and the mood of the room — and delivers all of it in the other world's language, not just the literal sentence.
Q: What does it mean for an interpreter to "read the room"?
A: Knowing not only what to say but what not to say, and when to let a pause stand. For example, telling whether a three-second silence from a Japanese counterpart is a refusal or serious consideration, and not rushing to fill it. It is needed because silence and indirect phrasing mean different things across cultures.
Q: If someone is fluent in two languages, can they interpret well?
A: Fluency is only the starting line. Interpreting is a separate ability — holding two languages at once, under real-time pressure, while reading the social grain of both cultures and carrying meaning across. Someone can be fluent in English and still fail as an interpreter if they miss what "we'll review it internally" actually meant.
Q: How do you actually know if an interpreter is good?
A: The core abilities don't show up on a résumé or a degree. You only know by watching the person do the work — whether they carry modality precisely, catch indirect refusals, and calibrate register. That is exactly why MetaPret verifies skill before the match rather than after.
Related
- https://metapret.net/how-it-works
- In-person vs remote interpretation: when each actually works
- Seoul interpreters
- How interpreter matching works on MetaPret