# Language skills on a resume: levels, scales, what a matcher reads

> Ten versions of a Languages line run through HiredFolio's keyword matcher, the ETS TOEIC cut scores, CEFR and ILR descriptors quoted from the source, and where the line goes on the page.

Canonical: https://hiredfolio.com/blog/resume-language-skills

Published 2026-11-09 · 10 min

Keywords: language skills resume, how to list language skills on a resume, language proficiency levels resume, resume language levels, fluent vs proficient resume

"Fluent" is the most common word on a Languages line and the least informative one. No scale defines it, recruiters discount it, and the first phone screen in that language settles the question anyway. The line also has a second reader now: the keyword matcher inside whatever tool the company, or you, use to compare the resume with the posting. That reader does not know what a flag emoji means.

So this article does three things. It shows what a keyword matcher actually gets out of ten versions of the same Languages line, so you know which words carry. It gives you the scales and the TOEIC cut scores from the organisations that publish them, so the level you write can be checked. And it settles the small questions: bars or words, where the section goes, whether a beginner level belongs on the page at all.

## Ten versions of one Languages line, through a keyword matcher

HiredFolio's ATS check scores the keyword part of a resume with one function, `computeKeywordMatch`. It takes a list of terms and the text of a resume and reports which terms it finds. We gave it six terms a Customer Success posting could reasonably carry ("fluent English", "English", "French", "C1", "professional working proficiency", "Spanish") and ten versions of a Languages section for the same candidate: French native, English C1, Spanish B1. The script and its full output are in the pull request that published this article, so anyone can rerun it.

| Languages line as written on the resume                                                                                   | Terms found, of 6 |
| ------------------------------------------------------------------------------------------------------------------------- | ----------------- |
| English: fluent · Spanish: conversational                                                                                 | 2                 |
| English (C1) · Spanish (B1)                                                                                               | 3                 |
| Fluent English (C1, TOEIC 945, 2025) · Spanish: intermediate (B1)                                                         | 4                 |
| French: native · English: full professional proficiency (C1, TOEIC 945, 2025) · Spanish: limited working proficiency (B1) | 4                 |
| French: native · Fluent English (C1, TOEIC 945, 2025) · Spanish: professional working proficiency (B1)                    | 6                 |
| Bilingual English/French · Spanish: basic                                                                                 | 3                 |
| EN: C1 · FR: native · ES: B1                                                                                              | 1                 |
| English ●●●●○ · French ●●●●● · Spanish ●●○○○                                                                              | 3                 |
| 🇬🇧 C1 · 🇫🇷 native · 🇪🇸 B1                                                                                                 | 1                 |
| Anglais : courant · Espagnol : notions (a French line, on the English posting)                                            | 2                 |

The absolute numbers depend on the six terms we picked. The order does not, and it says five things.

Flags and ISO codes erase the language. "🇬🇧 C1" and "EN: C1" each matched one term, the letter. The matcher never saw a language name, because there was none in the text.

A slash can glue two languages into one word. On our first run, "Bilingual English/French" matched only "Spanish": the matcher kept "English/French" as a single token, the way it keeps "CI/CD" whole, so neither name was found. Since 5 October 2026 it splits a slash-joined pair it does not know as one term, and the line finds English and French. Another program may still read one word. Write "English and French", or one language per line.

Bars carry nothing. "English ●●●●○" got the three names and no level. A program cannot read dots, and a recruiter cannot check them.

The posting's phrase matches as a phrase. "fluent English" counted only when the two words sat next to each other in that order. "English: fluent" did not match it. The line that scored six of six repeated the posting's exact phrases and added the letter and the dated score beside them.

A line in the wrong language keeps the names and loses the rest. "Anglais : courant" on the English posting still matched "English" and "Spanish", because the matcher's lexicon aliases anglais to English and espagnol to Spanish; "courant" matched nothing, because the posting said "fluent". Write the language in the posting's language.

One limit to be clear about. The matcher does not pull a level out of a posting on its own. HiredFolio's [free keyword extractor](/tools/job-description-keyword-extractor), run on the same posting, returned "English", "French" and "Spanish" as hard skills and no level at all: its lexicon knows language names, not adjectives. The level words are for the human reader. The language name, written in full and in the posting's language, is for the program.

## Write the level in three parts

The posting's own phrase, then a scale, then a dated proof. Each part serves a different reader, and none of them is long.

<div class="blog-beforeafter">
  <p class="blog-beforeafter-kicker">Example <span>one Languages line rewritten</span></p>
  <div class="blog-beforeafter-grid">
    <div class="blog-beforeafter-cell blog-beforeafter-before">
      <p class="blog-beforeafter-tag">Nothing to check</p>
      <p class="blog-beforeafter-text">Languages: English (fluent), Spanish, some German</p>
    </div>
    <div class="blog-beforeafter-cell blog-beforeafter-after">
      <p class="blog-beforeafter-tag">Phrase, scale, proof</p>
      <p class="blog-beforeafter-text">
        English: fluent, full professional proficiency (C1, TOEIC 945, 2025). Spanish: limited working
        proficiency (B1). German: A2.
      </p>
    </div>
  </div>
</div>

The phrase is whatever the posting says. If it asks for "fluent English", the word "fluent" goes on the line, beside the letter that makes it checkable. If it asks for "professional working proficiency", that phrase goes on the line. Pick one scale for the whole resume. A resume that gives one language in CEFR letters and the next in ILR words reads as if the candidate looked each up separately, which is usually the case.

The proof is a test with its score and its year. A score without a year is a claim; a score with a year is a fact a recruiter can age.

## The scales, from the organisations that publish them

Most guides list the scales. Few quote the descriptors, and the descriptors are what let you place yourself honestly.

### CEFR: six letters, five skills

The Common European Framework of Reference runs from A1 to C2 and is the scale European recruiters read first. The [Europass self-assessment grid](https://europass.europa.eu/en/common-european-framework-reference-language-skills) rates five skills separately, and its spoken-interaction descriptors are the ones that matter for a job:

- B1: "I can deal with most situations likely to arise whilst travelling in an area where the language is spoken."
- B2: "I can interact with a degree of fluency and spontaneity that makes regular interaction with native speakers quite possible."
- C1: "I can express myself fluently and spontaneously without much obvious searching for expressions."

Read the three and place yourself on the one you could demonstrate on a call tomorrow. Your speaking and your writing can sit two letters apart; write the lower one, or both if the job uses both.

### ILR: the scale behind "working proficiency"

The Interagency Language Roundtable scale is the US government's, from 0 to 5, and the "working proficiency" phrases on job boards descend from it. From the [ILR speaking descriptions](https://www.govtilr.org/Skills/ILRscale2.htm):

- Speaking 2, Limited Working Proficiency: "Able to satisfy routine social demands and limited work requirements."
- Speaking 3, General Professional Proficiency: "Able to speak the language with sufficient structural accuracy and vocabulary to participate effectively in most formal and informal conversations in practical, social and professional topics."
- Speaking 5 is "Functionally Native Proficiency".

Use the phrase if the posting uses it. Add the ILR number only if you were rated, which in practice means a federal job. ACTFL is the third scale guides name; it lives in US education, so quote an ACTFL rating only if you hold one.

### "Fluent", "conversational", "bilingual"

No scale defines any of them, which is why they need a letter beside them. If you have to translate: the Europass B1 descriptor, most situations that arise while travelling, is what people mean by conversational. The B2 descriptor, regular interaction with native speakers, is what most postings mean by fluent. "Bilingual" claims two native languages. Write it only if you grew up with both; a recruiter who speaks the language will find out in the first minute, and the rest of the resume goes down with it.

## What a TOEIC score proves, by ETS's own table

The score to CEFR mapping gets passed around as hearsay. The source is one page: ETS Global's [mapping table for the TOEIC Listening and Reading test](https://www.eu.ets.org/content/dam/ets-org/eu/pdfs/toeic/mapping-cefr-toeic-listening-reading-test.pdf) (2025 edition). Total minimum scores:

| CEFR level | Total minimum score | Listening | Reading |
| ---------- | ------------------- | --------- | ------- |
| C1         | 945                 | 490       | 455     |
| B2         | 785                 | 400       | 385     |
| B1         | 550                 | 275       | 275     |
| A2         | 225                 | 110       | 115     |
| A1         | 120                 | 60        | 60      |

Three things the table says that the hearsay drops. There is no C2 row: a 990 is still a C1 claim, and writing "C2 (TOEIC 990)" is a mistake a certified reader spots. ETS writes that it "does not recommend to use the minimum cut scores strictly" and "encourages score users to consider CEFR levels separately for Listening and Reading", so a 785 made of 450 listening and 335 reading is a B2 listener and a B1 reader. And for A1 to B1, ETS "advises to take the TOEIC Bridge tests", which is a polite way of saying a 400 does not belong on a resume.

Date the score. ETS Global's [score page](https://www.etsglobal.org/fr/en/content/understanding-toeic-tests-scores) says it "will re-issue and confirm score results for 2 years after the test was taken". A 2021 score can still go on the line, as "TOEIC 945 (2021)", but the recruiter will read the year, so you should too.

For IELTS, TOEFL, Cambridge, DELF or HSK, the same rule: the test name, the score or grade, the year. The scale conversions belong to the test publishers; quote theirs, not a blog's.

## Bars, dots, flags and years: what each format loses

<div class="blog-dodont">
  <p class="blog-takeaway-head">Formats for the level <span>what survives a program and a reader</span></p>
  <div class="blog-dodont-grid">
    <div class="blog-dodont-col blog-dodont-dont">
      <p class="blog-dodont-tag">Lost in matching</p>
      <p class="blog-dodont-item">🇬🇧 🇪🇸 flags in place of names</p>
      <p class="blog-dodont-item">EN / ES / DE codes</p>
      <p class="blog-dodont-item">●●●●○ or "80%"</p>
      <p class="blog-dodont-item">"English/French", where a program keeps the slash</p>
      <p class="blog-dodont-item">"5 years of Spanish"</p>
    </div>
    <div class="blog-dodont-col blog-dodont-do">
      <p class="blog-dodont-tag">Read by both</p>
      <p class="blog-dodont-item">The language name in full, in the resume's language</p>
      <p class="blog-dodont-item">English, Spanish, German</p>
      <p class="blog-dodont-item">C1 (TOEIC 945, 2025)</p>
      <p class="blog-dodont-item">"English and French", or one per line</p>
      <p class="blog-dodont-item">"Spanish: B1, daily phone support for Madrid accounts"</p>
    </div>
  </div>
  <p class="blog-dodont-foot">
    A level survives only as text: a word a program can match and a letter a person can check.
  </p>
</div>

Years of study describe the past. "Five years of Spanish" can mean a B2 or an A2, depending on whether any of the five were recent, so say what you can do now, and where you last did it. Parentheses are fine: "English (C1)" matched both the name and the letter in our run. Graphics are a resume-template habit, and the template makers sell them because they fill space. A row of dots fills the same space as a dated score and says nothing.

## Where the languages go, and which to leave out

Three cases cover almost every resume.

The posting does not ask, and you have one or two languages: one line inside Skills, "Spanish (B1)", and move on.

The posting asks: give languages their own section, right after the summary or above Skills, and put the required language in the summary line too ("Customer success manager, C1 English, five years in SaaS support"). The summary is read first, and the matcher reads it the same as everything else.

The job is the language, as it is for interpreters, bilingual support and in-country sales: the level goes in the summary and the proof goes in the experience bullets, as work done in that language, not as a label. "Ran weekly QBRs with four German accounts, in German" tells the reader more than any letter.

Leave A1 off unless the posting names that language; ETS's own advice for A1 to B1 English is a different test, and a recruiter reads a beginner level as filler. Your native language goes on the line when it is not the resume's language or when you apply abroad. Applying to a US company in English with "English: native" on the page tells them nothing; applying to Berlin with it does. If the move is to France, the conventions change again, down to the word "courant": the [French CV format guide](/blog/french-cv-format) covers that line.

## Check the line against the posting

The matcher run above is the point of this whole article: the words on the Languages line either match the posting or they do not, and you can know which before sending. Paste the posting and the resume into the [free ATS check](/ats-checker): it lists the terms it read in the posting and which of them the resume carries, language names included, and it works in French as well as English. If a required language comes back missing, the cause is almost always one of the four above: a flag, a code, a slash, or the posting's phrase written in a different order.

Then do the thing no tool can: read the line aloud in that language. If "fluent" felt like a stretch, write B2.

The rest of the Skills section follows the same logic, and the [skills section guide](/blog/skills-for-resume) and the [resume keywords by job](/blog/resume-keywords) count show which other terms postings actually carry.

<div class="blog-takeaway">
  <p class="blog-takeaway-head">Key takeaways <span>before you send the next one</span></p>
  <div class="blog-takeaway-list">
    <div class="blog-takeaway-item">
      <span class="blog-takeaway-num">01</span>
      <p class="blog-takeaway-text">
        Write the language name in full, then the posting's own phrase, then a scale letter and a dated score. No flags, codes, slashes or dots.
      </p>
    </div>
    <div class="blog-takeaway-item">
      <span class="blog-takeaway-num">02</span>
      <p class="blog-takeaway-text">
        Place yourself on the Europass descriptor you could demonstrate on a call tomorrow, and never write C2 from a TOEIC score.
      </p>
    </div>
    <div class="blog-takeaway-item">
      <span class="blog-takeaway-num">03</span>
      <p class="blog-takeaway-text">
        Give languages their own section only when the posting asks; otherwise one line in Skills is enough.
      </p>
    </div>
  </div>
  <p class="blog-takeaway-next">
    Two minutes to find out what the matcher reads:
    <a href="/ats-checker">run your resume against the posting</a>.
  </p>
</div>

## Read next

- [Nursing skills for your resume: 30 to list, and how 60 hospital postings word them](https://hiredfolio.com/blog/nursing-skills)
- [Customer service skills for your resume: what 44 support job ads ask for](https://hiredfolio.com/blog/customer-service-skills)
- [Resume objective: 30 examples by job and how to write one (2026)](https://hiredfolio.com/blog/resume-objective)
