The CV Mistake That Underprices Your Languages

Open your CV and find your languages.

I can almost tell you where they are. Near the bottom, in a tidy row beneath your certifications and somewhere above your interests, set in the same modest font as everything else on the page. "Languages: English (native), Spanish (fluent), French (professional)." Clean. Honest. Complete.

And catastrophically underpriced.

In the previous piece, we worked out what your languages are actually worth — the gap between what the market pays for the capability and what you currently collect for it. Calculating that number is the first move. This is the second, and it is the one almost everyone gets wrong: positioning. Because a value nobody can see is a value nobody will pay for — and the single most common place multilingual professionals make their value invisible is the one document whose entire job is to display it.

Placement is a price signal

Where a thing sits on a CV is not a neutral decision. It is a statement of priority, and the people reading the document — recruiters, hiring managers, decision-makers who spend seconds per page — read priority before they read content. What appears at the top is the headline. What appears at the bottom is the footnote.

By placing your languages at the bottom, in the skills graveyard alongside your software proficiencies, you tell every reader the same thing: this is a nice-to-have. A bonus. And bonuses, as we established, are precisely the things nobody negotiates over, because they were never presented as load-bearing in the first place. The position of your languages on the page is itself a number — and right now, for most people, it is signalling a low one.

A trait, or a capability

The second mistake is subtler than placement, and it lives in the words themselves. "Spanish (fluent)" describes a trait — a static fact about you, like your height. It tells the reader what you have. It says nothing about what you do with it, or what it produces.

Compare it to the version that names the outcome: the deal closed in a second language, the market opened, the client retained, the negotiation that moved because you understood both the words and the room. That is not a trait. It is a capability with a track record — and a capability with a track record is something a buyer can price, because you have shown them the return.

Move it, then reframe it

So the repositioning has two halves.

First, move it. If your work genuinely depends on languages — if the role would not function without them — they do not belong at the bottom of the page. They belong in your professional summary, in the first lines a reader sees, stated as a core competency rather than a closing afterthought.

Second, reframe it. Stop listing the language as a possession and start describing it as a function. Not "fluent in Mandarin," but the specific, concrete thing that fluency did: the market it unlocked, the partnership it secured, the misunderstanding it caught before it cost someone money. Attach a result wherever you honestly can. Numbers where you have them; outcomes always.

Not only on the CV

The CV is where this is most visible, but it is not the only place you underprice yourself — and fixing one document while leaving the rest untouched only goes so far.

Your professional profile online repeats the buried-at-the-bottom pattern by default, and deserves the same treatment. So does the way you describe yourself out loud. "I speak three languages" is a trait. "I run our entire relationship with the Latin American market" is a position. The first invites a polite nod. The second invites a conversation about what that is worth.

Positioning is not exaggeration. You are not inventing a capability; you spent years building a real one. You are simply refusing to file it under miscellaneous.

Stop hiding the number

The market reads priority. It prices what you place in front of it and overlooks what you tuck away — and for most multilingual professionals the tucking-away is so habitual it no longer feels like a choice. It is one. You can keep your most valuable capability at the bottom of the page, in the same font as everything else, or you can move it to the top and describe it as what it actually is.

You already did the hard part. You learned the languages, and you worked out what they are worth. What remains is refusing to hide the number once you have it. The full framework for positioning the capability — and the rest of the system for turning it into income — is laid out in The Language Advantage by Andreas Apollonis.