11 min read
You're applying in London on Monday and Chicago on Tuesday. Same jobs on paper. Different upload rules. Your UK CV looks polished to a human skimming page one, then Workday imports your skills column as a mystery employer and drops your real company on row eight. You didn't change jobs. You changed parsers.
That's not a keyword problem. It's a read-order problem. You don't need a new story. You need the right column rules for the portal you're staring at tonight. Before you rebuild ten years of work history, check your resume for free with the posting pasted in. You're confirming whether dates and employer names survived export, not whether you typed enough tools in a sidebar.
Job searching across borders is slow enough without reformatting from scratch every weekend. Below you'll see what each market's parser treats as a job block, before/after pairs across roles, what weak imports share, and copy-paste headers you can drop into Word tonight.
And if you're batching applications in Greenhouse after work, don't upload the decorative UK template first. Build the US single-column file, confirm plain-text order, then keep a British English export in a separate folder for UK reqs. When a posting wants a letter, generate a cover letter from the same job title line you put in the resume so the packet doesn't contradict itself.
Quick Wins
- Export to plain text and confirm each employer name sits directly above its bullets.
- Collapse any two-column UK template into one column before a US Workday upload.
- Spell dates as Month Year on the same line as job title and company.
- Save two files: Lastname_Resume_US.pdf and Lastname_CV_UK.pdf from the same facts.
US vs UK CV formatting key differences to pass ATS in 2024 job applications: what good files look like
Parsers on both sides still read top to bottom. They do not understand design intent. They map headings to fields and hope your dates stay attached to the right employer.
The US bar: single column, standard headings like Professional Experience and Education, Month Year dates beside title and company, no photo, city and region only for location, impact bullets with tools named inside the sentence. Workday, Greenhouse, Lever, and iCIMS treat sidebars as separate job rows when they read left column first.
The UK bar: often two pages with a brief personal profile, Employment History or Career History labels, British English spellings, and sometimes degree classification in Education. UK teams still run ATS, and header tables can scramble there too. The tolerance for layout flourishes is slightly higher until upload strips them.
A composite marketing coordinator whose UK CV leads with a skills grid and paragraph-style job stories can look ready to a hiring manager over coffee. Uploaded to a US req, the parser may read SEO as a job title and bury the agency name. Same person. Different field mapping.
Read Workday resume format 2026 when the employer routes through Workday specifically. This page is the US versus UK layout split before you touch keyword lists.
Edge case: you're a UK resident targeting US remote roles. Strip full street addresses, switch organise and programme spellings for US files, and keep visa or work-authorization lines factual in a single line if the posting asks. Do not hide employment gaps to save space.
Edge case: you're a US applicant targeting London corporate roles. Add degree class when you earned one, use British spellings on the UK export, and keep a personal profile to three lines. Do not paste a US summary that says optimize when the posting uses optimise in the job title.
Edge case: you're returning after a layoff and tempted to keep one global file because you're tired of editing. Two exports take twenty minutes once your master doc is honest. One hybrid upload costs you a week of silence when the parser mislabels your last employer.
Before/after pairs across roles
Each pair shows a UK-leaning layout that breaks US parsing, then the market-appropriate rewrite. Titles and metrics inside bullets are illustrations only.
Pair 1: Marketing coordinator, two-column template on a US req
Before: Left column lists Google Analytics, HubSpot, and Canva with icon bullets. Right column holds two jobs as short paragraphs without metrics. Dates sit in a header table above the name.
After: Single column. Marketing Coordinator, Agency Name, Remote US, June 2021 to Present. Ran email campaigns in HubSpot for 40k subscribers; lifted click-through 14% after A/B testing subject lines in Q1 2024.
Pair 2: Registered nurse, narrative CV vs metric resume
Before: Responsible for patient care on a busy ward. Worked closely with multidisciplinary teams to deliver safe outcomes.
After: Staff Nurse, Regional NHS Trust, Manchester UK, March 2020 to Present. Precepted four orientees on a 32-bed med-surg unit; maintained medication administration record accuracy through weekly audits with charge nurse sign-off.
Pair 3: Accountant, skills table detached from employers
Before: Technical Skills table on page one lists Excel, SAP, and IFRS. Page two lists employers with one line each.
After: Financial Analyst, Retail Group plc, September 2019 to Present. Closed monthly P&L in SAP for 12 cost centres; shortened close cycle from nine days to six after standardising journal templates in Excel.
Pair 4: Project manager, date format and section labels
Before: Employment History heading. Dates as 03/2018 to 11/2023. Company address block under each role.
After: Professional Experience heading for US file. March 2018 to November 2023 on the title line. Project Manager, Logistics Cloud, Denver CO. Delivered SAP rollout across three warehouses on time and 8% under budget cap for FY22.
Pair 5: Customer support lead, long profile vs three-line summary
Before: Half-page personal profile describing passion for customer-centric culture and stakeholder collaboration.
After: Summary: Support Lead with nine years in SaaS ticketing on Zendesk and Salesforce Service Cloud. Cut first-response time from 6h to 90m after queue redesign. Targeting US remote team lead roles.
Pair 6: HR coordinator, photo and full address on US upload
Before: Headshot top right. Full home address and marital status line. Career history begins on page two.
After: No photo. City and country only: Leeds, UK or Austin, TX. HR Coordinator, People Ops Ltd, January 2021 to Present. Onboarded 120 hires in Workday; maintained 98% data accuracy on start-date fields during peak hiring season.
I've screened cross-border stacks in Workday and Greenhouse for years, and the stall pattern is almost always layout: skills floating away from employers, or dates living in a table the parser reads before your name.
Copy-paste US experience block
Use for US reqs. Replace bracketed lines. Keep one column in Word or Google Docs before PDF export.
[Job Title] | [Company Name] | [City, ST or Remote US]
[Month Year] to [Month Year or Present]
- [Verb] [system] [scope]; [metric outcome from your real work].
- [Second bullet with posting keyword in first eight words].
- [Third bullet on scope: team size, volume, or budget you owned].
Skills: [Optional comma list when posting asks; otherwise keep tools in bullets]
Copy-paste UK employment entry
Use for UK reqs. British English spellings. Degree class belongs in Education, not repeated in every bullet.
[Job Title]
[Company Name], [City, UK]
[Month Year] to [Month Year or Present]
- [Duty with technology and outcome].
- [Second bullet aligned to posting language].
Personal profile (max three lines): [Role], [years] experience in [sector], [two posting keywords].
When Greenhouse mangles UK finance CVs, see fixing parsing issues in Greenhouse for UK finance CVs for portal-specific paste tests after you fix column layout here.
What weak cross-border files share
Weak imports rhyme even when the industry changes. Fix these four patterns before you argue about keyword density.
Sidebars and skill bars: tools parse as employers. Collapse to one column for US uploads. Put systems inside dated bullets instead of colored bars.
Date tables in headers: employment blocks detach from titles. Move Month Year to the same line as job title and company in plain paragraphs.
Text boxes for summaries: some exporters drop them on PDF save. Type the profile as normal body text under a standard heading.
One hybrid file for every country: British spellings on a US req and US brevity on a UK CV both signal you did not read the posting. Maintain two exports from one fact base.
Before: Upload the prettier Canva PDF because it matches your brand colors.
After: Upload the boring Word export that survives plain-text paste with employers still glued to bullets.
This will not fix applying to roles you're not qualified for. It stops a qualified file from dying in the parser because the UK template fought the US field map.
Verify layout before you upload
Paste the posting and your export into HireFlow's free ATS resume checker after you rebuild section order. A polished UK CV with scrambled US import still fails the screen even when the greeting line is perfect.
When you are deciding which version to send, score your job match on the US file and the UK file separately against the same posting. Mismatched section labels often hide must-have terms in Skills while Experience stays thin.
Do this now: Plain-text paste test, collapse any sidebar, save US and UK exports, run one checker pass on the file you will upload tonight.
Build both exports tonight
You do not need a new career story for each country. You need two parser-safe shapes built from the same facts: a US resume and a UK CV with localized headings, spellings, and date placement.
- Plain-text paste test on the file you plan to upload.
- Collapse sidebars before any US Workday or Greenhouse upload.
- Spell every date as Month Year beside title and employer.
- Keep Lastname_Resume_US and Lastname_CV_UK in separate folders.
Open one live req. Run a free ATS check , fix the layout, then send the version the portal can actually read.
Read more
Frequently asked questions
Send a US-style resume: single column, Professional Experience heading, Month Year dates on the title line, no photo, and city plus region only. Calling the file a CV does not hurt you. Importing a UK template with a skills sidebar and narrative paragraphs often breaks Workday and Greenhouse before a recruiter opens it.
Follow the posting first. When both DOCX and PDF are allowed, paste-test each export into plain text. US portals on Workday often parse a simple Word file cleanly when dates sit in the same paragraph as the employer name. UK employers sometimes prefer PDF to hold layout. Upload the version that keeps employer lines attached to bullets, not the prettier design file.
Many UK hiring teams expect a short profile at the top. Parsers read it as plain text, so keep it to three lines with role title, years of experience, and two posting keywords. US resumes can use a tight summary with the same discipline or skip it when experience bullets already prove the role.
Use Month Year in words on every role, for example January 2022 to March 2024. Numeric-only cells in tables and DD/MM/YYYY strings confuse some US parsers and older Taleo configs. Consistency matters more than which country you live in today.
No. Correct US vs UK structure stops qualified files from dying in the parser. It does not invent skills. Fix layout and regional labels first, then decide whether the posting is worth a tailored application.