8 min read
Myth: every international apply needs a translated CV. Reality: most cross-border corporate reqs on Greenhouse still screen an English PDF because the hiring manager, legal review, and interview loop are in English. You don't owe a second language file until the apply path asks for one.
The expensive mistake isn't skipping translation. It's shipping a machine-translated file that renames your title, scrambles dates, and breaks the same parser rules as a fancy two-column template at home. You'll feel productive; the portal won't import it cleanly.
Check your resume for free on whichever language version you'll upload tonight. You're confirming section order and posting verbs survived export, not debating grammar theory.
Below: decision criteria, what English-only wins, what localized files fix, layout traps, and a copy-paste header block for bilingual markets. Job searching across borders is exhausting; this is a file strategy, not a loyalty test to one language.
Four signals before you translate your resume for international jobs
Read the apply path, not the company HQ map. A US firm hiring in Dublin may still run English screens. A local insurer in Montreal may expect French materials even when the LinkedIn ad is bilingual.
| Signal | Lean English | Lean localized file |
|---|---|---|
| Posting and portal language | English fields only | Local language required or default |
| Interview language stated | English loop named | Local language fluency required |
| Your proof bullets | Already mirror English posting verbs | Posting verbs only exist in local language |
| Regulated or public-sector req | Rare for full English | Often mandates local CV format |
Parsers care about structure first. Month Year dates, employer rows, and plain section headers matter in every language. A translated file that adds photos, marital status, or multi-column EU CV layout can fail Workday import even when the words are perfect.
For US-style single-column rules that still apply on global portals, see SAP ATS parsing US resume formatting that works . Translation doesn't replace those layout constraints.
English-only vs localized resume paths
Path A: English master for English reqs
Use one reverse-chronological PDF when the posting, screening call, and offer paperwork are English. Tailor bullet one to the posting title family. Keep employer names as they appear on payroll. This is the default for multinationals hiring remote English speakers into US or UK entities.
Before: You translate every bullet to French for a London fintech req that never mentions French, and dates flip to DD/MM in one row and MM/DD in another.
After: You keep English, fix Month Year consistency, and mirror two must-have tools from the posting in bullet one under the employer that used them.
Path B: Localized file when the market screens in that language
Build a second file when HR or the portal explicitly requests local language. Translate outcomes and skills, not legal employer strings. Match posting verbs in bullet one. If you cannot defend the wording on a phone screen, do not upload that language yet.
Before: Machine output lists "Ingénieur logiciel senior" as your title while your contract still says Software Engineer II.
After: Employer row keeps Software Engineer II with honest dates; summary adds one line that maps the role to the local title standard used in the posting.
Copy-paste bilingual header skeleton:
[Local language summary: 2 sentences + target role family]
[English mirror: same facts, same metrics, no new employers]
Experience (reverse chronological, Month Year dates unchanged)
Company Legal Name | City
Title on contract | March 2021 to Present
• [Local verb] [posting noun] … [metric].
• English backup bullet optional only if portal allows two uploads.
I've screened international packs in Greenhouse where the English resume matched the req and the translated attachment repeated different job titles. Recruiters assume the candidate is hiding something before they reach bullet one.
When you're also tuning remote eligibility on the same file, read how to write a resume for remote jobs for location and authorization lines that belong in the English master.
Translation traps that fail ATS import
Swapping layout standards when you swap languages. US single-column PDFs still beat ornate EU templates on many corporate portals, even in Europe. Translate text inside a boring column instead of adopting every local CV custom on day one.
Renaming employers or degrees. Background checks and LinkedIn use one spelling. Translating Amazon.com to a phonetic local string confuses parsers and humans.
Before: Skills block lists twelve translated tools with zero proof in Experience.
After: Six skills max, each appears in a dated bullet under the job that used the tool.
Uploading both files without labels. Recruiters open the wrong language first and pass. Filename language codes matter.
This won't fix work authorization gaps or missing licenses. It stops a qualified bilingual candidate from getting screened out because the parser read garbage characters or mismatched titles between two versions.
Scan before the border apply
Run the file you'll actually upload through HireFlow's free ATS resume checker with the target posting pasted in. Confirm must-have terms appear inside Experience, not only in a translated skills footer.
If you're rebuilding the English master before you localize, build your resume in a single-column template so the second language export doesn't inherit broken tables.
When the letter must explain relocation or visa timing the resume fields can't hold, generate a cover letter in the same language as the primary upload.
Do this now: Read the posting language line, pick English or localized as primary, align titles and dates across versions, scan once, then apply with labeled filenames.
Pick one primary file tonight
Should you translate your resume for international jobs? Only when the screening language demands it. Otherwise polish the English master, keep dates honest, and stop fighting the parser with layout experiments in every locale.
- Match file language to posting, portal, and interview language.
- Keep employer names and titles verifiable across versions.
- Use single-column exports with Month Year dates.
- Label EN and local PDFs before upload.
Open the target posting, paste it into a free ATS check , fix bullet one, then submit one clean primary file.
Read more
Frequently asked questions
Usually keep one strong English file when the posting, portal, and interview loop are English. Translate when the posting is local language, when the form asks for a CV in that language, or when HR confirms screening happens in French, German, Japanese, or another working language. An English posting in Paris can still expect French materials from local applicants. Read the apply instructions, not only the ad language.
Maintain a master in the language you can defend in an interview, plus a localized version when the market requires it. Keep employer names, Month Year dates, and job titles consistent across both. Do not let the translated file invent titles your background check will contradict. Name files clearly: FirstName_LastName_EN.pdf and FirstName_LastName_FR.pdf.
Raw machine output often breaks section headers, accent characters, and bullet symbols parsers expect. If you translate, rebuild headings in plain text, keep a single column, and export PDF from a clean DOCX. Have a fluent reader fix verbs in bullet one. Parsers match tokens; garbled characters can split keywords into junk tokens.
Keep legal employer names and vendor certification strings as they appear on LinkedIn and payroll. Translate your role description and outcomes, not the trademark on the building. If the posting uses a local job title standard, mirror that title in the summary once while the employer row stays truthful.