The Cross-Border Resume Conversion, Field by Field by Country

You have a resume that works at home, a posting in another country, and a nagging sense that the two do not fit. They do not. This is a field-by-field lookup for converting one work history into another market's hiring conventions: which fields to change, what each one proves to a local recruiter, and where copying a convention across a border quietly sinks the application. It is for anyone applying for jobs abroad who wants to submit something a local screener reads as native, not imported.

The core fact that makes this hard: the same field is an asset in one market and a legal risk three thousand miles away. A photo and a birth date are customary in Germany and expected in Dubai. In the US they are a compliance risk for the recruiter, who protects themselves by dropping your file. You are not converting a document once; you are re-deciding six or seven fields against a specific destination.

Which fields actually differ across borders

Six fields carry almost all of the cross-border variation: the document's name, its length, whether it carries a photo, what personal data it lists, the language and spelling variant, and its structure. Everything else on your resume - your history, your accomplishments, your keywords - travels unchanged.

Treat these six as the conversion surface. If you change nothing else, change these:

• Document name. Resume or CV, and whether that word means a two-page summary or a multi-page academic document.
• Length. One page, two pages, two to three pages, or a fixed government form.
• Photo. Expected, discouraged, or an active screening liability.
• Personal data. Date of birth, nationality, and marital status: demanded in some markets, discarded on sight in others.
• Language and spelling. Local language versus English, and American versus British versus Australian spelling.
• Structure. Cover letter, personal summary, selection-criteria document, signature, or a split into two forms.

The rest of this guide takes each field, states the norm per country, says what it proves to a local recruiter, and says where copying it backfires.

Photo, personal data, and length by market

Here is the field-by-field table. Read across your target market's row and change only what differs from your current document.

A few rows need the fine print that a table cannot hold. The US one-page bias is stronger than in the UK, Europe, or the Gulf, with one exception: federal government resumes run three to five pages. In the UK, omit date of birth, age, and salary history, and keep to two pages of A4. Australia runs longer than all of these at two to three pages, with no photo, no date of birth, and no marital status. The Gulf expects the opposite: nationality is mandatory, date of birth is highly requested, marital status is expected, and a professional photo is almost always present on a Dubai CV.

Japan is a category of its own. The rirekisho requires a professional passport-sized photo, three centimetres by four, glued to the upper-right corner and taken within three months. That photo is not optional decoration; it is a required field on a standardised form.

What each field proves, and how it lies. A photo on a German or Gulf CV proves you know the local form; its absence reads as an incomplete document. The same photo on a US resume proves nothing good - it reads as naive at best and forces a compliance-conscious recruiter to discard the file. A date of birth on a Gulf CV proves you have handled the visa and allowance logistics; on a UK resume it proves you did not localise, and it hands the screener a protected characteristic they did not want to see. Length lies the most quietly: a crisp one-pager that feels professional in New York reads as thin in London, Sydney, or Dubai, because those markets equate two to three pages with seniority.

Resume versus CV, and where the word flips

The word "CV" means different documents in different places, and getting it wrong signals an imported application before a recruiter reads a line. In the US and Canada, a resume is the brief one-to-two-page document for most jobs and a CV is a long academic document for research, faculty, and medical roles. In the UK and Europe, "CV" is simply the standard term for every application, one to two pages. Australia treats "resume" and "CV" as almost interchangeable.

The trap inside North America is that the flip is field-based, not just country-based. If you are a researcher or physician applying in the US, the word "CV" is correct and expected, and it means the long publications-and-grants document, not the two-page summary. If you carry that habit into a non-academic US application, you will over-deliver a document nobody asked for.

Language, spelling, and the translation trap

Match the posting's language, and only translate into the local language if you are genuinely fluent. A German-language posting expects a German CV; an English-language posting accepts English. This is the one field where doing more work makes the document worse: a bad translation is worse than clean English, and German guides in particular treat an obvious machine translation as a red flag.

Spelling is the cheaper half of this field and the one people skip. A single "organize" in a UK or Australian CV signals an imported document as loudly as a wrong page size. Use British spelling for the UK - organise, specialise, programme. Australia uses Australian and British spelling. Words like "color," "organize," and "behavior" jump off the page as non-local to an Australian reader. Run a British or Australian spellcheck pass and read the output; a spellchecker set to the wrong locale is why these slip through.

A bad translation is worse than clean English, and a single American spelling reads as loudly as the wrong page size.

If the posting is in a language you do not command, submit in English rather than in a translation you cannot vouch for, or have a native speaker proof the local-language version before it goes out. Fluency here means you could defend the wording in an interview, not that a tool produced grammatical sentences.

Structure: the sections that appear and disappear

Beyond the six core fields, markets differ in which whole sections a complete application contains. This is where you add or remove documents, not just edit fields. Germany expects a formal cover letter, the Anschreiben, and a signature with place and date on the CV itself. France expects a lettre de motivation. Australia frequently adds a key selection criteria document that summarises your skills against the posting's stated criteria, submitted alongside the CV and cover letter.

Ordering is more stable than it looks. Reverse-chronological dominates in the US, UK, Australia, and the Japanese education section; a functional or skills-based order is a fallback only when your experience is thin. A personal summary is standard and expected under different names: "Professional Summary" in the US, "personal statement" in the UK, and a summary block in the Gulf. Japan splits the whole thing into two forms - the rirekisho, a standardised snapshot, plus the shokumu-keirekisho, a career-history sheet.

The step-by-step conversion

Work the fields in this order. Front-loading the name and length decisions means every later edit happens inside a document of the right shape, and the channel check at the end catches the photo-versus-portal conflict that sinks otherwise-correct conversions.

Tailoring the keywords and structure in the ATS pass by hand for every posting is where the hours go. Refolk writes your resume from your own history and then tailors it to each posting you apply to, drafting the cover letter and scoring how well you actually fit, so the per-application rebuild stops eating your evenings.

How this goes wrong: failure modes and false positives

Most cross-border resumes fail in one of eight predictable ways. Each has a false positive - a version that looks correct on screen while it is quietly broken - and a local check that catches it.

Copying a German or French photo into an ATS upload. Photos usually sit in a header, sidebar, or text box, and those are exactly the structures a parser reads badly. The false positive is a CV that looks complete on screen while the parser buried your name. Check: paste the PDF into a plain-text reader and confirm your name and contact details appear first.

Leaving date of birth or marital status on an Anglophone resume. It reads as naive and hands the recruiter a screening liability, so they discard it. Check: search the document for any birth year, age, gender, or marital field before an Anglophone submission.

Sending a one-page US resume to the UK, Australia, or the Gulf. It feels tight and professional to you and reads as thin to them. Check: match page count to the market table above.

Trusting the "75% auto-rejected by ATS" claim. It is contested. Roughly 98% of Fortune 500 use an ATS, but around 92% do not auto-reject, and the "75%" figure traces to a defunct 2013 startup. Check: treat the ATS as ranking and search, keyword-match to the posting, and skip the design tricks sold on the back of that scare.

Machine-translating into the local language. A bad translation is worse than English. Check: translate only if fluent, or have a native speaker proof it.

Omitting nationality or visa status on a Gulf CV. Recruiters filter on availability first, so the CV stalls. Nationality is tied to salary bands and visa quotas, and marital status affects housing and flight allowances. Check: confirm nationality, visa status, and notice period sit near the top.

Keeping US spelling in a UK or Australia CV. A single "organize" signals an imported document. Check: run a British or Australian spellcheck pass and read the flagged words.

Using US Letter where A4 is standard. Margins shift or content clips on local printers and parsers. Check: set page size to A4 for every market except the US and Canada.

Why the ATS pass matters even in photo markets

Applicant tracking systems have gone global, which collapses the old "North America versus everywhere else" framing. In 2025, Jobscan detected an ATS at 489 of the 500 Fortune 500 companies, 97.8%, and that figure has held between 97.4% and 98.8% every year since 2018. The same platforms - Workday, SAP SuccessFactors, Taleo, PageUp - run in German, Australian, and Gulf enterprises. In German enterprise, Workday leads ATS use at roughly 37% share, followed by SAP SuccessFactors at about 13%. UAE government portals such as Dubai Careers and TAMM reject CVs with embedded images outright.

The consequence is direct: the single-column, text-based, image-free rule now applies even in markets that expect a photo. That is the whole argument for keeping two versions of the same file. The photo goes in the email version; the portal version strips it.

There is also a human layer, and it is lopsided across markets. In Refolk's index of professional profiles, the recruiter and talent-acquisition population is far denser in some markets than others.

The UK has 4.6 times the recruiter density of the UAE in Refolk's index. A thicker recruiter layer means more specialist, convention-strict screening, so a UK CV that gets a spelling variant or a page count wrong is more likely to meet someone who notices. The smaller, freelance-heavy Gulf pool leans harder on fast keyword filters, which raises the payoff of a clean ATS pass rather than lowering it. Neither market lets you skip the work; they just punish different mistakes.

If you want to see who those screeners are before you convert, you can look them up directly.

Before you submit: the localisation checklist

Run this against the converted file before it leaves your outbox. It is ordered to catch the expensive mistakes - protected-class data and the photo-portal conflict - before the cosmetic ones.

Sending my [document-name] of [page-count] pages to [country] via [channel]; photo decision, personal-data fields, spelling variant, page size, and structure all match that market and channel, and the plain-text paste shows my name first.

Keeping the conversion current

Two things in this guide move over time, and you should re-check them rather than trust a snapshot. The first is the ATS adoption figure: it is republished annually, so if you want the current number, look for the latest Fortune 500 ATS audit rather than repeating a figure from memory. The second is any single country's convention, especially Germany's, where law and custom pull against each other - the AGG has banned required photos and birth dates since 2006, yet both remain customary. When a market is genuinely unsettled, confirm against a current sector template or, better, against a real recruiter in that market before you commit.

The durable part is the method. The fields that differ across borders do not change; only their per-country values do. Keep one clean master history, decide the six fields against the destination, keep a photo and a photo-free variant, and route each by channel. Do that and every future application abroad is a lookup, not a rebuild.