Languages on a resume are listed with a stated proficiency level, using a recognised scale rather than vague descriptors. Only languages at working proficiency or above belong on the document, since anything below that is not usable in a professional context.

The section is short — usually two to five lines — and its placement depends on whether the language is a job requirement or supplementary. Where a posting names a language, it belongs near the top; otherwise it sits with skills or near the bottom.

Languages are one of the few resume items where the claim gets tested directly and immediately — sometimes in the first phone call, in that language, with no warning. That makes accurate self-description more important here than almost anywhere else on the page.

The common failure is listing school-level study as a professional capability. "Basic French" from a decade ago is not a skill; it is a memory.

How to Describe Your Level

Vague labels invite misinterpretation in both directions. Use a scale, and use it consistently.

Level What it means CEFR
Native First language, or fully equivalent —
Bilingual Two languages at native or near-native level C2
Fluent Can work entirely in the language, including nuance and pressure C1–C2
Professional working Can hold meetings, write documents, and handle routine business B2
Conversational Comfortable in everyday exchange; limited in technical or formal settings B1
Basic Simple phrases only — generally not worth listing A1–A2

Two formatting conventions, either acceptable: plain descriptors — "Spanish — professional working proficiency" — or the CEFR reference where the employer is European or the posting uses it, since it is precise and widely recognised there.

Where you hold a formal certification — DELE, DELF, JLPT, HSK, IELTS, TOEFL, Goethe-Zertifikat — include it with the level and year. It converts a self-assessment into a verified one and belongs with your other credentials, following the format in listing certifications.

Whatever you claim, assume the interview will start in that language without notice. Describe yourself at the level you could sustain on a bad day, not your best one.

Where the Section Belongs

  • Named in the posting as a requirement — put it in the professional summary and give it its own line near the top. It is a screening criterion, not background.
  • Relevant to the market or client base — a short Languages section directly under skills.
  • Genuinely supplementary — two lines near the bottom, or folded into the skills section as one grouped entry.
  • Applying internationally — near the top, since language capability often determines eligibility rather than merely helping.

Keep the heading conventional — "Languages" — for the same parsing reasons that apply to every section, covered in making a resume machine-readable. And avoid flag icons and graphic proficiency bars: they carry no extractable text and the scale they imply is undefined, the same problem discussed in choosing which skills earn their place.

When Languages Actually Help

They carry real weight in specific contexts and almost none elsewhere, which is worth knowing before deciding how much space to give them.

  1. Customer-facing roles in multilingual markets. Support, sales, healthcare, hospitality, and public services in regions with significant language communities.
  2. International or multi-region teams. Where colleagues, suppliers, or clients operate in another language day to day.
  3. Roles with explicit language requirements. Translation, localisation, diplomatic and consular work, international development, some legal and compliance functions.
  4. Companies with operations where you speak the language. Even where the posting does not mention it, a match with a company's actual footprint is a genuine differentiator.
  5. Anything involving relocation. Local language capability materially changes how an application is read.

Outside these, a language is a small positive that costs two lines. It does not need a dedicated section, and it does not belong in your summary. Where it does matter, mirroring the posting's own phrasing helps for the reasons set out in resume keywords.

Not Overstating It

Language claims are unusually easy to verify and unusually embarrassing to fail. A few practical rules:

  • Do not list a language you have not used in years without noting that it is rusty, or leave it off entirely. Capability degrades and the interview will find the current level, not the historical one.
  • Distinguish reading from speaking where they differ significantly. "German — fluent reading, conversational spoken" is honest and still useful; many technical roles need the first far more than the second.
  • Do not call yourself fluent because you spent a summer somewhere. Fluent means working entirely in the language including under pressure, which is a high bar.
  • Do not list programming languages here. They belong in the skills section; mixing them looks careless.
  • Do not list your resume's own language as a separate entry unless the role requires certified proficiency, in which case give the certification.

One genuinely useful addition where you have it: a line showing the language in professional use. "Ran weekly client calls in Spanish for a Madrid-based account" is evidence rather than a claim, and evidence is what the rest of the resume should be doing too — the principle is in making a resume memorable.

If you want to check whether a language requirement in a posting is being picked up by your current document, the first comparison is free, and credit options are on the pricing page. Building the document from scratch, the free resume builder at FixResume includes a languages section you can position where it fits.

Common Questions About Languages on a Resume

What proficiency levels should I use?

Use a recognised scale rather than vague words: native, bilingual, fluent, professional working, or conversational. The CEFR levels from A1 to C2 are precise and widely understood, particularly by European employers. Whichever you choose, apply it consistently across every language you list.

Should I list a language I studied at school?

Only if you can still hold a conversation in it, in which case describe it as conversational rather than fluent. School-level study from years ago is not a professional capability, and listing it invites a question you cannot answer. Leaving it off costs you nothing.

Where should the languages section go?

Near the top, and in the summary, when the posting names a language as a requirement, since it functions as a screening criterion. Otherwise a short section under skills or near the bottom is sufficient. For international applications it belongs high on the page because it often determines eligibility.

Should I include a language certification?

Yes, with the level and year, where you hold one such as DELE, DELF, JLPT, HSK, or Goethe-Zertifikat. A certification converts a self-assessment into a verified claim, which matters given how easily language ability is tested. Note that some certifications are considered to expire after a few years.

Can I use flag icons or proficiency bars?

No. Graphics carry no extractable text, so an automated system reads them as nothing at all, and the scale a bar implies is undefined anyway. Flags also conflate languages with countries, which is inaccurate for widely spoken languages. Plain text with a named level works better.

Is it worth listing a language the job does not require?

It is worth two lines if you are at professional working level or above, particularly where the company has operations in that language even if the posting is silent about it. It does not warrant a prominent section or a mention in your summary unless the role genuinely calls for it.