How to List Languages on a Resume Honestly

Why the usual words fail

Fluent, proficient, conversational, basic. Four words, no shared definition, and each one interpreted differently by every person who reads it. One candidate writes "conversational Spanish" meaning they can hold a meeting; another writes it meaning they can order lunch. The hiring manager cannot tell the difference until the call, and by then one of the two has a problem.

The fix is not to abandon plain language but to anchor it. Give a framework level, or give a concrete statement of what you can actually do, or both. Either turns an adjective into a claim that means the same thing to everybody.

The three frameworks worth knowing

You do not need to have sat a formal exam to use these scales — they are descriptive frameworks, and self-assessment against a published descriptor is normal and expected. What matters is that you read the descriptor honestly and use one scale throughout.

The ILR scale descriptors and the ACTFL proficiency guidelines are both published in full and worth reading before you assign yourself a level. They are more demanding than most people assume — the top bands of both describe an ability well beyond ordinary comfortable conversation.

Where the section goes

Placement is a judgement about relevance, and languages have the widest swing of any optional section: the same fact can belong in the second line of the page or in the last.

• The posting requires the language. Put it in the summary and again in a short languages block near the top. This is a hard requirement being screened on, and there is no reason to make anyone hunt.
• The employer is international or the role is client-facing across markets. A dedicated section in the upper half of the page, or a line in the skills block.
• The language is a genuine but secondary advantage. Its own small section near the bottom, after education.
• One language at a low level, unrelated role. A single line at the foot of the page, or leave it out. A2 in a language nobody asked about is not doing much work.
• Translation, interpreting, teaching or localisation roles. The languages are the qualification. They belong at the very top, with the direction of work stated — translating into your native language is a different service from translating out of it.

Being specific about what you can do

The strongest version of this section pairs a level with evidence, because the evidence is what a sceptical reader trusts. Evidence here does not mean a certificate; it means a context in which you used the language and something happened.

A qualification

DELE, DELF, Goethe-Zertifikat, JLPT, HSK, TOEFL or IELTS — name it with the level and the year, since some are time-limited.

Work you did in it

"Handled the Portuguese-speaking half of a 200-account support queue for three years" is worth more than any self-assessed label.

Where you learned it

Two years living in the country, a degree in the language, or a bilingual upbringing. This explains the level rather than merely asserting it.

The specific skill split

Reading and writing frequently outrun speaking, especially in languages learned academically. Saying so is honest and often exactly what a documentation-heavy role wants.

When the four skills differ

Reading, writing, speaking and listening genuinely diverge, and a single label hides that. Someone who reads technical German comfortably but hesitates on the phone is well described by "German — reading C1, spoken B1" and badly described by either "fluent" or "basic". Where the split is meaningful for the job, state it; where it is not, one overall level is fine.

Honesty, and what happens when you overstate

This is the section where exaggeration is caught fastest and costs most. An interviewer who speaks the language will switch into it, usually without announcing that they are about to, and there is no recovery from a "fluent" claim that collapses in the first exchange. It is not treated as an overstatement; it is treated as a statement about your reliability generally, and it contaminates everything else on the page.

The under-claiming case is also worth naming. Plenty of people write "conversational" about a language they can genuinely work in, usually because they compare themselves to native speakers rather than to the requirement. If you have held a real working conversation in the language under pressure and it went fine, say B2 and stop apologising for it.

Formatting and small details

1. Order by strength, native language first, then descending. If one language is the reason you are applying, lead with that one instead.
2. Use English names for the languages on an English-language resume — "Mandarin Chinese", not the endonym — unless the resume is being read in the other language.
3. Name the variety when it matters. Mandarin versus Cantonese, Brazilian versus European Portuguese, simplified versus traditional characters. In localisation and translation this is the whole point.
4. Keep it to one line per language. This section should be compact; if it is running to a paragraph, the detail belongs in the experience bullets instead.
5. Do not include programming languages here. They go in skills. A section mixing Python with Portuguese confuses both.

For a sense of how far up the page the section should sit for language-dependent work, compare a general commercial resume in the examples library with one for a social worker or a flight attendant, where a second language is frequently a stated requirement rather than a nice extra. You can move the block in a few seconds in the builder.