How to list languages on a resume (without overstating your level)

Languages belong on a resume when they are relevant to the work, or when they say something real about what you can do for this employer. A language you studied for two years at school and have not used since does not meet that test, however much you liked the classes. A language you used with customers, colleagues, or clients does, even if your level is only intermediate.

The other reason to get this section right is that it is checkable. If you write "fluent in French", a French-speaking interviewer may simply switch to French. That is not a trap; it is the normal way a claimed skill gets verified. Write the level you could actually work at tomorrow, not the level you hope to reach by the time the job starts.

When to include a languages section, and when to leave it off

Include it when one of these is true:

• The posting asks for it. If the posting names a language, and you speak it at a usable level, say so plainly. This is the first place a reader looks for it.
• The work itself is multilingual. Support, sales, translation, teaching, and roles serving a particular community all count, even when the posting does not list a language as a formal requirement.
• You used the language on the job. A language tied to real work, such as handling supplier emails in German or onboarding customers in Spanish, is evidence, not decoration.

Leave it off when none of those apply, or when the only honest level is beginner. A beginner level tells the reader you cannot yet do useful work in that language, and it takes up space that could carry a skill you can actually use. The same rule applies to the rest of the resume: how to list skills on a resume covers the same honesty test for skills in general. If you are learning a language and want the employer to know, a single line in a cover letter ("currently studying Portuguese, aiming for B1") is a better home for it than a resume section that implies working ability.

Pick one scale, and use it for every language

The most common mistake in this section is mixing scales: "Spanish: fluent, French: B2, German: intermediate". A reader cannot compare those three claims, because each one comes from a different system. Pick one scale and apply it to every language you list.

For most applicants outside the United States, the clearest choice is the Common European Framework of Reference, or CEFR, which runs from A1 to C2:

• A1-A2 (Basic): you can handle simple, familiar exchanges and everyday topics, with help and patience from the other person.
• B1 (Intermediate): you can deal with most situations on familiar ground, describe experiences, and explain a simple opinion.
• B2 (Upper-intermediate): you can work in the language on professional topics, take part in meetings, and read and write work documents with occasional gaps.
• C1 (Advanced): you can use the language flexibly and effectively for professional purposes, including nuanced discussion and long reports.
• C2 (Proficient): you can understand almost everything you hear or read, and express yourself precisely, including in demanding situations.

Native or bilingual is separate from the scale: it means you grew up speaking the language, or speak it at the level of someone who did. Do not use it for a language you learned at school, however good your exam results were.

In the United States, you will also see the ILR scale, which LinkedIn mirrors with labels such as limited working proficiency, professional working proficiency, and full professional proficiency. Those labels are roughly comparable to the CEFR levels above, but they are not exact conversions, so do not translate one into the other and present the result as a measured score. Whichever system you choose, pair it with a plain word as well, so a reader who does not know the scale still understands: "Spanish: Advanced (C1)" reads clearly to both audiences.

Calibrate the level by what you can actually do

Scales are only useful if the level behind them is honest. Before you write a level down, test it against the work, not against your coursework:

• Could you take a meeting in it? If you could follow the discussion and contribute, even slowly, that is working ability. If you would need the meeting in your first language, it is not.
• Could you write a work email in it? A short, correct email to a colleague is a fair test for B1 and above. A message full of errors you would not spot is not.
• Could you read a document in it? Reading a news article is easier than reading a contract or a technical specification. Match the test to the job: a support role needs conversation, a research role needs reading.
• When did you last use it? A language unused for five years is rarely at the level it once was. If you would need a week of practice before using it at work, say so by dropping a level, not by hoping no one checks.

One more calibration rule: split the skills when they genuinely differ. "Spanish: B2 speaking, B1 writing" is more useful, and more believable, than a single claim that hides a weak side. Only do this when the difference matters for the role; for most resumes, one honest level per language is enough.

Formats that work, with examples

Keep the section short. Three to five lines is plenty, and one line is fine when only one language matters for the role.

Notice what each line does. The language name is the standard English name, which is also what applicant tracking systems are most likely to recognise: write "Spanish", not only "Espanol", and "Mandarin" rather than a regional label a parser may not match. The level is a plain word plus a scale code. The strongest line adds one short proof point, the work where the language was used, which is what turns a claim into evidence.

Where the section sits depends on how important languages are for the role. If the posting asks for a language, put the section near the top, just after the summary or skills, so the reader finds it without hunting. If languages are a supporting strength, put it after experience, with the rest of the supporting sections. And when a language was central to one particular job, mention it in that job's bullets too, as part of the skills evidence, not only in the standalone section: "Handled onboarding calls in Spanish for new customers in Spain and Mexico" tells a reader more than a level label on its own.

Certificates and proof, used sparingly

A certificate helps when it matches the level you claim. If you hold a DELE, DELF, Goethe, IELTS, or similar qualification, add it in the same line: "Spanish: Advanced (C1), DELE C1". That gives the reader something verifiable, and it explains why you chose that level. The fuller guidance on listing qualifications is in how to list certifications on a resume.

Do not add a certificate that contradicts your level, and do not list a certificate for a language you no longer speak at that level. An old B2 certificate next to a current claim of C1 raises the question the certificate was supposed to answer. When the certificate is old, either drop the level to match what you can do now, or leave the certificate out and let the level stand on its own.

Tailor the section to each posting

Tailoring a languages section is mostly a matter of ordering and emphasis, not rewriting. Put the language the posting asks for first, even if it is not your strongest language overall. If the posting asks for "fluent French", and your honest level is B2, do not upgrade yourself to fluent to match the wording: mirror the posting's language only where it is honestly true of you, and let the rest of the resume show what you can do. The same discipline applies across the whole document, covered in how to tailor your resume to a job description.

For roles where no language is requested, keep the section but keep it brief: two lines are enough to show a genuine strength without suggesting that languages are the main thing you offer. And if you speak several languages, list only the ones at a usable level. A long list of beginner languages reads as padding, and padding in one section makes the reader doubt the sections around it.

Five mistakes that weaken a languages section

• Writing "fluent" for everything. Fluent is the most overclaimed word on resumes. If every language is fluent, none of them is believable. Use the scale, and reserve the top levels for languages you could work in tomorrow.
• Mixing scales in one section. One system, applied consistently, is the whole point of a scale. Mixed labels force the reader to guess, and guessing is not how shortlists are made.
• Listing languages you cannot use at work. School-level languages, holiday phrases, and languages you once studied belong nowhere on a resume. They add length without adding evidence.
• Using vague words alone. "Good French", "basic Spanish", and "some German" mean different things to different readers. A plain word plus a scale code removes the guesswork.
• Hiding the language in a wall of skills. A language buried in a comma-separated skills list is easy to miss, and hard for a parser to read as a language. Give languages their own short section, with one language per line.

The 60-second languages audit

Before you send any application, run this check:

1. Is every language at a usable level? Drop anything below the level where you could do real work in it.
2. Is there one scale, used consistently? One system for every language, with a plain word next to each code.
3. Could you defend each level in an interview? If the interviewer switched to that language, would you keep up? If not, lower the level.
4. Is the posting's language first? Order by relevance to this role, not by how proud you are of each language.
5. Is there proof where it matters? One short note about where you used the language, or one certificate, for the language the role actually needs.

A languages section should be the easiest section on the resume to trust: short, specific, and backed by real use. Write it that way, and it does quiet work for the rest of the application. One practical check before you send: run the draft through Tailr's ATS checker and see whether the languages the posting asks for are the ones your resume actually shows, in words a parser can read.