Onboarding employees who don't speak English well

Translate the material that has consequences — contracts, safety, compliance, systems access — and accept that the social parts matter more than the documents. Give new joiners written material in their language before any live session, not after.

Onboarding is dense, high-stakes and front-loaded, which is the worst combination for someone working in a second language. It is also one of the few processes where translation has an unambiguous return.

Triage what actually needs translating

Not everything, and the split is usually clear:

Must be translated: employment terms, safety instruction, compliance training people sign off on, anything with a legal or physical consequence. If a misunderstanding here creates liability, translate it properly and keep a record.

Should be translated: systems access instructions, expenses and leave policy, the org chart, who to ask about what. Cheap to translate once, re-read many times.

Usually should not be: the company culture deck. Translating it does not make it land, and the effort is better spent on a person who will answer questions.

Written before spoken

Send material in the new joiner’s language before the live session, not as a follow-up. Someone who has read the outline can follow a spoken session in a second language; someone hearing it cold cannot, and will not interrupt to say so on day one.

This is the cheapest single improvement available in onboarding.

Reduce the density

Standard onboarding assumes a listener who can absorb quickly in their strongest language. That assumption fails, and the fix is not more translation but less compression:

• Spread it out. Four two-hour days beat one eight-hour day for everyone, and dramatically so in a second language.
• Repeat the important things in more than one format. Said, written, and available to look up later.
• Provide a glossary of internal acronyms. Every company has fifty and assumes they are obvious.
• Name one person to ask anything. A new joiner who is unsure whether their question is stupid will not post it in a channel of forty people.

The social part is the part that fails

Practical information can be translated and re-read. What cannot be re-read is the informal conversation where people learn how things actually work — who to trust, what is really urgent, which process everyone quietly ignores.

Someone who cannot follow fast hallway conversation in a second language misses all of it, and looks disengaged while doing so.

Countermeasures that work:

• A buddy who shares their language, if one exists, for the first month
• Written team norms, so the unwritten ones are smaller
• Scheduled one-to-ones with more people than seems necessary, because a scheduled conversation is far easier to participate in than an ambient one

Live translation, where

For the sessions that are genuinely interactive — a systems walkthrough where they need to ask questions, a first team meeting — live translation removes a real barrier during the weeks when the person has the least context to fill gaps with.

Check the limits: Google Meet does one English-anchored pair per meeting with a 90-minute cap; Teams Interpreter covers 10 languages and needs Microsoft 365 Copilot rather than Teams Premium; Zoom gives captions only, not audio. A recorded walkthrough with a translated transcript is often more useful than a live translated session anyway, because the new joiner can replay it in week three when it finally makes sense.