Why “Native-Level Fluency” Might Be Costing You Your Best Hires

A few months ago, someone forwarded me a job listing for a marketing role. Under requirements, in bold: “Native English speaker essential.” The role involved writing product copy, yes, but also managing a team spread across four countries, in none of which English was anyone’s first language.

I read it twice, then thought about who that single line would quietly filter out before a human ever opened a CV: the Dutch copywriter who had worked in English for a decade, the Nigerian candidate whose English was, technically, also a native language, the German applicant who wrote more precisely than most native speakers I know.

“Native-level fluency” turns up in job listings constantly, and it rarely means what it says, which is worth unpacking properly, because the assumption underneath it shapes who gets hired long before anyone reaches an interview.

What “Native-Level Fluency” Actually Asks For

Here’s the problem with the phrase: nativeness isn’t a proficiency level, it’s an accident of birth. Someone can be a native speaker of a language and still write poorly in a professional register, structuring mails clumsily or missing the tone a client expects. Someone else can have learned that same language at fifteen, as a second or third language, and go on to communicate with more precision, clarity, and cultural nuance than most people born into it.

When a job listing asks for native-level fluency, it’s usually reaching for one of a handful of different things, even if the person who wrote it hasn’t stopped to separate them out. Sometimes it means reliable written communication in a professional context: mails that read cleanly, reports that don’t need heavy editing. Sometimes it means comfort thinking on your feet in real-time conversation, the kind of fluency that lets someone hold a negotiation or field an unexpected question without losing their thread. Occasionally it means cultural fluency with idiom and tone, understanding when a joke lands and when it doesn’t. And sometimes, less often admitted, it simply means a vague sense of safety, a feeling that the person will “fit in” without anyone quite defining what that means.

Only the first three of these are genuinely skills that can be named, taught, and tested. The fourth is a proxy, and proxies are where bias creeps in quietly, without anyone setting out to discriminate against anyone at all.

Why Companies Default to “Native” Anyway

This pattern is rarely malicious. “Native speaker” functions as a shortcut. It sounds precise, it’s easy to drop into a job advert on a Friday afternoon when a dozen other things are competing for attention, and it feels like a safe, defensible bar to set. Nobody drafting that line sits down intending to write something discriminatory, and most hiring managers would be genuinely uncomfortable if you suggested they had.

Intent and impact aren’t the same thing, though, and this is where the real risk sits, not only reputationally, but legally. In the United States, the Equal Employment Opportunity Commission has been explicit on this point for years: an English fluency requirement is only lawful if it’s genuinely necessary for the effective performance of the specific role in question, and it has to be assessed position by position rather than applied as a blanket rule across dissimilar jobs. Applying an identical fluency bar to a warehouse role and a senior client-facing role, regardless of what each actually demands day to day, is precisely the pattern regulators flag as indirect discrimination.

In the European Union, requirements tied to national origin fall under anti-discrimination law more broadly. In Germany, that means the Allgemeines Gleichbehandlungsgesetz, generally referred to as the AGG. In the UK, it falls under the Equality Act. None of these frameworks require proof that a company intended to discriminate, only that a requirement had a disproportionate effect on people from a particular national or linguistic background, and a blanket “native speaker” line does exactly that by design.

There is also a cost that has nothing to do with legal exposure at all. Every unnecessary native-level fluency requirement narrows the talent pool for something that, in the great majority of cases, isn’t actually the thing the company needs from the role.

What to Ask For Instead

Before writing “native speaker” into your next job listing, it’s worth sitting with three questions, ideally alongside whoever will actually be working with the new hire, not just whoever happens to be drafting the listing.

What’s the actual task?

A role built around spontaneous client calls needs real-time fluency under pressure. A technical writing role needs precision and consistency far more than it needs speed. A customer support role might need patience and clarity more than either. These are different requirements, and “native speaker” answers none of them particularly well, because it was never designed to measure any of them in the first place.

Is there a proficiency framework that says this more precisely?

The CEFR scale, running from A1 through C2, exists for exactly this reason, offering a shared, testable vocabulary for language ability. “C1 or above, with strong written communication skills” is specific, it’s testable through an interview or a writing sample, and it doesn’t quietly exclude a highly proficient non-native speaker who happens to have learned the language as an adult rather than as a child.

And, perhaps most usefully: would a native speaker with weak skills in this particular area actually pass your bar, and would a highly proficient non-native speaker actually fail it?

If the honest answer is that your native-level fluency requirement wouldn’t survive contact with real candidates sitting in front of you, it isn’t measuring what you think it is, and it’s doing quiet harm every time it sits in a new listing.

Writing Job Listings That Don’t Lower the Bar

Being precise about what the standard actually is tends to raise the quality of who applies rather than lower it, which is worth saying plainly, since that’s usually the first worry that surfaces when this topic comes up in a hiring conversation.

In practice, that means swapping “native English speaker” for something like “C1/C2 English, written and spoken,” or “professional working proficiency” if that fits the role better. It means naming the specific skill the role needs rather than reaching for a birthplace-based proxy: “comfortable leading client calls in English” tells a candidate, and whoever is assessing them, something concrete that can actually be tested in an interview. If accent genuinely matters for a role, voice acting or dialect coaching being the obvious examples, it’s worth saying so explicitly and being ready to justify why, rather than folding it quietly into a general fluency requirement that ends up screening out far more than intended. And wherever possible, it means testing the actual skill directly, through a short writing sample or a real conversation, rather than inferring it from where someone happened to grow up.

The goal is a bar that measures what the role genuinely needs and lets the strongest candidates clear it on merit rather than birthplace, which tends to be better for the company as well as fairer to the people applying to work there.

Ready to Rethink Your Hiring Language?

Every job listing sends a signal about who belongs in your organisation before a single interview takes place. With a closer look at how requirements are written and assessed, companies can widen their candidate pool, reduce legal exposure, and still hold a genuinely high bar.

If you’re navigating questions, challenges, or goals around multilingualism, whether in your hiring, your team’s day-to-day communication, or your organisation’s wider culture, I offer tailored consulting sessions that focus on practical, workable change.

You can book a free 30-minute call or find more information about my work and current offers on my website. I also share ongoing insights and resources on Instagram, Facebook, and LinkedIn. I’d love to see you there!

FAQs