What does a Language Lead actually do?

Tell someone you’re a Language Lead and you’ll get one of two reactions. Either a confident nod that clearly means “no idea, but sounds senior,” or the honest follow-up: “so… you’re a translator?”

Not quite. And the gap between those two things is the whole job.

So let’s clear it up honestly, unglamorous parts included. Because the role is genuinely useful, genuinely misunderstood, and (I’ll admit) genuinely hard to explain at parties.

The one-sentence version

A Language Lead owns a language inside your product. Not a project. Not a batch of strings. The language (its quality, its consistency, its voice, across everything) as the product grows.

A translator is handed strings and translates them. A Language Lead is responsible for what French is in your product: how it sounds, which words you use, whether it stays coherent when five different people touch it over two years. One does a task. The other owns an outcome.

An analogy, because I can’t resist one. A translator lays bricks, skilled, essential work. A Language Lead is closer to the architect who’s responsible for the building still standing, looking right, and not having three incompatible staircases because nobody was keeping track. Both matter. They’re not the same job.

What that actually looks like, day to day

Here’s where the mystique dissolves into the real work. A Language Lead:

Builds and guards the style guide. Tu or vous? Formal or warm? How do we sound when something goes wrong? These decisions get made once, written down, and (the hard part) actually enforced.

Example: your English error message says “Oops! Something went wrong.” A Lead decides whether French keeps that playful “Oups !”: great for a casual consumer app, faintly unserious for a B2B payroll tool where users are handling money and would prefer a calm Une erreur est survenue. Same source string, opposite right answers, one person making the call consistently.
Owns the glossary. Every product has its words: feature names, domain terms, the things that must always translate the same way.

Example: you have a feature called Workspace . Is it Espace de travail everywhere, or does it stay Workspace? Whichever you pick, it can’t be both. Not Espace de travail in the menu and Workspace in the help center and espace in an email. Multiply that by every key term in your product and you’ll see why someone has to own the list and defend it against the slow entropy of “eh, close enough.”

Makes the calls no one else can. Should this term stay in English? Does this CTA need rewriting rather than translating?

Example: “Get started” translated literally is Commencer: correct, and flat. Depending on your brand, the right French might be C'est parti , Démarrer or Créer mon compte. A rewrite, not a translation, chosen to actually convert. Or take seat as in a license seat: siège would be nonsense; the real French is closer to licence or utilisateur . A Lead knows the difference and picks on purpose.
Reviews in context. Not in a spreadsheet, where every string looks plausible. In the live UI, where reality bites.

Example: Wishlist fits neatly on your button. Its honest French, Ajouter à ma liste de souhaits is nearly four times longer and cheerfully bursts out of the box. You only catch that by seeing it in place, which is exactly where a Lead reviews, not in a tidy column of strings that all look fine in isolation.
Coordinates other linguists. On bigger projects, the Lead briefs translators, answers their questions, and reviews the result, so ten people produce one consistent voice instead of ten slightly different ones. Without that, you get a product where the tone quietly changes every time a different freelancer picked up a batch. Users can’t name it, but they feel the seams.
Bridges language and engineering. Flagging the hard-coded string, the layout with no room for French to breathe, and the classic: English plural logic.

Example:

Keeps it coherent over time. Products don’t stop. New features, new strings, new edge cases… forever. The Lead keeps French consistent release after release, so version 40 still sounds like version 1, and the term you carefully chose in January hasn’t quietly mutated into three variants by June.

The honest, unglamorous truth

Since you’re still reading, you’ve earned the real talk.

A lot of this job is not thrilling. It’s updating a glossary. It’s catching the same misused term for the fortieth time and gently fixing it again. It’s writing a style-guide entry about whether numbers get a non-breaking space before the euro sign (they do) that maybe three people will ever read. Much of the best work is invisible. You only notice a Language Lead’s contribution when it’s missing, which is a strange kind of success to build a career on.

It’s also part diplomacy. You’re often telling people (kindly) that their favorite headline doesn’t work in French, or that “we’ll just machine-translate the help center” is going to cost more later than it saves now. Being right isn’t enough; you have to be right and easy to work with.

And it’s rarer than it should be. Plenty of companies don’t know the role exists, or fold it into “we have a translator.” Which is fine, right up until their French sounds like it was assembled from three different products by people who never spoke to each other. Because it was.

When do you actually need one?

Not every company does. If you’re translating a one-page site once, hire a good translator and call it a day. You need a Language Lead when:

Your product is ongoing: you ship features constantly, and French has to keep up.
Consistency matters: multiple people touch the language, and it’s starting to show (the same term translated three ways is the classic first symptom).
The stakes are higher than “readable”: your French is part of your brand, your conversion, or your compliance.
You want one accountable person for a language, not a rotating cast and a hope.

That’s the moment a Lead stops being a nice-to-have and starts paying for itself: in coherence, in trust, in the French your users don’t consciously notice because nothing is wrong.

The short version

A Language Lead owns a language the way a good editor owns a publication’s voice: making a thousand small, consistent, mostly invisible decisions so the whole thing feels like it came from one confident mind. Not a translator. Not a reviewer. The person accountable for what your product sounds like in French, today, and forty releases from now.

Which, it turns out, is a lot harder to fit on a business card than “translator.” I’m still working on the party version.

Want the full picture? I’ve put together a guide to the Language Lead role: the complete list of responsibilities and deliverables, what to look for when hiring one, and how the role fits alongside your existing team. Get in touch and I’ll send it your way. And if French is the language you’re trying to get right, well… you know where to find me!