# Listing languages and skills on a resume honestly

> Name each language with a level a stranger can understand, say what you can do in it, and list a skill only if you have used it. Show how recently or how often you used each skill. An honest line holds up in the interview, and an inflated one is usually caught there.

Source: https://zorlya.com/blog/listing-languages-and-skills-on-a-resume-honestly

By Zorlya. Published 2026-09-12, updated 2026-10-25. Resumes and applications. 8 min read.

A skills section is the part of a resume most likely to be tested out loud. An interviewer reads "Advanced Excel" or "Fluent in French" and asks you to show it. If the line was generous, the next five minutes are uncomfortable. This post gives you a way of listing languages and skills on a resume so each line is accurate, specific and still strong.

## Why a vague level does not help

Words like "fluent", "advanced" and "good knowledge" mean different things to different people. A reader in one country may hear "fluent" and expect you to negotiate a contract. A reader in another may use the same word for someone who can chat. Because the word is unreliable, the reader tests it.

Star ratings and percentage bars are worse. "Python: 80%" has no meaning, because nobody knows 80% of what. Leave them out. Give the reader something they can check: a level with a plain description, or a fact about how you used the skill.

## Languages: a level, plus what you do in it

Write each language on its own line with a level and one concrete use. For your first language, say so: "Bengali (native)".

For other languages, many employers and schools use the Common European Framework of Reference for Languages, or CEFR. Its [self-assessment grid, published on Europass](https://europass.europa.eu/system/files/2020-05/CEFR%20self-assessment%20grid%20EN.pdf), has six levels in three bands:

| Level | Band in the grid | Example of what the grid describes |
|---|---|---|
| A1, A2 | Basic user | Simple everyday exchanges and short, simple texts |
| B1, B2 | Independent user | The main points of familiar matters, then clear detailed text on a wide range of subjects |
| C1, C2 | Proficient user | Fluent, flexible use for social, academic and professional purposes, then ease with virtually everything heard or read |

### How does the grid describe each skill?

The grid describes each level separately for listening, reading, spoken interaction, spoken production and writing, so your level can differ between them. Reading the grid row by row is a fair way to place yourself if you have never taken a test. If you took a test and know the result, write the level and the year: "English, C1 (tested 2024)". If you were never tested, do not guess a letter. Use plain words instead: "Professional working proficiency: I write reports and lead meetings in English." Or: "Conversational: I handle daily talk and read documents with a dictionary." Or: "Basic: greetings and simple questions."

The part after the colon does the real work. It tells the reader what you could do on your first day.

If you write your resume in English as a second language, the resume itself is the first sample of your English. A clean, plain resume is better evidence than any label. Ask someone to read it once for errors.

Some postings name a language and no level. Others set a required level or test score, especially in public-sector and international roles. That rule differs by employer and country, so check the employer's own page for the exact requirement before you decide how to describe yourself.

## How should I order and lay out languages?

Put your first language first, then the others from strongest to weakest. Use one scale for every language on the page, so the reader can compare them. If one skill is clearly weaker than the rest, say so in the line.

Illustrative: the person is invented. A languages section for someone applying to an office role in Lisbon:

- Bengali: native
- English: C1 (tested 2024). Write reports and run client calls in English
- Portuguese: B1 in speaking and listening, A2 in writing. Handle daily talk at work, and write short emails with a spell checker
- Hindi: conversational. Follow films and everyday talk, no reading

Every line says what the person can do on day one, and the Portuguese line is honest about the gap between speaking and writing. An interviewer who switches to Portuguese for two minutes finds what the page promised.

## Where should languages go on a resume?

If the posting asks for a language, put the languages near the top, or in their own short section, so a reader finds them in seconds. If no language is asked for, a short section near the end is enough. Put a test certificate in that section with the year, and repeat it under certificates only if you have a certificates section anyway.

## Skills: only what you have used

Use one test for every skill on the page: could I answer a hard question about this tomorrow without preparing? If yes, list it. If you did a one-hour tutorial two years ago, leave it out.

There are honest ways to show depth without a rating. Attach the skill to work, inside a bullet: "Built the monthly budget report in Excel, with pivot tables, for a team of 12." Then the skills section only repeats what your bullets already prove. Show recency with a short note such as "used daily since 2021" or "used from 2019 to 2021", so the reader can weigh it. And split the list by confidence into two small groups, "Use regularly" and "Have worked with". A third group called "Familiar with" tends to read as padding.

## Copying words from the posting

Postings name tools in particular ways, and it helps to use the posting's own name when it is true. If the posting says "project management" and you wrote "managing projects", change yours to match. Recruiters and applicant tracking systems search for words, so a matching term is easier to find. The post on [what an applicant tracking system does with your resume](/blog/what-an-ats-does-with-your-resume) explains those searches.

Do not add a tool you have never touched because the posting names it. That is where tailoring turns into a false claim. The post on [tailoring one resume in 20 minutes](/blog/one-resume-or-many-tailor-in-20-minutes) lists what is safe to change: order, emphasis and wording, never facts.

## Check each line before you send

Go through every language and skill once with these questions.

- Would a former colleague agree with this level?
- Can I name a project or a result for this skill?
- If the interview switched to this language or tool for ten minutes, would I be comfortable?
- Is the date or the duration correct?

A line that fails two of the four needs rewording or removing.

## A lower level that is true still works

Many people think a modest level will lose them the job. A modest level that is true usually leads to a better conversation. "Conversational Spanish, currently studying" tells an employer you are working on it, and some roles need nothing more. A claim that collapses in the interview costs you more than that line, because the reader starts to doubt the rest of the resume.

Some roles do set a hard requirement, such as a language needed to serve the public. If you do not meet it, applying is unlikely to work, and your time is better spent on roles where your real level fits.

## Questions people ask

### Should I list a language I am still learning?

Yes, with its true level and the word "studying" if that is so. "Spanish: A2, studying" is honest and shows effort. Leave out a language you only know a few words of.

### What if I have no test score?

Use the grid to place yourself, or plain words that say what you can do. Do not write a level you guessed as if a test gave it.

### Should I use stars or bars for skills?

No. A bar has no scale a reader can check, and "80%" invites the question of what the other 20% is. Use words, years and examples.

### How many skills should I list?

As many as you can back up in an interview, and no more. A short list you can defend is stronger than a long one you cannot.

## What we know and what we do not

If you use Zorlya, the skills on your profile are one of the four parts every job's score has. They are compared with the skills a posting names, after spelling variants such as "React.js" and "ReactJS" are treated as one skill. The method is in [how Zorlya scores a job](/blog/how-zorlya-scores-a-job). A skill you list but cannot back up raises a score that your work does not support, which helps nobody. The score does not read spoken languages as a separate part, and Zorlya does not test or check the levels you give. A posting's language requirement is something to read in the posting itself, and the employer decides how to test it.