US vs UK CV Formatting for ATS | Key Differences | HireFlow.net

11 min read

You didn't move countries. You just changed where you're applying. Same experience, same skills, and suddenly Workday shows a blank skills section or a UK recruiter emails back asking for a "proper CV." You're not imagining it. US and UK hiring files look similar on the surface and parse differently under the hood.

That's why US vs UK CV formatting differences for ATS matter before you hit submit. Portals don't care that you're qualified. They care whether your headings, dates, and file type map into fields recruiters can search. Before you send another cross-border application, check your resume for free against the posting so you're not guessing which version the parser actually read.

I've screened imports in Greenhouse and Workday on both sides of the Atlantic. The candidates who stall usually have strong backgrounds trapped in the wrong regional template. This guide covers length, section order, spelling, PDF versus DOCX behavior, and the edge cases that trip up career changers and remote applicants.

You'll get before-and-after examples for US and UK layouts, a copy-paste header block, portal habits that stop scrambled dates, and mistakes that waste good applications on the wrong file name alone.

What US vs UK CV formatting means for ATS parsers

A US resume and a UK CV are not two random templates. They're two sets of recruiter expectations baked into how parsers label your text. Workday, Greenhouse, Lever, and Taleo all strip design and map content into searchable fields: name, experience blocks, education, skills.

Regional style changes which fields get filled. US files usually lead with a short summary and metric-heavy bullets. UK files often open with a personal profile, list qualifications with dates, and carry slightly longer role descriptions. When you upload the wrong style, parsers still run. Recruiters just see gaps.

Cross-border rule: Parsers read plain text in order. Regional polish only helps if section headings and dates survive the import.

This is not about tricking the system with keyword stuffing or hiding white text. That fails human review fast. What you're fixing is structure: the right labels, the right length, the right spelling, and a file type the portal can actually read.

What this is not: a reason to pad pages with hobbies, photos, or full home addresses on US applications. UK norms around personal details have tightened too. Keep contact info professional: email, phone, city, LinkedIn URL when allowed.

For a broader adaptation walkthrough, read UK CV vs US resume adaptation for international jobs . This post stays focused on what parsers do differently when you cross markets.

Step-by-step: adapt US vs UK CV formatting for ATS

Step 1: Pick the market from the posting, not your passport

Read the employer location, payroll region, and portal language. A London HQ posting on Greenhouse still wants UK spelling even if you're American. A US remote role on Workday wants resume labels and one-page discipline for early-career hires.

Before: One three-page "international CV" with a photo, full street address, GCSE list, and US-style quota bullets mixed together.
After: Two saved files. US: two pages max, no photo, Summary plus Experience with Salesforce metrics. UK: two pages, Personal Profile, Experience with fuller context, Education with qualification dates.

Name each version clearly on your desktop. You won't remember which export you uploaded at 11 p.m. on a Tuesday.

Step 2: Reorder sections the way local parsers expect

Standard headings beat creative labels every time. Parsers map "Experience" and "Education" reliably. They dump "Career Journey" or "Where I've Added Value" into generic buckets.

US resume order: Name and contact line, optional Summary (3 lines), Skills row, Experience (reverse chronological), Education, Certifications if relevant.
UK CV order: Name and contact, Personal Profile (3 lines), Experience, Education and Qualifications, Skills, optional Interests only if they add professional signal.

Put email and phone in the document body, not a header/footer. Both Workday and Greenhouse drop margin contact lines on import more often than you'd think.

Step 3: Fix spelling, labels, and date formats

UK postings: organise, programme, analyse, CV, referees available on request. US postings: organize, program, analyze, resume, references available upon request. Mixing them in one file looks careless to humans and confuses keyword matching.

Use Month YYYY everywhere: Mar 2021 to Present. Avoid day-first dates on US uploads and ambiguous 03/21 strings that parsers read as March or May depending on config.

Mid-level analyst example:
Before: "Responsible for weekly reports" with UK profile paragraph listing every module from university.
After (US): "Built weekly Tableau dashboards for 12 stakeholders, cutting report prep time by 6 hours."
After (UK): Same bullet plus one extra line of role context: "Seconded to finance during year-end close."

Step 4: Choose PDF or DOCX with a live portal test

You'll hear absolutes about file type. Ignore them until you test. PDF exported from Microsoft Word usually preserves visual layout for recruiters who download the attachment. DOCX often gives parsers cleaner access to headings when tables aren't involved.

Greenhouse frequently accepts both. Workday sometimes maps DOCX employment history more accurately when each job is a simple stacked block, not a table cell. Upload a test application when you can, or paste all text into Notepad and confirm Experience reads top to bottom.

Before: Canva PDF with icons and a two-column skills sidebar.
After: Single-column Word DOCX at Calibri 11 pt, then optional PDF export from Word only. No scanned photos of printed pages.

Read how resume file type impacts screening when a posting allows both formats and you need a tiebreaker.

Step 5: Tailor keywords without breaking regional style

Open the posting. Highlight must-have tools, certifications, and verbs. Mirror exact phrases in your first three bullets under the most recent role. US recruiters want numbers early. UK recruiters still want numbers, but they'll read one extra line of scope per job.

Account executive composite:
Before: Generic pipeline bullet with no CRM name.
After (US): "Exceeded quota at 118% across 42 enterprise accounts in Salesforce, average deal size $280K."
After (UK): Same metric line plus sector context: "Focused on FTSE 250 financial services accounts."

Run the tailored file through a match check when the role lists more than eight must-have tools. Fix parsing warnings before you chase keyword gaps.

Step 6: Preview parsed fields, then submit

Many candidates upload and click submit. Workday and Greenhouse both offer review screens where you can edit scrambled rows. Use them on a laptop when you have more than three jobs listed.

Scroll every employment block. Confirm employer, title, start month, end month. If a UK qualification landed inside a job title field, shorten the heading in your source file and re-upload.

Greenhouse sometimes shows parsed text beside the PDF thumbnail. Read the parsed view. That's often what keyword scoring uses, not the pretty attachment preview.

Edge case: UK candidate applying to US remote roles

Remote US employers still want US resume conventions: no photo, tight length, metric bullets, US spelling. Add one neutral work-authorization line if the portal asks about sponsorship. Don't bury visa details in paragraph three.

Drop secondary school credentials unless you graduated within the last three years. US recruiters scanning eight years of experience don't need A-level subjects clogging page one.

Edge case: US candidate applying to UK corporate roles

Add a three-line Personal Profile even if it feels redundant. UK hiring managers expect it. Keep it keyword-rich and short. Expand education with degree class or equivalent when the posting lists qualifications explicitly.

Avoid US-only jargon recruiters won't search: "varsity athlete" without context, GPA for mid-career roles, or state abbreviations without country when the employer is UK-based.

Copy-paste header blocks (US and UK)

Open Word. Single column. Calibri or Arial 11 pt. Paste the block that matches your target market, then rebuild jobs underneath.

Save US version as DOCX, export PDF from Word, paste-test both. Save UK version the same way. Stop when Experience reads cleanly in Notepad for each market.

Comparison table: what parsers and recruiters notice first

Registered nurse composite:
Before: US one-pager with RN license in a sidebar table.
After (UK): Profile line with NMC registration, Epic and patient ratio metrics in plain bullets, Education listing qualification year.
After (US): License on one line under name, ratio and unit metrics in first two bullets, no profile paragraph.

Common US vs UK CV formatting mistakes for ATS

Uploading one "global" file everywhere. Parsers don't translate regional style. Save two versions and match the posting country.

Keeping UK personal details on US uploads. Photos, marital status, and full street addresses create parsing noise and raise bias concerns. Strip them for US corporate portals.

Using creative section titles. "Professional Snapshot" and "Key Achievements" sound fine in a deck. Parsers want Experience and Education.

Assuming PDF always wins. Some Workday configs parse DOCX dates more reliably. Test both when allowed instead of guessing from a blog headline.

Mixing US and UK spelling in one document. Pick a market per file. organise and organize in the same upload looks like you didn't proofread.

Skipping the parsed preview. The attachment thumbnail can look perfect while employment rows are scrambled. Fix parsed fields before submit.

Renaming a UK CV "resume" without changing structure. Filename alone doesn't fix section order. Recruiters still see a UK layout in a US req.

Test US and UK versions before the real application

Run each export through HireFlow's free ATS resume checker with the full job description pasted in. You'll see parser-style output, date alignment, and keyword gaps without burning a live submission on the wrong file.

Compare PDF and DOCX side by side for the same market. Keep whichever version imports complete Experience rows in Workday or Greenhouse, even if the other looked sharper in Preview mode.

When the role asks for a cover letter, draft with the cover letter generator , then match employer names and spelling to the resume version you're uploading. US letter, US resume. UK letter, UK CV.

Pair this with Workday resume upload formatting fixes when your US file parses cleanly at home but breaks inside the portal preview.

Two markets, two files, one parser-safe habit

US vs UK CV formatting for ATS comes down to saving two honest versions: the right headings, spelling, length, and file type for each market. Workday and Greenhouse don't care where you went to school. They care whether your experience imported into searchable rows.

• Build separate US resume and UK CV exports with standard section labels parsers recognize.
• Test PDF and DOCX with a paste check before you trust either format on a live req.
• Edit parsed preview rows on the portal so recruiters see the same story your file tells.

Open both versions, run the free resume check , fix the first section each report flags, and save new filenames by country. That's how you stop losing cross-border interviews to a template built for the wrong side of the ocean.