How to list languages on a resume (exact wording)

What's the exact format for listing languages on a resume?

Use one line per language in the form "Language — proficiency level": `English — Full professional proficiency`. That single pattern reads correctly in every market and survives every parser. Put it under a heading called simply Languages, give each language its own line, and write the level out in words instead of drawing it. If you hold a certificate, add it in brackets: `French — B2 (DELF, 2024)`. Then resist the urge to get clever. Flags, five-dot rating scales, progress bars and little donut charts all communicate less than a single word does, because software can't read them and a human has to guess whether three dots out of five means you can run a client call or order a coffee.

There's a second reason to spell it out. A recruiter working through a stack of applications spends seconds on your languages section, and ambiguity costs you the benefit of the doubt. "Spanish ●●●○○" invites the reader to assume the lower interpretation. "Spanish — Professional working proficiency" tells them exactly what they're getting and gives them language they can repeat to the hiring manager. Keep the entries in a sensible order too: strongest first, or the language the job asks for first. Nobody wants to read past three decorative icons to find out whether you actually speak the language the role is built around.

The strongest version of this section ties the level to real work. `Spanish — B2; weekly client calls and written reporting with the Madrid team` does something a bare label never can — it shows the language earning its place in a job rather than sitting in a drawer since university. One short clause is enough; don't let it swell into a paragraph. If you're rebuilding your CV from the ground up and want the structure handled for you, you can build a clean, ATS-friendly CV and keep the languages block in the plain single-column format parsers handle best, rather than retrofitting a template that fights you.

Which proficiency levels do recruiters actually trust?

Five labels do the heavy lifting in English-language hiring: native or bilingual, full professional proficiency, professional working proficiency, limited working proficiency, and elementary. They come from the US government's ILR scale and are the same wording used in professional profiles, which is exactly why recruiters read them without effort. In Europe, CEFR letters (A1 through C2) are understood on sight and often preferred. Numbered ILR ratings belong on applications for federal, defense and diplomatic roles, where a posting may literally ask for "3/3". Match the scale to the market you're applying into, and name the scale when it isn't obvious.

Be honest about which band you're in, because this is one of the few CV claims that gets tested live. Full professional proficiency means you can negotiate, present and write documents that need no editing. Professional working proficiency means you handle meetings and email competently with the odd gap. The jump between those two is where most people flatter themselves, and a twenty-minute screening call in that language exposes it immediately. If a posting makes the language a hard requirement and you're genuinely borderline, state the honest level and attach evidence — a test score or a certificate does more for you than an inflated adjective ever will.

Two technical rules save you from looking careless. First, don't mix scales on one CV: CEFR letters for one language and ILR numbers for another reads like you copied from two different sources. Second, don't invent conversions. The crosswalks below are approximate, and the frameworks organize skills differently, so report what your credential actually says — TOEFL, IELTS, DELF or DALF, DELE, Goethe-Zertifikat, JLPT, HSK — rather than converting it yourself. ILR does allow per-skill detail, which is useful when your reading outruns your speaking: `Mandarin — ILR speaking 2, reading 3` is precise, credible and quietly impressive.

Where should the languages section go on your CV?

By default, put languages near the bottom — after experience, education and skills, alongside certifications. Move it to the top, directly beneath your professional summary, the moment the job ad treats the language as a requirement rather than a nice-to-have. That's the whole rule. A trilingual customer success candidate applying to a role that says "fluent German required" should not make anyone scroll to page two to find the German. Placement is a signal in itself: what sits high on the page is what you're claiming as central to your candidacy, and recruiters read it that way whether or not you intended it.

Where the language is the job, go further and work it into the top third as prose. A summary that opens "Bilingual Spanish/English support lead, six years in SaaS" gets the point across before the section even arrives — then the Languages block confirms it with a proper level. The same applies to translation, localization, international sales and any role with a regional remit. One caution: don't park languages inside your personal-details block next to things that shouldn't be there at all. It's worth knowing which personal details to cut from a CV before you decide what sits at the top of the page.

Avoid three placements that quietly lose the information. Sidebars and two-column layouts, where the languages column gets interleaved with your job history during extraction. Headers and footers, which many parsers skip entirely. And graphics or text boxes, which may not be extracted as text at all. If you're squeezed for space on a one-page CV, a single comma-separated line works perfectly well: `Languages: Hebrew (native), English (full professional), Russian (conversational)`. That's compact, unambiguous and parses cleanly. What doesn't work is cutting the section when the role needs it, or keeping it when the role plainly doesn't.

How does an ATS read your language section?

Most applicant tracking systems don't understand your proficiency scale — they extract text and match it against the words in the job description. That's the practical reality behind every piece of ATS advice here. If the posting says "bilingual Spanish/English required" and your CV says "speaks Spanish," nothing connects the two. If it asks for "professional working proficiency in Mandarin" and you wrote "Chinese, advanced," you've described the same ability in vocabulary the system isn't looking for. Recruiters also filter and search by these phrases inside the system, so the wording matters long after the initial screen.

So mirror the posting's exact phrasing, then add your own precision beside it. If the ad says "fluent French," write `French — Fluent (C1, DALF)` rather than choosing between their word and yours. Use the language name the ad uses too: a system searching for "Mandarin" won't necessarily surface "Chinese," and one searching for "Castilian" won't surface "Spanish." None of this is keyword stuffing — it's one accurate line written in the employer's vocabulary. Repeating "bilingual" six times across your CV is the version that backfires, both with the filter and with the person reading afterward.

Formatting decides whether any of it gets read. Export a text-based PDF, not a scan or an image; keep the section in a single column; skip icons and flags. If you want to see what a parser pulls out of your file before you send it, a free CV check that rates ATS compatibility will show you the score and the layout analysis, and pasting in the job description surfaces the skills the ad asks for that your CV doesn't mention — language requirements included. Bear in mind that parsing accuracy is highest in English and drops with other scripts and regional conventions, which is precisely where bilingual applicants get burned.

What changes on a bilingual Hebrew/English CV, and when should you drop a language?

Keep two separate files — one Hebrew, one English — rather than one mixed document, and on the Hebrew CV put the languages section last, stating your Hebrew level and your English level explicitly. Israeli job ads routinely specify an English level, so "אנגלית – שליטה מלאה" or "רמה גבוהה" is doing real screening work, not decoration. Apply in the language of the ad: a Hebrew posting gets the Hebrew file, an English-language posting from a global company gets the English one. If a role demands native-level English, say so high up instead of burying it beneath military service and education.

Mixed-script files are where things break. A Hebrew CV with English job titles scattered through it can scramble during extraction, because right-to-left text and left-to-right fragments on the same line don't always come out in the order you see on screen. Keep technology names and company names in English where that's the norm, but don't build whole sections in two directions at once. If you're producing a Hebrew CV properly exported right to left, a Hebrew CV builder made for the Israeli market handles the direction and layout so your bilingual claim doesn't collapse in the file itself.

Here's the opinion that will save you more space than any formatting trick: drop every language you can't work in. Below roughly B1, or limited working proficiency, a listed language costs you credibility instead of adding to it — "Italian — basic" tells a recruiter you studied it for two years in school and have forgotten most of it. Three languages you genuinely use beat six with two real ones among them. The exceptions are narrow: the ad explicitly asks for exposure to that language, you're applying somewhere a partial level still matters operationally, or you're early in your career with thin experience and little else to show. Otherwise, cut it and reclaim the line.

Frequently asked questions