The Language Barrier Myth

I watched a hiring manager reject a candidate last year for "communication issues."

The candidate had a master's degree in finance from a top university in LATAM. She'd managed a team of twelve at a multinational bank. She had negotiated vendor contracts across four countries. She spoke English and Spanish.

The hiring manager spoke one language. His feedback after the interview was three words: "Hard to understand."

I asked him to be more specific. Did she struggle to explain her experience? No. Did she misunderstand any of his questions? No. Could she not articulate her approach to the role? She actually gave one of the more detailed answers he'd heard all week.

So what was the communication issue, exactly?

She had an accent.

That was it. That was the whole thing.

"Strong Communication Skills Required"

Go look at your last five job postings. I'll bet at least three of them list "strong communication skills" as a requirement. Maybe all five.

Now ask yourself what that actually means.

Because in theory, it means the person can convey ideas clearly, listen actively, collaborate with a team, write a coherent email. Those are legitimate skills. Nobody's arguing with that.

But in practice -- and I say this having reviewed thousands of candidate scorecards across hundreds of companies -- "communication skills" has become the most socially acceptable way to reject someone for not sounding like the people already in the room.

Nobody writes "accent" on a scorecard. That would be too obvious. They write "communication." They write "culture fit." They write "might struggle with client-facing work." And everyone nods because it sounds reasonable.

It's not reasonable. It's bias with a dress code.

Let's Talk About What Communication Actually Is

I've placed candidates from over thirty countries in the last two years. You know what I've noticed about the ones who get flagged for "communication issues"?

They're often the strongest communicators in the entire candidate pool.

Not despite speaking multiple languages. Because of it.

When you grow up navigating between languages, you develop a skill that most monolingual professionals never build: the ability to read a room across cultural contexts. You learn that the same word means different things to different people. You learn to adjust your tone, your pacing, your framing based on who you're talking to. You learn to listen harder because you've spent your life in environments where assumptions get you in trouble.

That's not a communication deficit. That's a communication superpower.

The candidate I mentioned earlier? The one who got rejected for being "hard to understand"? She had spent five years managing teams that spoke three different languages across two time zones. She had presented quarterly results to an international board of directors. She ran client meetings in French on Tuesday and English on Thursday.

But she didn't sound like the other accountants in Mississauga, so she got a no.

The Business Case You're Ignoring

Here's where this gets expensive.

Canada's demographics are shifting fast. Roughly 500,000 new permanent residents arrive each year. In the Greater Toronto Area alone, more than half of residents were born outside Canada. Your customer base, your vendors, your partners -- they're increasingly multilingual and multicultural.

So when you screen out a candidate because their English sounds different, you're not just being unfair. You're being strategically stupid.

That candidate who speaks Mandarin and English? She can help you break into a market segment your competitors can't touch. The project manager who speaks Arabic and French? He's the reason your Montreal client finally feels heard. The sales rep who grew up code-switching between Hindi and English? She reads rooms better than anyone on your current team because she's been doing it since she was five.

Companies that get this -- that treat multilingual ability as a competitive advantage rather than a red flag -- are building teams that can actually serve a diverse market. The ones that screen for accent are building teams that feel comfortable. Those are not the same thing.

The Hiring Manager Problem

I want to be fair here. Most hiring managers who reject candidates for "communication" aren't doing it maliciously. They're not sitting in the interview thinking "this person has an accent, I'm going to tank them." It's more subtle than that.

They're pattern-matching. They have a mental model of what a "strong communicator" sounds like, and that model was built from every colleague, every boss, every client they've ever worked with. If those people all sounded a certain way, then "good communication" starts to mean "sounds like the people I'm used to."

That's not evil. It's human. But it's still a problem, and it's your job as a leader to interrupt it.

Here's what I tell every hiring manager I train: if you're about to flag someone for communication, ask yourself one question first. "Did this person successfully convey their ideas and answer my questions?" If the answer is yes, then your issue isn't with their communication. It's with their delivery. And delivery is a preference, not a qualification.

What to Do Instead

If you actually want to assess communication skills -- real ones, not accent preferences -- here's how.

Separate content from delivery. After every interview, ask yourself: "Did I understand what they said?" Not "did I like how they said it." If you can summarize their answer back to yourself, they communicated. Full stop.

Test for the skills that matter. If the role requires client presentations, give them a short presentation exercise. If it requires written communication, ask for a writing sample. Don't use a thirty-minute conversation as a proxy for skills you never actually tested.

Check your scorecards for coded language. If multiple interviewers are using phrases like "not polished," "might struggle externally," or "didn't click" -- and this keeps happening with candidates who have accents -- you don't have a talent problem. You have a bias problem. Name it. Address it.

Redefine "communication skills" in your job postings. Instead of the generic phrase, say what you actually mean. "Able to explain technical concepts to non-technical stakeholders." "Comfortable presenting to groups of 10-20." "Strong written communication for client-facing reports." Be specific. Specific requirements attract qualified people. Vague requirements attract whatever bias the screener brings with them.

The Question I Keep Coming Back To

That candidate I mentioned at the top -- the one who speaks two languages, managed international teams, and presented to a global board?

She eventually got hired. Different company. Same city. She's now one of their top performers. Her manager told me last month that she's the best hire they made all year.

The first company? They're still looking to fill the role. It's been eight months.

I think about that a lot. Not because it's unusual. Because it happens every single week. Companies reject exceptional talent because that talent doesn't sound like what they expected. Then they complain about a "talent shortage" while multilingual, multicultural, deeply qualified candidates go build someone else's company.