Should You Put Languages on Your Resume? The Honest Answer

Here is the short answer: yes, in most cases. But a languages line only helps when it is specific, honest, and matched to the job. A vague word like "fluent" with no scale, no proof, and no connection to the work reads as decoration. A precise line with a level, a certificate, or a work example reads as evidence. Recruiters treat those two very differently, and the data explains why.

What employers actually say about language skills

The strongest employer survey on this topic is still the one from the American Council on the Teaching of Foreign Languages (ACTFL). Its 2019 report, Making Languages Our Business, surveyed 1,200 U.S. employers through Ipsos Public Affairs. Nine out of ten said they rely on employees with language skills other than English. More than half, 56%, expected their demand for those skills to grow over the next five years. One in three language-dependent employers reported a language skills gap, and one in four employers said they had lost business because they lacked the right language skills.

That last number is the one to sit with. Languages are not a nice extra on these resumes. For a quarter of employers, missing language capacity cost them a deal. The most in-demand languages in that survey were Spanish (named by 85% of employers relying on language skills), Chinese (34%), French (22%), Japanese (17%), and German (17%). And 47% of employers said they needed language skills exclusively for the domestic market, not for overseas work. A bilingual customer service rep in Texas or a nurse in California is not an international hire. They are a domestic one.

The pay data points the same way. Preply's 2025 analysis of more than 13 million job listings across 18 countries, sourced from Adzuna, found bilingual workers in the USA earning an average of $14,050 more per year than monolingual peers, an 18.8% premium. In the UK the premium was $6,395 a year, or 11.5%. Across all countries studied, the average was $9,353, or 14.3%. Treat those as averages across very different jobs, not a promise for any single role. But the direction is consistent: employers pay for a skill they struggle to hire.

One caution before you get excited. The Bureau of Labor Statistics counts only 73,900 interpreter and translator jobs in the USA in 2025, with a median wage of $60,170 in May 2025 and about 6,000 openings a year projected through 2035. That narrow occupation is small and slow-growing. The real opportunity is much bigger, because it lives inside other jobs: sales, healthcare, customer service, logistics, teaching. Your language skill usually earns its place as a multiplier on a job you already want, not as a job title on its own.

When languages belong on your resume

Include them when any of these five cases is true:

1. The posting asks for them. This is the easiest call. If the job lists "Spanish required" or "German a plus," your languages section moves near the top of the resume, right under your summary or skills section, and the language name should match the posting word for word. Recruiters filter by keywords, and a Jobscan survey of 384 recruiters found 99.7% use keyword filters. "Español" will not match a filter looking for "Spanish."

2. You have used the language at work. A support agent who handled a Portuguese queue, a nurse who took patient histories in Mandarin, a sales rep who closed deals in French: these are not language claims, they are work history. Put the language inside the bullet itself ("Resolved billing cases for the Spanish-speaking customer base, 40% of ticket volume") and also in the languages section. The bullet is the proof; the section is the summary.

3. The role serves customers, patients, or clients who speak it. Healthcare, retail, hospitality, social work, education, and public-facing government roles all count. ACTFL found customer service, sales, marketing, management, and IT were the departments with the greatest language need. If your customers speak it, say so.

4. You hold a certificate or test score. A DELE B2, a JLPT N2, a DALF C1, an IELTS band, or a Seal of Biliteracy turns a self-assessment into something checkable. Certificates belong next to the language, not buried in a separate section the recruiter never reaches.

5. You are early in your career and need proof you can learn. For a new graduate with a thin work history, a real second language signals discipline and trainability in a way a coursework list never will. It is one of the few sections where a junior candidate can outshine a senior one.

When to leave languages off

There are four honest reasons to cut the section:

You only know a few phrases. Holiday Spanish, a semester of high-school French ten years ago, or a language you can read but not speak does not belong on a resume unless the job specifically needs that narrow ability (reading technical documents, say) and you label it exactly that way. Listing a language you cannot actually use is the fastest way to fail an interview, because this is one of the few resume claims a hiring manager can test on the spot by simply switching languages mid-conversation.

The language has nothing to do with the job and the resume is already full. A one-page resume is a trade. If you are applying for a backend engineering role in Ohio and your second language is conversational Italian with no connection to the work, that line costs space a stronger bullet could use. Keep it for LinkedIn, where space is free.

You would be embarrassed if tested. This is the only test that matters. If a native speaker sat across from you tomorrow and ran the interview in that language, would you hold up? If the answer is no, the level you wrote is too high. Downgrade it or drop it.

You are padding. A languages section with four languages at "basic" level reads worse than one language at a professional level. Recruiters read padding as insecurity. One strong line beats four weak ones.

The proficiency problem: "fluent" means nothing on its own

Ask ten people what "fluent" means and you will get ten answers. One person's fluent is another person's "can order lunch." That is why you need a scale, and which scale you pick depends on where you are applying.

CEFR (A1 to C2): The Common European Framework, built by the Council of Europe, is the standard in Europe and increasingly understood worldwide. A1 is beginner, B1 handles everyday situations independently, B2 works professionally in the language, C1 is advanced and flexible, C2 is near-native mastery. If you are applying in the UK or EU, use CEFR. Recruiters there read it instantly.

ILR (0 to 5): The Interagency Language Roundtable scale is used by U.S. federal agencies. Level 1 handles basic survival needs, level 2 handles routine social and work topics, level 3 is the professional threshold where you can discuss complex topics and read demanding texts. Use it for U.S. government or defense-adjacent roles.

ACTFL (Novice to Distinguished): The American Council's scale, common in U.S. education, runs Novice, Intermediate, Advanced, Superior, and Distinguished, each with Low, Mid, and High sublevels. Use it if your certificate already reports it.

Plain words (LinkedIn style): Native or bilingual, full professional proficiency, professional working proficiency, limited working proficiency, elementary proficiency. This is the safest choice for a general U.S. corporate resume, because no recruiter needs a conversion chart to understand it.

Pick one scale and use it for every language on the page. Mixing scales ("Spanish: C1, French: conversational, German: fluent") forces the recruiter to do translation work, and most will not bother. If you have a certificate, report the scale that certificate uses. If you do not, plain words are the most honest option, because they describe what you can do rather than implying a test you never took.

Here is a rough crosswalk so you can place yourself honestly. B2 on CEFR is roughly professional working proficiency: you can work in the language, but you will still reach for a dictionary on technical documents. C1 is roughly full professional proficiency: you can run meetings and write reports. Anything below B1 is not a professional claim at all. If your level is A2, you are describing a personal skill, not a workplace one, and it only belongs on the resume if the job asks for exactly that.

How to write the section: three formats that work

Format 1: The dedicated section. Best when languages matter to the role. Keep it to one or two lines:

Languages: English (Native), Spanish (Full professional proficiency, DELE C1), Portuguese (Professional working proficiency)

Order by relevance to the job first, not by fluency. If the role is for the Brazilian market, Portuguese goes first even if your Spanish is stronger.

Format 2: Woven into experience bullets. Best when the language is part of work you already describe:

• Managed onboarding for Spanish-speaking clients, cutting setup time from five days to two
• Translated product documentation from English to German for the EU launch

This format is the most believable, because the language claim arrives with a result attached.

Format 3: The skills-section line. Best when space is tight and languages are a bonus rather than a requirement:

Skills: Python, SQL, Tableau | Languages: English (Native), French (B2)

Never use flag icons, star ratings, or progress bars for languages. A row of filled dots looks clever and parses terribly: applicant tracking systems cannot read a graphic, and a human reader cannot tell whether four dots out of five means B2 or wishful thinking. Text only, every time.

The honesty test: employers can and do check

Language skills are, as Language Testing International has put it, easy to lie about on paper, which is exactly why employers verify them. Expect one of three checks if the language matters to the role: a portion of the interview conducted in that language, a written task such as translating a document or drafting an email, or a formal proficiency test before an offer. A Babbel survey from 2022 found that 1 in 8 Americans admitted lying about language fluency on a resume or application. That is the pool your honest line is competing with, and it is why a certificate or a work example matters so much: it separates you from the people who padded.

Two rules keep you safe. First, never claim a level you cannot demonstrate in a live conversation at that level. Written fluency without spoken fluency is a real profile, but label it ("Spanish: reading and writing, professional level; speaking, conversational") rather than calling the whole package fluent. Second, never list a language you are "currently learning" at a working level. If you are learning it and the job wants it, write "Spanish (Elementary, currently studying)" and only if the posting treats it as a nice-to-have. Learning is admirable. Pretending you have arrived is not.

The ATS angle

Languages are one of the easiest sections to get right for hiring software and one of the easiest to break. Three rules cover it. First, spell the language in full and in English ("Spanish," not "Español") unless the posting itself uses another form. Second, use standard section headings like "Languages" so the parser files the section correctly. Third, repeat the language name where it is true: once in the languages section and once inside a relevant work bullet. Repetition in an ATS context is not stuffing when each mention is attached to real work. What breaks parsing is the decorative stuff: flags, icons, tables, and text boxes. Keep the section as plain text lines, the same way you would write the rest of the resume. If you want to check how your resume parses before you send it, run it through a free ATS resume checker and look at what the parser actually extracts from your languages section. If it comes back garbled, the section needs simplifying, not decorating.

The US vs UK difference

In the US, plain-word levels are the norm and most resumes list languages only when they are job-relevant. In the UK, where the document is a CV rather than a resume, CEFR levels are expected and language sections are more common, partly because European employers are used to reading them and partly because UK graduate schemes and public-sector roles often ask for them explicitly. If you are applying across both markets, keep two versions: a US version with plain words and a UK version with CEFR levels. The content is the same. The vocabulary changes, and that small change signals that you understand the market you are applying to. The same logic applies to the document itself: a US resume, a UK CV, and an academic CV are three different documents, and sending the wrong one is a quiet way to look out of touch.

The 30-second decision test

Run through these five questions before you publish:

1. Is this language relevant to this job, this employer, or this customer base?
2. Can I state my level on a recognized scale or in plain words a stranger would understand?
3. Could I pass a 10-minute conversation or a short written task in it tomorrow?
4. Do I have proof: a certificate, a test score, or a work example?
5. If I delete this section, does the resume get weaker or just shorter?

If you answered yes to the first three, include it. If you also have proof, put the proof on the line. If you answered no to the first three, leave it off this application and keep it for the one where it fits. Languages are not a personality section. They are a capability claim, and capability claims earn their space or they do not.

Frequently asked questions

Should I list my native language? Yes, when you list other languages too, because it anchors the scale. "English (Native), Spanish (Professional working proficiency)" tells the recruiter exactly where you stand. On its own, listing only your native language adds nothing unless the posting asks for native-level ability.

Should I include a language I am still learning? Only if it is at least at a usable level and the job treats it as a plus rather than a requirement. Label it honestly as elementary or in progress. Never list a language you started last month as a skill.

Is it better to say "bilingual" or to name a level? Name the level. "Bilingual" is a claim about identity as much as ability, and recruiters cannot tell from it whether you can run a client meeting or just chat with family. A level plus a certificate settles the question before it is asked.

Where should the languages section go? Near the top if the posting requires the language, near the bottom with skills and certifications if it is a bonus. Placement is a signal: top placement says "this is why you should hire me," bottom placement says "this is extra."

Do I need a certificate to list a language? No, but a certificate removes doubt. Heritage speakers and people who learned a language at home often have no certificate and full professional ability. In that case, a work example in a bullet does the same job as a certificate.

Can a language section hurt my application? Yes, in two ways: an inflated level that collapses in the interview, and a padded list of beginner languages that makes the whole resume look less credible. Both are avoidable. Be specific, be honest, and cut anything you cannot defend.

The bottom line

Languages belong on your resume when they are real, relevant, and stated precisely. Nine out of ten US employers rely on them, a quarter have lost business without them, and bilingual workers earn a measurable premium. But none of that helps a line that says "fluent" and means "I took it in school." Write the level, name the proof, and put the language where the job can see it. Then let the rest of the resume do its work.

Before you send your next application, run your resume through ZenWrit's free ATS resume checker and check that your languages section parses cleanly alongside your skills and experience. A section the software cannot read is a section that never existed.

Related reading: How to List Certifications on Your Resume (certificates make language claims checkable), What "ATS-Friendly" Really Means (how parsers read your sections), Skills-Based Hiring Is Here (where the languages section fits), Should You Put Hobbies on Your Resume? (the same include-or-cut logic), Resume Summary vs. Objective (where to signal languages up top).