How to List Languages on Your Resume (With Proficiency Levels)

These numbers make a clear case: language skills are valuable, but they're invisible on most resumes. The gap exists because most job seekers don't understand which proficiency framework to use or where employers expect languages to appear. Meanwhile, employers have developed an unconscious skepticism toward language claims because they see so many vague or exaggerated ones. That skepticism disappears the moment you use a professional, standardized framework.

The ACTFL and CEFR frameworks exist primarily for educational and formal testing contexts. Unless you have a certification to back them up, they're harder for employers to evaluate. The ILR scale is too niche unless you're applying to government jobs. For 95% of job seekers and employers, the LinkedIn/Resume Descriptor framework is the right choice. It's widely understood, requires no certification, and clearly communicates your ability level to someone who's not a linguist. If you're applying for a role in government, defense, or intelligence, shift to the ILR scale. If you have a formal language certification (TOEFL, DALF, DELE, etc.), include both the certification name and the proficiency level for extra credibility.

The key distinction: don't confuse proficiency with how long you've studied or where you learned the language. A native speaker of Spanish has native proficiency. Someone who lived in France for five years and uses French daily at work has professional proficiency. Someone who passed the DELF B2 exam and can handle business emails but struggles with nuance has professional working proficiency. Employers care only about what you can do, not how you got there. Be ruthlessly honest with yourself. If you can't conduct a 30-minute business meeting in the language without a translator, you don't have "professional" proficiency. Overstating your level is one of the fastest ways to get screened out—many employers test language claims in the interview or initial phone screen, and failing that test signals dishonesty about everything else on your resume.

Language demand varies dramatically by industry and geography. If you're in healthcare, Spanish is non-negotiable. In finance or tech, Mandarin and Japanese open doors to high-paying roles. In legal and government, the demand is driven by formal policy, which is why those sectors specifically require ILR scale proficiency. Geography matters too: bilingual Spanish speakers in border states command higher premiums than those in monolingual markets. If you're in an industry or region where your languages have less direct value, position them strategically (see "Where to Place Languages" below). If you're in a high-demand sector, make sure your language section is impossible to miss.

The decision is simple: if the job description mentions language requirements or if languages are central to the role (sales to Spanish-speaking markets, support for Japanese clients, translation work), create a dedicated "Languages" section and place it high on the resume—right after your summary or core competencies and before work experience. If languages are a "nice-to-have" or an unexpected bonus, include them in your general Skills section near the bottom. The positioning signals how important the skill is to the role. Recruiters scan resumes in a top-to-bottom pattern, so top placement ensures your languages get reviewed in the critical first 7.4 seconds.

The after version works because it removes all ambiguity. Every language gets one line, with a clear framework. The employer knows exactly what they're getting. There's no room for interpretation, and the resume passes ATS screening because you're using standard terminology. The before version fails because "a little" and "some" don't trigger ATS keyword matching (the system is looking for "proficiency," "native," "professional," etc.), and a human recruiter can't trust the claims.

The most valuable language on your resume isn't the language you speak—it's the language of clarity. Tell the employer exactly what you can do, using a framework they recognize, and they'll stop guessing and start hiring.