How to List a Second Language on a Resume Without Overstating Your Proficiency

Name the language and describe the level you can defend in a work conversation. Do not call yourself fluent because you can manage a basic exchange. If your reading, speaking, and writing differ, say so; use a recognized framework or test result when it is relevant and accurately reported.

!A candidate considers how to describe different language skills on a resume.

The safest resume entry is specific enough to be useful and modest enough to survive follow-up questions. “Spanish - conversational” is clearer than “Spanish - fluent” when you can discuss familiar topics but would struggle to lead a client negotiation. If you read well but speak haltingly, say that. A hiring manager needs a realistic picture, not a bigger adjective.

A language line is a claim about what you can do. Treat it like any other resume claim: make it relevant, concrete, and supportable. Harvard’s resume guidance recommends specific, fact-based language, while UC Berkeley advises connecting listed skills to experience and the employer’s needs. Harvard’s resume guide and Berkeley’s resume guidance support the same practical rule: tell the reader what is true and relevant, not what sounds impressive.

The best default: name the language and the level you can defend

Use a short label that matches your ordinary ability in the settings the job may require. A hiring manager should be able to ask a reasonable follow-up question without exposing a mismatch between the word on the page and your actual skill.

Examples of concise entries include:

• Languages: Spanish - conversational
• Languages: French - intermediate; English - fluent
• Languages: Arabic - professional working proficiency
• Languages: Japanese - advanced reading; basic spoken conversation

These are hypothetical examples, not claims about real candidates. Choose the wording that fits your own ability. “Conversational” should not mean you can greet someone and exchange a few memorized phrases. It should mean you can sustain ordinary conversation in a defined range of contexts. “Professional working proficiency” should not mean you know some industry vocabulary. It should mean you can perform relevant work tasks in the language at the level you claim.

The best label is not always the most familiar one. “Fluent” has no single meaning that every employer applies in the same way. A reader may infer that you can handle unfamiliar questions, keep a conversation moving, and explain your ideas without frequent help. If that is not reliable, use a narrower description.

Your resume does not need to settle every nuance of your language ability. It needs to avoid promising more than you can deliver. A well-chosen phrase gives a credible signal and leaves room to explain the details in an interview.

Why broad labels can mislead

Words such as “basic,” “conversational,” “proficient,” and “fluent” are convenient, but they are not precise measurements by themselves. Different people use them differently. One person may call themselves conversational because they can chat with relatives; another may mean they can handle a work call about scheduling and routine issues.

“Fluent” is the riskiest broad label when it stands alone. It can suggest ease across topics, contexts, and language skills. But language ability is not one single switch. You may understand a fast conversation but write slowly. You may read technical documents well but find spontaneous speech difficult. You may speak comfortably about familiar topics yet struggle with formal presentations.

“Proficient” is also easy to overstate. It sounds like a strong claim, but does not tell the reader what you can do. If you choose it, consider adding a task or skill qualifier: “professional proficiency in written French” or “proficient in reading German technical documentation.” A narrower claim can be more impressive because it is more credible.

“Basic” has the opposite problem. It can understate useful ability, or leave the reader unsure whether you mean basic greetings, routine conversation, or beginner coursework. Replace it with a concrete description where space allows: “basic spoken Italian for greetings and simple directions” is more informative than “Italian - basic.”

A resume is a short document, so no label can describe every situation. Still, you can make the label less ambiguous by naming the skill, context, or limitation that matters most. Avoid treating a vague adjective as a substitute for evidence.

Separate speaking, listening, reading, and writing

Language ability often varies by skill. Separate the skills when the difference affects the job or changes the meaning of your overall label.

The Council of Europe’s Common European Framework of Reference for Languages, or CEFR, uses “can-do” descriptors and distinguishes activities such as listening, reading, spoken interaction, spoken production, and writing. Its self-assessment grid includes multiple scales rather than one all-purpose label. The Council of Europe’s CEFR self-assessment grid is a useful prompt for examining those differences. The framework does not make a resume claim true by itself; your description still has to reflect your current ability.

Here are hypothetical examples for uneven skill profiles:

• Strong reading, limited speaking: “Portuguese - advanced reading; basic spoken conversation.”
• Comfortable listening, slower writing: “Spanish - conversational listening and speaking; intermediate writing.”
• Professional speaking, limited formal writing: “French - professional spoken communication; intermediate written French.”
• Strong workplace writing, hesitant spontaneous speech: “German - professional written communication; conversational speaking.”
• Can follow meetings but not lead them: “Mandarin - intermediate listening; basic spoken interaction.”
• Understands familiar topics, needs time for unfamiliar ones: “Korean - conversational on familiar topics; developing business vocabulary.”

These examples are hypothetical. Use only wording that matches what you can do without inventing a work history or skill.

A useful test is to picture a task, not a language class. Could you read a short customer email and understand its request? Could you answer a follow-up question without switching languages? Could you write a clear reply without translating every sentence word by word? The answer may differ for each skill. That is not a flaw. It is information.

Do not list every skill separately if the job does not need that level of detail. For a role where the language is incidental, one honest overall phrase may be enough. For a role that depends on written communication, distinguish writing from speaking. For a customer-facing position, listening and spoken interaction may matter more. Match the detail to the work.

What “conversational” should mean

“Conversational” is a useful label when you can hold a real exchange on familiar topics, not merely recite prepared phrases. You can ask and answer questions, understand the general point, and recover when you miss something. You may still pause, search for words, or need the other person to repeat a sentence.

The word does not automatically mean business-ready. A friendly conversation about food, family, or travel is different from explaining a delayed shipment, clarifying a contract term, or calming an upset customer. If your conversational ability is limited to familiar situations, say so when the distinction matters.

Hypothetical examples:

• “Spanish - conversational for everyday topics; not yet suitable for customer negotiations.”
• “Italian - conversational speaking and listening; limited professional vocabulary.”
• “French - conversational in familiar settings; intermediate reading.”

The parenthetical limitation is not self-sabotage. It prevents a reasonable reader from assuming more than you mean. If the language is not central to the role, you can keep the resume entry shorter and discuss scope if asked.

Test your label with an unscripted conversation. Could you talk for several minutes about a familiar subject? Could you ask for clarification? Could you understand a reply you did not expect? If every exchange depends on rehearsed lines or your conversation partner’s patience, “conversational” may be too strong. Use “basic spoken ability” or describe the specific tasks you can handle instead.

Do not confuse confidence with capability. A person may feel nervous and still communicate effectively. Another may feel relaxed in casual conversation but lack the vocabulary for a workplace setting. Judge the actual tasks, not your self-image.

When “professional working proficiency” fits

“Professional working proficiency” should point to real work tasks you can perform, not merely a wish to work in the language. The phrase is useful when you can handle at least some routine professional communication independently. But it remains broad, so narrow it if the job relies on a particular skill.

Ask yourself what “working” means for this position. It could mean answering routine questions, reading instructions, writing short updates, or contributing to internal discussions. It might not mean negotiating a complex agreement, interpreting legal documents, or delivering a polished presentation. Do not let a broad label imply all of those abilities if you have only practiced one.

A more useful resume line often names the task:

• Hypothetical: “French - professional proficiency in routine written customer correspondence.”
• Hypothetical: “Spanish - can handle scheduling calls and routine service questions; developing formal writing.”
• Hypothetical: “German - comfortable participating in internal project discussions; not a translator.”

Only include a task description if it is true. Avoid using “professional” as a credibility shortcut. A person can use a second language at work and still need support for complex or high-stakes communication.

If a job requires interpreting, translating, legal drafting, medical communication, or another specialized language task, ordinary proficiency may not establish qualification. Those duties can demand separate training, subject knowledge, or credentials. State what you actually have. Do not imply that you are qualified for a regulated or sensitive task simply because you speak the language.

What “fluent” should mean on a resume

Use “fluent” only when you can defend the broad implication the word is likely to carry in the context of the job. There is no universal resume definition that makes “fluent” safe in every situation. The test is not whether you once completed an advanced course, lived abroad, or can talk comfortably about familiar subjects. The test is whether your current ability supports the expectation a reasonable interviewer could form from the word.

If the role requires you to speak with clients, expect the interviewer may ask a question in that language. If it requires written communication, expect a writing exercise or a discussion about documents you have handled. These are possibilities, not guaranteed hiring practices. Prepare because your resume creates an expectation, not because every employer uses a particular test.

“Fluent” may be a fair description for someone who can communicate readily across a broad range of work and everyday situations, including responding to unexpected questions. Even then, avoid letting the word imply expertise you do not have. Fluency is not the same as industry knowledge, perfect grammar, or authorization to interpret sensitive material.

If you are unsure whether “fluent” fits, select a more specific and defensible phrase. “Advanced spoken Spanish” or “professional French for meetings and routine correspondence” tells the reader more and stakes less on a vague label. A modest, accurate claim is stronger than an inflated claim that invites doubt.

Use a recognized framework or test when it adds useful evidence

A recognized framework or test result is the strongest exception to plain-language labels when the result is relevant, current enough for the purpose, and accurately reported. It gives the reader a reference point. It does not eliminate the need to explain what the result measures or whether it reflects the tasks in the job.

The CEFR describes six common reference levels, A1 through C2, using “can-do” descriptors. The Council of Europe explains that the framework distinguishes language activities, domains of use, and competencies, and that its self-assessment materials organize abilities by activity and level. Its overview of the CEFR explains the framework’s purpose and scope. A CEFR level can be useful if you know how it was established. Do not assign yourself a level casually because a course certificate, app, or informal quiz used the same letters.

If a formal exam produced the result, name the exam and date when that detail helps the reader assess it. For example, a hypothetical entry might say: “French - B2 CEFR, exam result earned in 2024; strong reading and listening, developing spoken confidence.” This does not claim that every B2 speaker has identical strengths. It tells the reader what reference you are using and adds an individual qualification.

A test result is evidence of performance on that test under its conditions. It is not a permanent guarantee of current ability, nor proof of competence in every professional setting. A result from several years ago may still matter, but say when you earned it if recency could change the reader’s interpretation. If your daily use has improved or declined since then, explain the current level as well.

A framework is more useful when the job posting names it, the employer works across countries where it is familiar, or the role calls for a specific language threshold. If the job asks for “business-level Spanish” and you have an exam result, give both the result and the relevant task evidence. If the job does not care about the framework, a clear plain-language description is usually easier to read.

Do not treat a test result as a universal translation of your skills. Different assessments may focus on different tasks, and an overall score can conceal a weaker skill. The CEFR’s own grid separates multiple activities; use that distinction when it matters. If a result reports only reading, do not let the resume imply that it measured speaking too.

A practical self-check before choosing a label

Choose the label after testing yourself against ordinary tasks. This table is a private calibration aid, not an official scoring system. It is not a substitute for a formal assessment, and it does not certify a level. Use it to identify which claims you can support without stretching.

Use the weakest skill that is essential to the job as a check on your overall label. If the role mainly involves reading technical material and you read well, your speaking weakness may not matter much. If the role involves live customer support, it matters a great deal. A strength in one skill does not erase a limitation in another.

Try a three-column note before writing the resume line:

1. Task: What would I need to do in the language?
2. Evidence: What have I actually done or what can I demonstrate now?
3. Boundary: Where would I need more time, help, or a different language?

A hypothetical candidate might write: “Task: answer routine Spanish calls. Evidence: can explain appointment times and ask follow-up questions. Boundary: cannot yet handle complaints about billing.” The resulting resume wording could be “Spanish - conversational; comfortable with routine scheduling calls.” That claim is narrow, practical, and defensible.

Do not manufacture work evidence to make the entry sound stronger. If you have not used a language at work, describe your skill directly or leave it off. Coursework, community use, family conversation, and self-study can all help you learn, but do not turn them into professional experience you did not have.

Hypothetical wording for uneven language ability

Uneven ability is common, and it is usually more honest to name the difference than to average every skill into one misleading label. These examples are hypothetical. They do not describe real candidates, and they should not be copied unless the underlying claim is true.

You read well but speak slowly

Try: “Japanese - advanced reading; intermediate spoken conversation.”

If the role requires reading documentation but little conversation, that is useful. If the job requires live customer calls, the limitation deserves more attention. Do not write “fluent Japanese” based on reading ability alone.

You speak comfortably but write with errors

Try: “Spanish - conversational speaking and listening; intermediate writing.”

If writing formal client messages is central, state the boundary in the resume or be prepared to discuss how you check your work. Do not imply polished business writing simply because conversation feels easy.

You understand speech but struggle to respond quickly

Try: “French - intermediate listening; basic spoken interaction.”

This distinction can matter in a role where you listen to calls, follow meetings, or respond in real time. If the job requires only reading, lead with reading instead.

You can speak about work but not every topic

Try: “German - professional spoken communication for routine project discussions; limited formal writing.”

That is narrower than “fluent,” but more useful. Do not call a small set of rehearsed phrases professional proficiency. The wording should describe independent, repeatable ability.

You learned the language years ago and use it rarely now

Try: “Italian - intermediate reading; conversational speaking, not used regularly in recent years.”

You may decide that the detail is unnecessary for the application. If you include the language because it is relevant, stale use is a reason to reassess your current level before claiming strength.

You have a formal exam result and a current gap

Try: “French - B2 CEFR exam result, 2022; currently strongest in reading and listening.”

The year helps prevent an old result from being mistaken for a current, comprehensive assessment. Add a current plain-language note if your day-to-day skill differs from the result.

You can handle greetings and fixed phrases only

Try: “Spanish - beginner; basic greetings and prepared phrases.”

If the language is not relevant to the job, consider leaving it off rather than using a tiny capability to imply more. If the employer specifically asks for all languages, describe it honestly.

You are a heritage speaker with a skill gap

Try: “Arabic - conversational listening and speaking; developing formal reading and writing.”

Family or community use can produce strong abilities in some settings and less practice in others. Do not assume that heritage status automatically means full professional proficiency. Describe the skill, not the label you think others expect.

You have strong vocabulary in one industry

Try: “Spanish - intermediate conversation; familiar with hospitality vocabulary.”

A limited vocabulary can be useful, but it is not the same as general fluency. If the role needs technical language, be clear about the scope and be ready to discuss how you handle an unfamiliar term.

When to include a language on your resume

Include a second language when it is relevant to the role, asked for in the posting, useful in the market or community the employer serves, or a meaningful part of your qualifications. Do not include it just because the resume template has room for a language section.

A language can be relevant even when it is not a stated requirement. It may help explain a qualification for work with international clients, multilingual communities, translated materials, or cross-border teams. But relevance is not proof of ability. Connect the language to the specific skill you have rather than making a vague claim about cultural competence or global expertise.

Leave it off when your ability is so limited that the entry distracts from stronger qualifications, the job has no clear use for it, and the application does not ask. Do not list a language merely to fill space or make a skills section look longer. Berkeley’s resume advice emphasizes selecting skills and experiences that relate to the employer’s needs; a language line should meet the same test. Berkeley’s resume guidance recommends tailoring content to the position and identifying relevant skill areas.

If an application asks which languages you speak, answer the form directly and truthfully even if you omit the language from your resume. An application field and a resume serve different purposes. Follow the employer’s wording and instructions; do not assume an optional resume line answers a required form question.

If a role requires a language, put the relevant ability where a reader can find it quickly. A short Languages section is usually clear. If the language is central to your professional work, you may also show it in a relevant accomplishment, but do not repeat the same claim in multiple places merely to make it look stronger.

How to place and format the language entry

For most resumes, a compact Languages section near Skills or Education is enough. Put the languages in a consistent order, and use a consistent format for each one. If the role specifically requires a language, place the section where it is easy to see rather than burying it at the bottom.

A simple structure works:

Languages

• Spanish - conversational speaking and listening
• French - intermediate reading and writing

Or, if you have a credible formal result:

Languages

• German - B2 CEFR exam result, earned 2024; professional reading, conversational speaking

Do not use flags, star ratings, progress bars, or a row of dots to represent language levels. A graphic suggests precision but rarely explains what the rating measures. A reader cannot tell whether four stars mean good conversation, strong reading, or simply confidence. Words are clearer.

Keep the heading and entries readable in the document. If the resume is crowded, remove a low-value item rather than shrinking the language line until it is hard to scan. Follow the employer’s file instructions. For a practical guide to selecting and checking a resume layout, see resumetemplate.co’s template gallery and free resume editor. The editor stores resumes in the browser on the device, and PDF export uses the browser’s print dialog; check the resulting document before submitting it.

Language is a text claim, so do not hide the only description inside an image or decorative chart. A plain, readable line is enough. Your job is to make the claim easy to find and easy to understand.

Prepare to discuss the claim in an interview

A resume language entry can prompt a follow-up. Prepare to describe what you can do, what you cannot yet do, and how the ability relates to the role. Do not prepare a speech that upgrades your claim under pressure.

A practical preparation routine:

1. Read the job description again. Identify the actual language tasks: calls, messages, documentation, presentations, or conversation with colleagues.
2. Choose one real capability. Be ready to explain a task you can perform, not just how long you studied or where you traveled.
3. Name a real boundary. If writing is weaker than speaking, say so. If you need extra time with unfamiliar topics, explain that plainly.
4. Practice a short sample. If you claim spoken ability, practice answering a normal question without a script. If you claim writing ability, write a brief, relevant message and review it honestly.
5. Prepare to ask for clarification. Useful communication includes recognizing when you missed something. Repeating or rephrasing is better than pretending to understand.
6. Do not claim a credential you do not have. If you report an exam result, know its name, date, score or level, and which skills it assessed.

These steps prepare you for a discussion; they do not predict the employer’s interview format. Some employers may assess a language directly, while others may ask about prior use or rely on the resume and conversation. Do not assume a particular test, and do not make unsupported claims about what employers universally do.

A useful answer can be simple: “I can handle routine scheduling conversations in Spanish and understand familiar questions. I would want support for a billing dispute or formal written response.” That answer gives the interviewer a working picture. It is better than “I’m fluent” followed by a retreat when the conversation turns to a task you cannot do.

If the employer switches languages unexpectedly, stay calm and answer within your ability. Ask for repetition if needed. If you do not understand the question, say so. A clear limit is more credible than guessing at what you heard.

Avoid these common overstatements

The most common mistake is using a high-status label to cover a low-detail claim. Avoid these shortcuts:

• “Fluent” because you can manage a basic exchange. A greeting and a short memorized conversation do not support a broad claim.
• “Native” because you grew up around the language. Background is not a substitute for current reading, writing, speaking, and listening ability.
• “Bilingual” when ability is uneven or limited. The word often suggests strong communication in two languages. If that is not what you can defend, state the specific skill instead.
• “Professional” because you know job-related vocabulary. Vocabulary is useful, but professional communication includes understanding questions and responding appropriately in context.
• A certificate as proof of every skill. A course certificate may show participation or completion; it does not automatically establish a particular level unless the assessment supports that claim.
• A test level without the test or date. A bare level may be hard to interpret. Name the framework or assessment and give the date when relevant.
• A stale level presented as current. Skills change with use. If the result or practice is old, reassess before stating a strong current claim.
• An overall label based on your strongest skill. Excellent reading does not prove fluent speaking; strong listening does not prove professional writing.
• A language listed as a credential for interpreting. Speaking another language does not by itself establish interpreting qualifications.

Harvard’s resume guidance asks candidates to keep language fact-based and specific. That principle matters especially with proficiency claims because adjectives can imply more than you intend. Harvard’s guide recommends qualifying claims rather than relying on general language.

Decide whether to use a framework, a plain label, or both

Choose the format that lets the employer understand your current ability with the least ambiguity. A framework is not automatically superior. It is useful when the reader recognizes it or when the job asks for it. Plain language is often better when the reader needs to know what you can do in practice.

The strongest entry may combine a formal result and a short qualification. For example, a hypothetical candidate could write: “French - B2 CEFR exam result, 2024; strongest in reading and listening.” If the role requires spoken customer support, that line should not imply the candidate meets that need unless the speaking ability supports it.

Do not list a framework level merely because it looks authoritative. The Council of Europe describes the CEFR as a reference framework with can-do descriptors across levels and activities, not a magic label that removes the need to understand what was assessed. The CEFR overview is the place to start if you use its levels. Follow the assessment provider’s official reporting rules for a test result.

Keep the claim relevant to the job

A language line should earn its space. Start with the job, then decide which part of your ability matters. A role that involves reading foreign-language reports has a different requirement from one that involves live customer calls. A role that serves multilingual clients may care about listening and spoken interaction. A research role may care more about reading and writing.

Read the job description for verbs. “Read,” “draft,” “present,” “negotiate,” “interpret,” “support,” and “communicate” point to different tasks. Do not assume that the broad phrase “language skills” means every skill is equally important.

Then match your evidence to the task:

• If the job asks for written correspondence, describe writing ability and any relevant subject context.
• If it asks for customer conversations, describe spoken interaction and listening, not just reading.
• If it asks for reading documents, say what kinds of documents you can handle, if you can do so accurately.
• If it asks for presentations, distinguish prepared presentation ability from spontaneous conversation.
• If it asks for translation or interpretation, do not imply qualification unless you have the relevant skill and credentials.

If the language is only a bonus, keep the entry brief. If it is central, give the reader enough detail to evaluate the fit. UC Berkeley’s guidance to tailor a resume to a position supports this approach: identify the employer’s required and preferred qualifications, then connect relevant skills to those needs. Berkeley’s resume guidance explains that a resume should make that connection.

Do not invent a business use because the employer serves a multilingual market. If you have not used the language at work, do not suggest that you have. You can say what you can do now and let the employer decide whether that capability is useful.

When the application asks for a proficiency level

Answer the exact question asked. If a form offers fixed choices, select the closest truthful option rather than trying to game the categories. If none fits, use a comment field if available to explain the difference between skills. If the form asks separately about speaking, reading, and writing, answer each separately.

Do not choose the highest available level because the job posting lists it. A requirement is not permission to inflate your answer. If you are below the stated level, say so or decide not to apply; do not make the resume and form contradict each other.

If the form asks whether you are bilingual, answer based on the meaning the employer gives the term, if it defines one. If it does not define it, do not assume that a modest conversational ability counts. You can clarify in a free-text field: “Conversational speaking and listening; intermediate reading.” That is more useful than a bare yes when the answer could be interpreted broadly.

Keep the resume, application, and interview consistent. If your resume says “professional working proficiency” and your application says “basic,” the mismatch will invite questions. Sometimes the difference reflects a form with crude categories. If so, explain that calmly and specifically. The goal is not to force identical phrasing; it is to tell the same truthful story.

If you are not sure what your level is

Do not guess upward. Use a practical self-assessment and, if the language matters to the job, consider a qualified assessment or a conversation with a knowledgeable instructor. The point is to check what you can do, not to buy a label.

The CEFR self-assessment grid can help you think in separate activities rather than one vague overall rating. It covers listening, reading, spoken interaction, spoken production, and writing. The Council of Europe’s grid provides descriptors you can compare against. ACTFL’s Can-Do Statements also organize communication across interpretive, interpersonal, and presentational modes. ACTFL notes that learners can differ by mode or skill, which reinforces the need to avoid flattening a mixed ability profile into one unsupported label. ACTFL’s Can-Do Statements can be used for self-evaluation and goal-setting; they are not a one-time test that certifies every situation.

Try the following check:

1. Pick a realistic task from the target job.
2. Attempt it without a translation tool or prepared script, unless the job itself permits those supports.
3. Record what you completed independently and where you needed help.
4. Repeat with a different skill: reading, writing, listening, and speaking.
5. Choose language that describes the strongest relevant ability without hiding a weaker essential one.

This is a personal check, not a validated assessment. A job seeker should not convert a few successful practice tasks into an official level. If a specific score or certification matters, follow the named assessment’s requirements.

If you lack confidence, do not automatically downgrade yourself. Nervousness can make a conversation harder, but it does not establish your level. Focus on repeatable tasks and evidence. If you can reliably explain a process, answer questions, and recover when you misunderstand, that is more informative than whether you feel perfectly fluent.

A quick editing pass for your resume language line

Before sending the resume, read the entry as if you were the hiring manager. Ask what you would reasonably expect after seeing each word. If the expectation is stronger than your ability, revise it.

Use this short editing sequence:

1. Name the language plainly. Avoid unexplained flags, abbreviations, or decorative symbols.
2. Replace the broadest adjective you can’t defend. If “fluent” makes you uneasy, choose a narrower description.
3. Separate skills where necessary. State reading, writing, speaking, or listening separately if the distinction affects the role.
4. Name a useful context. “Routine customer calls” is more concrete than “good communication” if that is what you can do.
5. Check dates and evidence. Confirm the exam name, result, and date if you include them.
6. Compare the resume with the application. Resolve any conflicting level claims before you submit.
7. Practice one follow-up answer. Be ready to explain what you can do and where you still need support.

A language claim does not need to sound impressive. It needs to be accurate, relevant, and easy to understand. Harvard recommends fact-based resume language, and Berkeley advises tailoring skills to the role. Those principles are especially useful here because the right detail can clarify a claim without making it longer than necessary. Harvard’s guidance and Berkeley’s resume guidance provide the underlying resume-writing advice.

Frequently asked questions

Should I write “fluent” or “proficient” on my resume?

Use the word you can defend in a work conversation. “Fluent” suggests broad, ready communication; “proficient” is vague unless you explain the skill or task. If you can manage familiar conversation but not complex work discussions, use “conversational” or a narrower description.

Is “conversational” a real proficiency level?

It is a common plain-language description, not a universally standardized level. Clarify what it means when the context could be misunderstood, such as “conversational speaking and listening for familiar topics.” Do not use it for greetings and memorized exchanges alone.

Can I list a language if I can read it but not speak it well?

Yes, if the ability is relevant. Say “advanced reading; basic spoken conversation” rather than using an overall label that implies equal strength across skills. If the job depends on speaking, do not let strong reading obscure that limitation.

Should I include a language I studied in school but rarely use now?

Include it only if your current ability is useful and you can describe it accurately. Coursework is not the same as current proficiency. Reassess your present skills, and leave the language off if it adds little to the application.

Do I need to list every language I know?

No, unless the application specifically asks for them. Include languages that are relevant or that you can describe meaningfully. If asked for all languages, answer fully and calibrate each level honestly.

Should I put my language level in the Skills section?

A compact Languages section is usually clearer. If your resume has a dedicated Skills section and the language is a relevant qualification, it can fit there. Use a plain-text description rather than a graphic rating.

Can I use a CEFR level if I assessed myself?

The CEFR provides descriptors and self-assessment materials, but do not imply that a formal exam awarded a level if you selected it yourself. If you use a self-assessed level, label it as self-assessed and make sure you understand the relevant descriptors. Use the specific activity levels when your abilities differ by skill.

Should I include the date of a language test?

Include it when the result’s age could affect how the reader interprets your current ability. A test result shows performance at a particular time and under particular conditions. If your current ability differs, say so.

What if I understand more than I can say?

Separate receptive skills, such as listening and reading, from spoken interaction or writing. For example, a hypothetical candidate might write “intermediate listening and reading; basic spoken interaction.” Choose wording that reflects the job’s actual requirements.

What if I can speak but cannot write professionally?

Say so. A hypothetical entry could read “conversational speaking and listening; basic writing.” If professional writing is essential, do not imply that speaking ability covers it.

Can I claim to be bilingual if I grew up with two languages?

Use “bilingual” only if you can support the level of ability the employer is likely to infer. Growing up around two languages may shape your experience, but it does not establish equal current ability in every skill. A specific description is safer when your strengths differ.

What if the job requires a level I do not have?

Do not inflate your claim. Decide whether your actual skills meet the essential task, and apply only with a truthful description. If you are close but not at the requested level, a precise account can let the employer assess the gap; it cannot guarantee that the employer will accept it.

Make the claim you can stand behind

The best resume language line names the language and describes the ability you can demonstrate now. Use plain labels for ordinary cases, separate skills when they differ, and report a recognized framework or test result when it is relevant and accurately stated. “Fluent” is not a reward for effort or a synonym for “I can get by.”

Choose one job-relevant task. Check whether you can perform it independently. Then write the line so a reader will expect no more than you can deliver. If you want a clean layout for the rest of the document, use the resume template gallery or the free resume editor, then review the printed PDF and make sure the language claim is still clear.

Your resume should start an honest conversation, not create a test you hope nobody gives you.