Language · 2026-08-14 · 14 min read

CV in English or Spanish: which language to send

Should your résumé be in English or Spanish? By job ad, country, and ATS: when to send each version, common mistakes, and how to keep two PDFs without duplicating errors.

Choosing the language of your CV is not cosmetic. It affects ATS parsing, how recruiters scan you, and whether your profile feels culturally aligned with the process. Many candidates assume English always helps. In practice, the wrong language can look poorly tailored—or simply fail keyword matching inside the company filter.

This guide gives clear decision rules: language of the posting, country of the role, company headquarters versus hiring team, local versus international process, and whether interviews will be in another language. You will also see how to keep two versions without inventing inconsistencies, and how ClarCV fits when you work in both Spanish and English.

The most reliable rule: match the job ad language

Also check the channel: a local Spanish job board often filters with Spanish dictionaries; LinkedIn Easy Apply to a global vacancy often filters in English. If a recruiter emails in one language and the ad is in another, match the ad for the attachment and reply to the email in the message language. That consistency reduces friction and shows process awareness.

When an ad is bilingual (paragraphs in both languages), pick the language of the mandatory requirements block and the application form labels. If the form fields are in English, an English CV usually parses more cleanly into those fields. If the form is Spanish, keep Spanish. Do not submit a half-translated file hoping to cover both.

If the posting is in Spanish, send a Spanish CV unless they explicitly ask otherwise. If it is in English, prioritize English. ATS systems and recruiters usually work from the same language as the ad: role titles, tools, and jargon appear there. Translating just in case weakens matches and can drop your ranking in the filter.

Concrete example: an English Customer Success Manager ad asks for churn reduction, CSAT, and Salesforce. A Spanish-only CV saying reducción de baja de clientes may be understood by a bilingual human but score weaker in ATS. The reverse is also true for Spanish local roles filled with English-only skill blocks.

When to use Spanish (even if you speak English)

Spanish also helps when your strongest proof points are local: public-sector acronyms, regional retail chains, Spanish labor law context, or client names that matter in that market. Translating those into awkward English can erase recognition. Keep the Spanish CV, and add a clean English skills line only if the ad asks for language ability—not as a substitute for a full English document.

Use Spanish when the market and process are local: Spain, much of LATAM, and many European employers posting domestic roles in Spanish. Also when HR and the hiring manager operate in Spanish and English is only a nice-to-have line in the ad.

• The ad, portal, and process emails are in Spanish.
• The role is on-site or hybrid in ES/LATAM without a global team.
• They expect a European-style local CV (photo and local conventions where appropriate).
• Your edge is local regulation, clients, or sector jargon.
• English in the ad is generic (B2) while the rest of the text is Spanish.

Before: a Madrid business analyst candidate sends a fully English CV with US titles (Business Analyst II). After: the same experience in Spanish, locally recognizable titles, and English B2/C1 listed cleanly. Typical outcome: stronger ATS match and faster reading for local recruiters.

When to use English

If you work at a multinational in Spain but want an internal move to an English-speaking hub, prepare the EN version with achievements translated into global metrics (ARR, NPS, SLA) and keep the ES version for local processes. Do not paste dense US jargon into a European hub CV: adapt tone to the destination market without inventing experience.

For remote roles that say “timezone Europe” but publish in English, treat English as the working language of hiring. Recruiters compare candidates across countries in one shortlist; a Spanish-only CV creates extra translation work they will not do. Make titles and tools internationally readable, and move country-specific details into context clauses rather than obscure abbreviations.

Use English when the process is international by design: global startups, multinationals with English reporting, remote-first roles, or when the ad asks for an English CV or résumé. Also when the hiring manager does not speak Spanish or the team spans multiple countries.

• The posting is fully in English with global titles.
• They explicitly request an English CV or résumé.
• The role is in the UK, Ireland, Netherlands, English-speaking DACH teams, or international remote.
• The company operates in English even if the office is in Madrid or Barcelona.
• You apply via LinkedIn Easy Apply to an English-only vacancy.

Be careful with intermediate English: grammar errors on a CV hurt more than an excellent Spanish CV plus an honest language level line. A short, clear, correct English version beats a literal translation full of calques.

Mixed cases (the confusing ones)

Spanish ad from a US company in Spain: Spanish usually wins if the ad and portal are Spanish; add a bilingual summary only if asked. English ad from a Spanish company: prioritize English and align keywords to the posting. Recruiters asking for both: prepare two files with the same facts (dates, employers, outcomes) and different linguistic prioritization.

If they review LinkedIn or a portfolio, align the primary language with the CV you send that week. You do not need a perfect clone of every sentence—you do need consistent titles, dates, and key metrics so you do not look like two different people.

How to maintain two versions without chaos

Version control matters. Keep a dated master list of achievements in a spreadsheet or notes file, then generate ES and EN CVs from it. When you win a new metric, update the master first. That habit prevents the classic failure mode: English CV says “reduced churn 12%” while Spanish CV still shows last year’s number. Inconsistencies across languages look like exaggeration in interviews.

Keep one source of truth: achievements, metrics, tools, and dates. Generate ES and EN from that base. Do not translate word for word—localize. Job titles especially: use the destination-market equivalent, not a calque. Account Manager, intern, education, and training are not always one-to-one mappings.

• Localize titles to the target market.
• Keep tool names in English (Python, HubSpot, SAP).
• Format numbers for the CV language (1.200 versus 1,200).
• Check acronyms: RR. HH. versus HR.
• Name files clearly: Last_First_CV_ES.pdf and _EN.pdf.

Photo, personal data, and market language

CV language often travels with cultural format. Many Spanish processes (ES/LATAM/EU) still expect a photo; US/UK English processes usually do not. An English CV for London should omit photo and ID numbers. A Spanish CV for a Valencia SME may expect a European layout with photo. Language is a hint for the full cultural package.

Keywords and ATS: do not mix languages in critical sections

A common mistake is a Spanish summary, English skills, and mixed bullets. Parsers look for patterns. Mixing languages weakens matches and looks careless. Pick one primary language for summary, experience, and skills. You can still add a languages line (English C1, Spanish native) without making the whole document bilingual.

Before: mixed Spanish and English customer success wording. After (EN CV): Owned the customer journey and improved NPS for the Customer Success team. Same truth, keywords aligned to an English ad.

Quick checklist before you send

One last trick: paste your CV into a plain-text document. If sections disappear or order breaks, an ATS may struggle too. Fix structure before worrying about fonts. Then return to a clean ATS-friendly PDF and reread only the summary and the first three bullets: they must work in the chosen language without a dictionary.

• Does the ad language match my CV language?
• Do job titles sound natural in that market?
• Do critical keywords appear in the ad language?
• Does format (photo, personal data) fit the country?
• Has grammar been reviewed carefully?
• Is the filename clear and professional?

How ClarCV helps

With ClarCV you upload PDF or Word, get AI feedback on clarity and structure, and regenerate ATS-friendly versions. The product UI is available in Spanish and English; CV output can match the language of each application. Start free; Pro is €7/month if you iterate often.