8 min read
Your London CV isn't failing because you're underqualified. It's failing because the parser read your US layout out of order: sidebar skills first, employment dates in a table cell, contact line in a header the software skipped. Same platform, different country, different expected shape. If you've only ever optimized for US uploads, you're not doing anything wrong. You just haven't built the second export yet.
Before you duplicate effort, check your resume for free on the export you plan to attach. Paste the text into Notepad. If sections scramble, fix layout before you debate UK spelling.
Below: the parser criteria that differ by region, US rules on one side and UK/EU rules on the other, a decision rule for tonight, and a copy-paste header block you can split into two files. Pair this with PDF vs Word for ATS when the posting names a file type. If the UK req asks for a short note, draft it in the cover letter generator after you lock the CV export.
Parser criteria that change by country
Applicant tracking systems in the US, UK, and EU often share the same vendor names. Workday, Greenhouse, and Taleo show up on every continent. What changes is the file shape recruiters in that market upload most often, and which fields local HR marks as required in the candidate profile.
Parsers read top to bottom in a single column. US resumes trained on one-page templates usually pass that test. UK and EU CVs sometimes open with a personal profile, photo, or nationality line in a header row. The software may attach those lines to the wrong field or drop dates that sit beside a photo column.
Date format is a silent filter. US uploads often tolerate January 2024 or 01/2024. UK and EU reviewers expect spelled-out months because numeric dates read as day-first or month-first depending on who's screening. Ambiguous strings like 04/07/2023 break tenure math in the parser.
Personal detail blocks flip by market. US corporate applications should omit photos, birth dates, and marital status. UK and EU CVs still carry some of those fields in traditional industries. Send a photo-heavy EU CV to a US tech req and the human screener may stop before the parser finishes. Send a bare US file to a German corporate role and the human reader may treat it as incomplete even when parsing succeeds.
I've screened international stacks where the US version ranked fine in Greenhouse but the same person's UK export landed with employment dates detached from job titles because the CV used a two-column Europass-style layout. Same candidate, two files, two parse outcomes.
Read resume formatting errors that break ATS parsing when your file looks fine on screen but jumbles in plain text.
Why your resume needs different formatting: US vs UK/EU for parsers
| Parser field | US resume default | UK / EU CV default |
|---|---|---|
| Length | One page for most roles; two only with dense relevant proof | Two pages common; education and early roles stay visible |
| Photo and personal lines | Omit photo, birth date, nationality, marital status | Photo optional by sector; nationality line still appears in some CVs |
| Date format | Month Year or MM/YYYY in experience lines | January 2022 to March 2024 spelled out |
| Section order | Contact, summary, experience, education, skills | Contact, personal profile, experience, education, skills, languages |
| Spelling and titles | US English; "resume" in conversation, "Resume" as heading | UK English; "CV" heading; "organise" not "organize" when applying in the UK |
| Typical file type | PDF single column when posting is silent | DOCX or PDF; follow posting when a public-sector portal specifies Word |
US formatting for parsers
Before: Two-column Canva layout, skills in a sidebar table, "Curriculum Vitae" heading, graduation year only.
After: One column, "Experience" heading, each role with Month Year dates inline, skills as a short list below education, no photo block.
US parsers map employer, title, start date, and end date into separate fields. Keep each role on consecutive lines: Company, Title, January 2022 to Present, then bullets. Do not nest jobs inside tables.
UK and EU formatting for parsers
Before: US one-pager exported with American spellings, no personal profile, jobs compressed to one line each.
After: Two-page CV, three-line personal profile, full employment history with spelled-out dates, languages line when the posting mentions multilingual work, UK spellings for UK reqs.
UK and EU parsers still want the same structured employment fields. The difference is you have room to keep earlier roles and education visible without shrinking font to 9 pt. Use that space for dated proof, not hobbies.
Copy-paste header blocks (split into two files)
US export (no photo)
Name | email | phone | city, ST | portfolio URL
Professional Summary
Two lines with target role and one metric from recent work.
Experience
Company Name | Job Title
January 2022 – Present
- Bullet with tool from posting and outcome
Education
University | Degree | May 2020
Skills
Tool 1, Tool 2, Tool 3 (ordered to match posting)
UK/EU export (add profile; photo only if local norm requires)
Name | email | phone | city, UK | LinkedIn URL
Personal Profile
Three sentences: role focus, sector, one proof line with Month Year context.
Experience
Company Name | Job Title
January 2019 – March 2024
- Bullet with spelled-out month dates in text
Education
University | Degree | September 2015 – June 2019
Languages
English (native), German (professional working)
Decision rule: if the job sits in the US, export the one-page file without personal detail blocks. If the job sits in the UK or EU, expand to two pages, spell every date, match local spelling, and add a profile line even when you're also qualified on substance alone.
Cross-border traps
One PDF for every country. You'll optimize for none. Keep one master document, then save US-Resume.pdf and UK-CV.docx with the shapes above.
Shipping US personal-detail omissions to a market that expects a profile block. Parsing may succeed while the human reader marks the file incomplete.
Numeric dates everywhere. 05/06/2022 means different things to different reviewers and parsers. Spell the month in international files.
Europass layout for a US tech req. Two columns and icon rows scramble Greenhouse parsing the same way a fancy US template does.
Before: Single global file with photo, six pages, skills on page five.
After: US one-pager without photo for US reqs; UK two-pager with profile and spelled dates for London reqs; same bullet facts, different order and length.
This won't fix applying to roles you're not qualified for. It stops a qualified file from dying because the parser read your sidebar as your work history.
Test both exports before upload
Run each country-specific export through HireFlow's free ATS resume checker with the posting you're targeting. Confirm job titles and dates survived parsing in plain text, not just on the PDF preview.
Rebuild cramped layouts in the free resume builder , export US and UK versions from the same master, then attach the file that matches the job's country before you hit submit.
Which file tonight
Why your resume needs different formatting for different countries is a parser and screening question, not a translation exercise. US uploads want a one-page, photo-free, single-column file. UK and EU uploads want spelled-out dates, room for history, and sometimes a profile or photo block the same software reads differently.
- Duplicate your master into US and UK/EU exports before the next application.
- Run the Notepad paste test on both files.
- Attach the file that matches where the job sits, not where you live.
Open the req you're applying to tonight. Run the free resume check on the export that matches that country's shape, fix dates and section order, then upload once with the right filename.
Read more
Frequently asked questions
Keep one master with your facts, but export two parser-safe versions. US uploads want a one-page resume without photos or birth dates. UK and EU portals often expect a two-page CV with spelled-out dates and sometimes a photo block. The same PDF name in both markets usually means one market's file fails parsing or human screening.
Many large employers run the same platforms, including Workday and Greenhouse, but local HR teams configure different required fields and length norms. A file that parses in New York can still look incomplete in London if section order, date format, or personal detail blocks do not match what that country's recruiters expect to see.
Some UK and EU corporate roles still expect a small professional photo on the CV file, especially outside tech. US corporate applications should not include a photo. If the posting is silent, match the country where the job sits, not where you live.
Spell out the month everywhere you can: January 2022 to March 2024. Numeric dates like 03/04/2024 confuse US and EU parsers differently. Month Year on one line under each job title is the safest default across regions.
Follow the posting. US corporate portals usually accept PDF if the layout is single column. Some UK public-sector and EU portals still ask for DOCX. When the posting is silent, PDF for US roles and DOCX for UK/EU roles is a practical starting point, then run a plain-text paste test before you submit.