Vague language claims like "speaks Spanish" often get lost in an ATS parse, while specific, standardized phrasing gets recognized reliably. The fix isn't adding more languages — it's phrasing the ones you already have so both the software and the recruiter reading it afterward can find them.
Here's exactly how to structure a bilingual or multilingual resume for ATS parsing, with real before/after phrasing you can copy directly.
This matters beyond the initial parse, too. A recruiter who searches an ATS database for "German fluent" or "Spanish, professional proficiency" is typing the standardized term they expect a qualified candidate to have used — a resume phrased any other way simply won't surface in that search, regardless of how strong the candidate actually is.
Why vague language listings get missed
Key Takeaway
ATS keyword matching looks for specific, standardized terms — vague phrasing like "speaks a bit of French" doesn't map cleanly to anything.
An ATS scans for keywords, job titles, and structured sections like "Skills" or "Work Experience." Language ability described loosely — "comfortable speaking Spanish," "some German" — doesn't map cleanly to the specific terms a job posting or recruiter search is looking for, which usually favor standardized proficiency words like "fluent," "native," or "professional proficiency."
There's a specific edge case worth calling out: resumes that mix two languages within the same document. A candidate might keep an official job title in French because that's the title on their diploma or employment contract, or paste in a line from a reference letter written in Portuguese. An ATS parser generally assumes a document is written primarily in one language, so a stray sentence or heading in another language can get mis-tagged, skipped entirely, or — in the worst case — cause a parsing error that scrambles the fields around it. If a foreign-language term is essential (an official title, a certification name), keep it in parentheses next to the English translation rather than letting it stand alone.
Proficiency claims also need to distinguish between how a language was learned, not just how well it's spoken. A heritage speaker who grew up speaking Tagalog at home but never studied it formally may have excellent conversational fluency but weak formal writing skills — "native" can overstate the writing side, while "conversational" can understate the speaking side. A classroom-learned language, by contrast, might read well on paper (grammar, vocabulary) but lack the fluency of real conversation. Being precise about which is true for you — "native speaker, conversational writing" or "professional working proficiency, self-taught" — protects you from a mismatch between what the resume promises and what an interview conducted partly in that language reveals.
How ATS platforms handle accents, scripts, and encoding
Key Takeaway
Modern ATS platforms generally handle accented Latin characters fine, but non-Latin scripts, scanned PDFs, and unusual fonts can still break text extraction entirely.
Most current ATS platforms parse Unicode text, which means accented characters — é, ñ, ü, ç — are usually extracted correctly from a standard, text-based PDF or Word document. That said, older or poorly configured systems can still choke on them, occasionally dropping the accent or replacing it with a garbled symbol. If your legal name contains an accented character, it's worth also checking how it renders after upload — a resume checker will show you the parsed text so you can catch this before a real application goes out.
Non-Latin scripts are a bigger risk. Cyrillic, Arabic, Hebrew, and CJK (Chinese, Japanese, Korean) characters may not parse reliably in a resume submitted against an English-language job posting, and some ATS search tools simply can't keyword-match against them at all. If you're applying to a role posted in English, write the resume itself in English and keep any non-Latin script — your name in its original characters, for example — as a small, secondary addition rather than the primary text of a section.
Font and file format choices matter more than most candidates expect. A resume exported as a flat image (a scanned document, or a PDF saved from a photo) has no extractable text at all — the ATS sees a picture, not words, regardless of what language it's in. Decorative or unusual fonts, especially ones bundled to render specific scripts, can also fail to embed properly when a PDF is generated, which sometimes turns clean text into a string of missing or replacement characters (often shown as boxes or question marks) once it's parsed. Stick to standard, widely supported fonts (Arial, Calibri, Georgia, Times New Roman) and always export to a text-based PDF, then confirm the exported file is still selectable and copyable text before you submit it anywhere.
Encoding mismatches cause a subtler failure. Smart quotes, em dashes, and apostrophes auto-corrected by a word processor set to a non-English locale can sometimes convert incorrectly when the document is saved or converted to PDF, producing mojibake — strings like ’ where an apostrophe should be. This rarely breaks the whole document, but it can corrupt exactly the punctuation inside a language proficiency line, a job title, or a company name, which is often the detail an ATS or recruiter is trying to match against.
Before and after: real phrasing fixes
Key Takeaway
Standardized proficiency terms plus a concrete, relevant example beat a vague claim every time.
Before: "Fluent in Portuguese."
After: "Bilingual Marketing Specialist (English/Portuguese); led client communications for two Brazil-based accounts."
Before: "Speaks Spanish, French, German."
After: "Languages: Spanish (native), French (professional proficiency, DELF B2), German (basic)."
Before: "Resolved customer inquiries."
After: "Resolved customer inquiries in English and Arabic for a bilingual support queue, reducing average handle time by 15%."
Before: "Trilingual: English, Mandarin, Cantonese."
After: "Medical Interpreter (English/Mandarin/Cantonese); provided certified interpretation for patient intake, discharge instructions, and consent forms in a hospital outpatient setting."
Check your own phrasing before you apply.
Run your resume through HireFlow's free ATS checker to confirm your languages section and job titles parse cleanly.
How to structure the languages section
Key Takeaway
A dedicated, plainly formatted section plus one real on-the-job example beats scattering vague mentions throughout the resume.
- Create a dedicated "Languages" section near Skills or Education.
- List each language with a standardized proficiency term: native, fluent, professional proficiency, conversational, or basic.
- Add a certification if you have one (DELE, DELF, CEFR level, TOEFL) for extra specificity.
- Reference at least one language in a real Experience bullet if you've genuinely used it on the job.
- Use plain text, standard fonts, and simple bullet points — no tables, icons, or proficiency "bars."
Order matters more than most candidates realize. List languages in the order most relevant to the role, not necessarily the order you learned them — a native Spanish speaker applying to a role that requires French should still lead with whichever language the job actually needs, then note native Spanish afterward. Recruiters scanning quickly, and some ATS keyword logic, will weight the first item in a list slightly more than the last.
A resume written partially in two languages — sometimes done intentionally to signal fluency — usually backfires. If the job posting is in English, submit the resume entirely in English and let the dedicated Languages section, plus any bilingual job titles you actually held, do the work of proving your ability. A resume that switches languages mid-document, even with good intentions, tends to read as unpolished and can trip up both keyword search and a human skimming it in ten seconds.
If you're a heritage speaker rather than someone who studied formally, it's fine — and more accurate — to note that distinction directly: "Vietnamese (native, spoken; conversational written)" is a completely legitimate line, and it's more useful to a recruiter than a plain "native" claim that later doesn't hold up if a task requires formal written correspondence.
Phrasing language skills for specific industries
Key Takeaway
The right phrasing depends on whether the role treats language as the core job or as a supporting skill — say which one applies to you.
Translation and localization
For roles where language is the job itself, lead with the language pair using the standard industry format: "English → Spanish translation" or "EN/FR localization." Name the tools you use (CAT tools, translation memory software) as their own keywords, and list any subject-matter specialization — legal, medical, technical documentation — since that's often what a search is actually filtering for, not just the language pair alone.
International sales and business development
Here, language is a means to an outcome, so tie it to territory and result rather than listing it alone: "Managed accounts across the DACH region in German and English" reads far stronger than "German speaker." If you negotiated contracts, closed deals, or ran demos in a second language, say so directly — that's the detail a hiring manager for an international role is actually screening for.
Customer support and client services
Phrase this around the queue or channel you supported: "Handled a bilingual English/Korean support queue" or "Provided Spanish-language phone and chat support." If your team tracked any language-specific coverage metric — being the only Vietnamese-speaking agent on a shift, for instance — a brief, honest mention of that scope adds useful context without requiring a specific number.
Healthcare and interpreter roles
Precision matters most here, since miscommunication has real consequences. Use the exact credential if you have one — "Certified Medical Interpreter" or "Qualified Bilingual Staff" — rather than a general proficiency term, and specify the clinical context (patient intake, discharge instructions, informed consent) where you've actually interpreted. A vague "fluent in Spanish" on a healthcare resume undersells a credential that recruiters in this field are specifically searching for by name.
Common mistakes to avoid
Key Takeaway
Precision and honesty beat both vagueness and exaggeration — an ATS and an interviewer will both eventually test the claim.
- Vague descriptions: "speaks French" reads weaker than "French (professional proficiency)."
- Listing too many languages at low proficiency: dilutes focus and can look padded.
- Non-standard formatting: proficiency icons, star ratings, or tables can break ATS parsing.
- Overstating fluency: a language claim that doesn't hold up in an interview conducted partly in that language damages trust fast.
- Using the foreign-language name instead of English: "Español" instead of "Spanish" can be missed by keyword matching on an English-language posting.
- Mixing languages mid-document: a stray heading, bullet, or job title left untranslated can confuse parsing and looks unfinished to a reviewer.
- Blurring heritage fluency with formal training: claiming "native" when writing ability is weaker than speaking ability (or vice versa) sets up a mismatch that surfaces in an interview or on the job.
Most of these mistakes share a root cause: treating the languages section as an afterthought rather than a real part of the resume. Giving it the same care as your job titles and skills — consistent formatting, standardized terms, and at least one concrete example of the language in use — is usually enough to fix all of them at once.
Frequently asked questions
Only if it's relevant to the role or genuinely notable. Listing five languages at conversational level can dilute focus; two or three languages at a clear, honest proficiency level read as stronger than a long, vague list.
Run it through a free ATS checker and confirm your languages section, job titles, and contact details are all being parsed correctly, then check keyword overlap against a specific job description.
Use the English name ("Spanish" rather than "Español," "German" rather than "Deutsch") for a resume submitted to an English-language job posting. ATS keyword matching and human readers both rely on the standard English term.
Yes, and it strengthens a vague claim. "Spanish (DELE B2)" or "French (CEFR C1)" is more specific and verifiable than "fluent," and gives both a recruiter and an ATS keyword match a concrete term to latch onto.
No. They complement rather than replace core skills. Tie language ability to a real, relevant achievement (client communication, translation, cross-market work) rather than listing it as a standalone credential.
Most consumer ATS checkers, including HireFlow's, are optimized for English-language resumes and job descriptions. If your resume itself is written in another language, results may be less reliable — write the resume in English with language skills listed as a section for the most accurate check.
Avoid duplicating full sections in two languages on one document. Pick the language the job posting is written in for the resume itself, then use a dedicated Languages section to note your other language skills — a side-by-side bilingual layout tends to confuse ATS parsing and reads as unfocused to a recruiter.
Use "basic" or "elementary proficiency" and optionally add "(currently studying)" in parentheses. Don't claim conversational or professional proficiency for a skill still in progress — be ready to demonstrate whatever level you list if it comes up in an interview.
Done for you
Turn this advice into an interview-ready resume
Professional writers rebuild your resume for ATS + recruiters — unlimited revisions, interview guarantee.