How to List Languages on a Resume (Levels & Formatting)

List languages in a dedicated Languages section near the bottom of your resume, each with a clear proficiency level, for example Spanish (Fluent) or German (Conversational). Use plain text, never bars or star ratings, so applicant tracking systems can parse it. If the posting asks for a language, repeat it in your summary and skills section too.

Yes, if you speak it at a conversational level or better. A real second language is one of the few resume lines that can win a tie-break on its own, and in some industries it is a hard requirement the applicant tracking system (ATS) screens for before a human reads a word.

Which industries those are is where most advice goes vague. When Roleframe's job analysis agents break down postings to extract the keywords recruiter filters actually scan for, bilingual requirements cluster in a handful of fields. Patient-facing healthcare postings regularly list "bilingual Spanish" as a must-have that recruiters filter on. The same pattern holds in customer support, inside sales, social work, and K-12 education. In those pipelines, a missing language keyword can mean the filter never surfaces you at all.

In software engineering and most corporate office roles, the pattern flips. A second language shows up as a nice-to-have and almost never as a screened keyword. List it anyway, since it helps with global teams and close calls between finalists, but keep it low on the page.

The question is rarely whether to list a language. It is how prominently. Almost everyone with a real second language should include it; the industry decides whether it belongs in your opening lines or in a quiet section at the end.

Most US resumes use a five-level scale adapted from the Interagency Language Roundtable (ILR), the framework the US government uses to grade language ability. LinkedIn uses the same wording, which is why recruiters recognize it instantly.

If you're torn between two levels, claim the lower one. Interviewers who speak the language often switch into it mid-conversation to check, and getting caught a level short costs more credibility than a modest label ever would.

The Common European Framework of Reference (CEFR) grades languages from A1 (beginner) to C2 (mastery). It is the standard on European CVs and carries weight in the US mainly when a certificate backs it up. If your recruiter pool might not know the codes, pair them with plain English.

Default placement is a dedicated Languages section near the bottom of the page, after your skills. That keeps the resume scannable and gives ATS parsers a clean, labeled section to read.

Move the language up when the posting mentions it. If "bilingual" or a specific language appears in the requirements, put it in three places. Your professional summary, so the recruiter sees it in the first seven seconds. Your skills section, so keyword filters catch it. And the Languages section itself, with the proficiency level spelled out.

If you speak one extra language and space is tight, folding it into your skills section as "Spanish (Fluent)" works fine. Skip the header trick where people write "Bilingual" next to their name; contact headers are the part of a resume that parsers misread most often. For a full breakdown of what goes where, see our guide to resume section order.

ATS parsers read text, and only text. Progress bars, dots, star ratings, and flag icons all parse as nothing, which means a beautifully designed language chart can leave the keyword "Spanish" entirely absent from your parsed profile.

Safe formatting is boring on purpose. Use the section header "Languages" since parsers are trained on it. Write one language per line, or one comma-separated line, with the proficiency level in parentheses.

If you'd rather not build this by hand, Roleframe's resume editor includes a dedicated Languages section and a set of ATS-friendly templates to choose from, so the section header, plain-text formatting, and parseable structure are handled for you.

Mirror the posting's wording. If the job says "bilingual English/Spanish," the word "bilingual" should appear on your resume, ideally in the summary. Keyword filters match strings, and "fluent in Spanish" does not always match a filter set to "bilingual." Our guide to ATS resume keywords covers the matching logic in detail.

Export as PDF. A text-based PDF parses cleanly in every modern ATS and locks your formatting so the recruiter sees exactly what you built. Send a .docx only if an employer explicitly asks for one. For layout rules beyond the languages section, see how to make your resume ATS-friendly.

If you could not hold a five-minute work conversation in the language, leave it off. That is the whole rule.

The trap catches people constantly. Three years of high-school Spanish or a long streak in a language app feels like it should count for something, so it lands on the resume as "Spanish (Basic)." Then the hiring manager, who grew up speaking Spanish, opens the interview with a friendly question in it. The candidate freezes, and suddenly every other line on the resume looks inflated too.

A weak language line also crowds out stronger material. A recruiter scanning your skills spends attention on everything you list, and "French (Beginner)" spends it badly.

Two honest exceptions. If you're targeting roles in a country whose language you're learning, "German (A2, actively learning)" signals commitment to relocation and sets expectations correctly. And when a posting genuinely values basic ability, hospitality and travel roles sometimes do, a clearly labeled basic level is fair game.

When a posting screens for a language, your summary is where it has to appear, because that is where a recruiter's first-pass scan lands. Lead with it, and attach it to the credential that matters most for the role.

Notice the pattern. The language never stands alone; it is tied to the work it enabled. "Bilingual" as a bare adjective is a claim, while "serving Spanish-speaking patient populations" is evidence. The same logic works in experience bullets. A line like "Handled Spanish-language patient intake and discharge instructions for roughly a third of the daily caseload" proves the skill in a way no proficiency label can. For more on writing an opening that survives the seven-second scan, see how to write a professional summary.