List languages when they are relevant to the role, the market, or the company's customers — one line, each language with an honest proficiency label: native, fluent, professional working proficiency, conversational, or basic. Skip the line entirely if you only speak the country's default language; stating English on a US resume in English proves itself.
Languages are a differentiator whenever the employer touches markets, customers, or teams that speak them. Customer-facing roles, multinational companies, government and NGO work, and any posting that names a language all make the line valuable — sometimes decisive, since bilingual requirements filter hard. In the Gulf, in Europe, and across global tech hubs, a languages line is standard resume furniture; recruiters expect to find it.
Where it adds nothing, cut it. A monolingual line restating the resume's own language is filler, and basic tourist proficiency in three languages reads as padding rather than capability. The test is whether a recruiter could act on the information: staff you differently, route you to different accounts, match you to a requirement.
The plain-English ladder works everywhere: native, fluent, professional working proficiency, conversational, basic. Professional working proficiency is the load-bearing label — it means you can do your job in the language: run meetings, write documents, handle customers. Conversational means social interaction but not work. Do not blur that boundary; it is the one interviewers probe.
Formal scales add precision where the audience knows them. European employers recognize CEFR levels — B2, C1, C2 — and government roles use the ILR scale. If you hold a real certificate, cite it with the level: Spanish, C1 (DELE). Skill bars and star ratings, as everywhere on a resume, are decoration a parser cannot read and an interviewer cannot calibrate.
A language claim is the single easiest resume line to verify: an interviewer who speaks it will switch mid-conversation, without warning, precisely because candidates inflate here. Fluent must survive five unprepared minutes on a work topic. If it would not, write conversational — the honest lower label plus a smooth interview beats the higher label plus a visible collapse.
Rustiness is real: if you were fluent a decade ago and have not used it since, professional proficiency, currently refreshing is truthful and defensible. And if a posting requires a language you genuinely cannot work in, the languages line is not the place to solve that — no phrasing survives the first phone screen conducted in it.
Only when it is not the default assumption: applying from or to non-English-speaking markets, or roles that explicitly require English. On a US or UK resume written in English, the line adds nothing — the document itself is the evidence.
You can perform your actual job in the language: run meetings, write clear documents, handle customers and colleagues without a translator. It sits between conversational, which covers social settings, and full fluency across any context.
Inside or directly under your skills section as a single labeled line. Give languages their own section only when they are central to the role — interpreter, localization, bilingual support — and then consider leading with them.
Check the rest of the page holds up too — the free scorer runs 60+ recruiter-grade checks on your resume in seconds.
