12 min read
You've got a strong US file. You're targeting London, Amsterdam, or Sydney. You run the body through a translation tool, swap a few verbs, and upload. The portal accepts it. Then nothing. You're not failing on language skill. You're failing because the parser still reads a US date stack, a one-page squeeze, and a title grade the local req doesn't recognize.
Check your resume for free on the exact PDF or DOCX you'll attach abroad. International files fail when you translate words but keep US date formats, page length, and title conventions. The steps below fix structure and labels first, then wording.
Below you'll pick the target market format, translate section labels not just body text, convert dates and metrics, keep a parse-clean layout, and localize title seniority without inflating. Two edge cases cover bilingual reqs and remote-only employers. Job searching across borders is stressful enough without sending a file that looks translated and reads foreign to the ATS row order.
And if you're wondering whether you need a full rewrite or a localization pass, start with export plain text. When employers and dates scramble, it's layout. When they parse clean but screens stay quiet, it's usually title level or metric labels.
Quick Wins
- Match page length and section order to the posting country sample.
- Translate Experience and Education headers, not only bullet verbs.
- Spell dates Month Year in the portal's expected order.
- Export plain text after save; fix scrambled employers before wording.
Why translate your resume for international jobs beyond language
Translation tools handle sentences. They don't handle hiring conventions. A US one-pager crammed into German section titles still breaks when the portal expects Berufserfahrung above Ausbildung with day-month-year dates and a two-page CV norm. Greenhouse and Workday in Europe use the same parsers as US instances. They read row order, not your fluency.
Localization beats literal translation: keep proof bullets, swap format, labels, date order, title seniority words, and personal-detail blocks to match what recruiters in that market scan first. The file should look like it was built for the req, not exported from a different country's template.
Read UK CV vs US resume for international applications when you're split between markets. This page is the step order for any cross-border upload once you've picked the country.
I've screened international uploads in Workday where translated prose imported cleanly but US date order still broke the Experience row. Recruiters abroad still skim title, employer, dates, bullet one. Localize level words honestly with a subtitle that explains internal grades when your headline lags the posting.
Edge case: multinational req posted in English for an EU hub. English body text is fine when labels and dates follow the sample CV on the careers site. Remote role with no location: default to the employer's headquarters country format.
Five steps to translate your resume for international jobs
Step 1: Pick the target market format before you translate a word
Open the employer's careers page and download their CV sample if one exists. Note page count, photo block, personal details, and whether Education sits above Experience. US and Canadian corporate roles: one page for most mid-level applicants, two only when senior proof is dense. UK: two pages is standard for experienced hires. Many EU markets: two pages with fuller education history.
Before: US one-page PDF with Summary, Skills, Experience, Education. Uploaded to a UK corporate req that shows a two-page sample with Personal Profile and no photo.
After: Two-page UK CV: Personal Profile (three lines), Core Skills (one column), Career History with Month Year dates, Education with degree class line. No Summary label. Same bullets, reordered sections.
Match the sample on the employer site first. Don't shrink a UK CV to one page because your US coach said so.
Step 2: Translate section labels and headers, not just body text
Parsers and human screeners both look for section strings. Experience left in English inside a German portal sometimes works. Experience buried under a custom header the parser doesn't map often doesn't. Translate standard headers: Work Experience, Education, Skills, Certifications, Languages. Keep employer names, university names, and tool strings (Salesforce, SAP, Epic) in their official spelling.
Before: Custom sidebar labels: My Journey, Toolkit, Wins. Body translated to French. Portal language French.
After: Standard headers: Expérience professionnelle, Formation, Compétences. Sidebar removed. Single column. Tool names unchanged: Salesforce, Power BI.
Before: Bilingual file with mixed headers: Experience, Formation académique, Skills.
After: All headers in the portal language OR all in English when the req is English-only. Mixed headers confuse both parsers and humans scanning for Formation vs Education.
Job titles need a human pass. Literal translation of internal grades sounds odd: Specialist Engineer becomes ingénieur spécialiste when the market expects Ingénieur d'études or Lead Developer. Use the posting's title words with a parenthetical for your formal title when they differ.
Step 3: Convert dates and metrics to local convention
US Month Year (Jan 2022 to Mar 2025) vs EU day-month-year on some forms (15 Jan 2022 to 03 Mar 2025). Pick one style per file and use it on every role line. Spell months in the portal language when the careers site does: janv. 2022 or Jan 2022, not 01/22 which parsers read as ambiguous.
Before: 01/2019 to 12/2023 on a UK upload. Plain-text export shows dates detached from employer rows.
After: Jan 2019 to Dec 2023 on the same line as employer name, en dash or to between months, present spelled Present not current.
Before: Managed $4M budget with no currency label on a UK req.
After: Managed USD 4M annual vendor budget (approx. £3.1M at 2024 rates) OR managed £3.1M annual vendor budget when you operated in sterling. Label currency. Don't silently swap symbols.
Step 4: Keep a parse-clean layout after translation
Translation often breaks layout: text boxes expand, tables shift, icons stay while words change. Save as PDF and DOCX when the portal allows both. Export plain text. If Experience dates appear under the wrong company, fix structure before you tweak verbs.
Before: Two-column Canva CV translated to Spanish. Icons for phone and email. Skills in a colored sidebar.
After: Single-column DOCX. Contact line on row one: name, city, country, phone with country code, email. No icons. Skills as a simple list below Experience.
Read US vs UK CV format differences for header and length rules that survive export. Parse-clean is the bar. Fluent prose in a scrambled file still dies in the portal.
Step 5: Localize title seniority without inflating
Grade names differ by country. Assistant Manager in one market maps to Team Lead in another. Senior Analyst in the US may read as mid-level in the UK when the posting expects Manager with direct reports. Mirror the posting's seniority word when your scope supports it. Add a clarifying subtitle when your formal title lags.
Before: Headline: Business Analyst II. Posting Dublin: Senior Business Analyst, client-facing, mentors juniors.
After: Headline: Senior Business Analyst (internal grade Analyst II). Bullet one: Led requirements workshops for 3 banking clients; mentored 2 junior analysts on Jira backlog hygiene, 2024 to present.
Don't claim Manager on the headline when you had no reports. Show acting scope in bullet one when you ran the work at the level on the sheet.
Edge case: bilingual posting or dual-language team
When the req lists two languages, add a Languages line with CEFR levels (C1 English, B2 Dutch) instead of fluent in both in the summary. Put the file in the language the application form defaults to. Attach a one-page translation appendix only when the employer explicitly asks. Two full resumes in one PDF often break upload limits and parse order.
Edge case: work authorization and location lines
Many EU forms ask authorization separately. One header line: Location: Berlin, Germany | Work authorization: EU citizen. False claims fail later. Omission on a form field beats a long essay on the resume.
Copy-paste localization checklist block
Copy-paste before upload:
[ ] Page count matches employer sample (1 US / 2 UK / 2 EU typical)
[ ] Section headers in portal language; tools and employers unchanged
[ ] Dates: Month Year consistent; no MM/YY slashes
[ ] Currency labeled on every budget or revenue bullet
[ ] Headline uses posting seniority word + honest subtitle if needed
[ ] Plain-text export: each employer + date range on one row
[ ] Photo and personal fields only if sample CV includes them
What breaks when US resumes land abroad
Translating bullets but keeping US section order on a UK req. Education placement and profile block labels matter as much as verbs. Reorder before you rewrite wording.
Stuffing every keyword in English and local language. Duplicate Skills lines in two languages look like keyword stuffing and double parse noise. Pick one language per field.
Leaving phone numbers without country codes. +1 numbers on a Berlin posting signal you didn't localize contact rows. Add country code and city line.
Uploading a scanned photo CV as PDF image. Parsers can't read image PDFs. Text must be selectable. If you need a photo, use a text-based template with an image block, not a flat scan.
Converting grades with online calculators you can't explain. One honest line beats a fake 2:1 equivalent. Name your US GPA and institution; let the recruiter map it.
Ignoring address and data-privacy norms. Full street address and birth date on a UK corporate upload add no proof. City and country are enough unless the form demands more.
Verify parse before the international upload
Run the localized file through the free ATS checker with the foreign posting pasted in. Translation can drop keywords that still matter in English reqs abroad. Confirm must-have terms appear in Experience, not only in a translated Skills cloud.
When the portal asks for a cover letter in the posting language, use the cover letter generator after the resume parses clean. Match section language to the letter so both files read as one package.
Then build your resume in a single-column template if plain-text export still scrambles rows. Re-enter bullets once in a parse-safe skeleton, then apply the localization checklist.
Ship the localized file, not the translated US template
When you translate your resume for international jobs, start with market format and parser layout, then language. Pick the sample the employer shows. Label sections in the portal language. Fix dates and currency. Match seniority words honestly. Run plain text before you celebrate fluent bullets.
Pick your next foreign req. Compare your file to their CV sample for sixty seconds. If page count, headers, or date style don't match, fix those before you pay for proofreading.
Borders change labels. They don't change the rule that bullet one still has to prove scope. Localize the skeleton first so a human actually reads that line.
Read more
Frequently asked questions
Match the posting language. If the req is in English for a Dublin or Singapore role, an English file is fine when labels and dates follow local convention. If the portal asks for Dutch or German, translate section headers and body text; keep employer names and tool strings in their original form when parsers search for them. Never submit a machine translation without a human pass on job titles and degree names.
Follow the market on the posting, not habit from your home country. UK and US corporate applications usually skip photos, marital status, and full street addresses. Some EU employers still expect a photo on a CV file even when the portal is in English. When the employer's sample CV includes a photo block, add one professional headshot in a single-column layout. When the sample is US-style, strip photo and birth date fields before upload.
One to two pages for US, Canada, Australia, and most UK corporate roles unless you're senior and the proof is dense. Two pages is normal for many EU markets when education and early roles stay on the file. Don't pad to match a longer local norm with duplicated bullets. Translate the same proof lines; add pages only when you have dated roles that still support the posting.
They parse structure first. Translated text in a two-column template or a table-based CV often imports employers and dates out of order even when the language is perfect. Export plain text after every save. If Experience dates land below the wrong employer, fix layout before you worry about word choice. Single-column PDF or DOCX with standard section labels parses more reliably across borders.
Convert only when the reader needs context to judge level. GPA on a 4.0 scale belongs beside a US degree; UK employers may want degree class or A-level equivalents spelled once in Education. Revenue and team-size metrics can stay in the currency you operated in if you label it: managed £2.1M pipeline or managed $2.1M pipeline. Don't invent conversions you can't defend. Name the currency and period instead of silent swaps.