12 min read
You applied through a UK employer's Greenhouse careers page. Confirmation landed in your inbox. A week later there's still no recruiter note, and you're wondering if anyone opened the CV you spent Sunday polishing. That's usually a parse problem, not a talent problem.
Check your resume for free on the posting before you reopen the upload field. You're confirming whether Greenhouse can see your latest employer, not chasing a mystery score.
This guide differs from a generic fix list: after every step you'll run a sixty-second check so you don't stack heading tweaks on a file that's still a two-column image export. Job hunting while you're employed or between contracts is draining enough without five blind re-uploads. Block forty-five minutes once instead of losing an hour each night to mystery silence from bad imports.
Quick Wins
- After step one: highlight text in the PDF; if you can't select words, stop and rebuild.
- After step two: paste into Notepad; current employer must appear before skills.
- After step four: every role uses the same Mon YYYY pattern.
What Greenhouse does with your UK CV on upload
Greenhouse fills database columns so coordinators can filter on employer, title, tenure, and location. It is not grading your design. A CV that looks brilliant in Preview can import with employers missing while education looks perfect.
UK CV templates often use sidebars, icon fonts, and tables because humans scan them quickly. The parser reads left to right like a typewriter. Skills in column one frequently land above your current job, which makes tenure filters fail before a human opens the attachment.
The step-by-step angle here is gating. Each procedure step ends with a pass/fail test on the same file you'll upload. If the gate fails, you do not move on to headings or keywords. That saves an evening compared with tweaking bullet verbs on a layout Greenhouse still reads backwards.
Remote UK roles still use the same import. City and right-to-work notes belong on plain lines at the top, not inside a footer band parsers skip. Two-page CVs are fine when both pages stay one column end to end.
For a broader list of common UK parse failures without the between-step tests, see avoiding common UK CV parsing issues on Greenhouse . Use this page when you want an ordered runbook with checkpoints.
Greenhouse ATS resume optimization UK CVs: five steps with gate checks
Step 1: Choose a file Greenhouse can read
Open the application page and note which formats it lists. When Word is allowed, save as .docx from a plain Word document, not from a design tool export. When only PDF is allowed, print to PDF from Word so the text stays selectable.
Skip: scanned paper CVs, phone photos, and portfolio PDFs where the CV page is a flat image. Greenhouse cannot search text that is not text.
Gate test: Open the PDF, press Ctrl+A or Cmd+A, copy, paste into Notepad. If you see readable sentences, pass. If you see blank space or gibberish characters, fix the export before step two.
Before: Canva export saved as PDF with non-selectable text.
After: Word document saved as .docx, then print-to-PDF with every line selectable.
Step 2: Flatten columns and tables
UK templates love a coloured sidebar for skills and contact icons. Move phone, email, city, and profile URL to plain lines at the top of the body. Shift tools into bullets under the job where you used them. Toggle gridlines in Word; if you see a table around dates, rebuild that block as stacked lines.
Gate test: Paste the full CV into Notepad again. Read the first fifteen lines of experience content. Your current employer name must appear before any standalone skills paragraph. If Python or stakeholder management shows up first, flatten further.
Contract and interim roles stay as repeated blocks: agency (client), title, Mon YYYY to Mon YYYY, bullets. Do not merge three contracts into one paragraph because the parser cannot split tenure.
Logos for past employers become stray characters in paste tests. Type the legal employer name you would put on a payroll form. One plain line beats a branded header strip.
Step 3: Rename sections for the parser
Use Experience, Education, and Skills as written. A heading like Key Achievements can work if it sits above dated bullets tied to employers. A heading like Personal Brand Statement often maps nowhere, so the whole block disappears from recruiter filters.
I've screened Greenhouse queues where the PDF showed three solid roles and the parsed profile listed only education because the experience header was a graphic banner.
Gate test: Search the .docx for the word Experience as plain text, not inside an image. Each job block should have a visible employer line above bullets. If headings are pictures, replace them with typed words.
Before: Section title Career Journey as WordArt.
After: Plain heading Experience with employer lines beneath.
Step 4: Standardise UK dates
Write Jan 2022 to Present on one line with the job title. Repeat Mon YYYY for every role. Career breaks get one honest line: Career break, Sep 2023 to Jan 2024. Do not hide gaps inside merged table cells.
Gate test: Scan every date string. If one role uses 03/2021 and another uses March 2021, pick Mon YYYY and fix both before step five. Mixed formats often split start and end into wrong fields.
Step 5: Full paste-test, then apply once
Select all, copy, paste into Notepad. Read aloud. If your current company is not in the first ten lines of experience text, return to step two. When the read order matches how you'd explain your career on a phone screen, upload once, screenshot any employer preview, and save it beside the job reference in your tracker.
Only now mirror keywords from the posting in bullet one. Layout gates come first; tailoring second.
If the employer shows a parsed preview after upload, compare it to your Notepad paste from step five. Mismatches mean one more layout fix, not more applications tonight.
Name the file with employer shorthand and date: Northwind_PM_Analyst_Oct2026.docx. Humans find it faster in email threads; you avoid attaching last week's export by mistake.
Copy-paste experience block (edit brackets)
EXPERIENCE
[Job title] | [Employer], [City] | [Mon YYYY] to Present
- [Bullet with tool from posting and scope you can defend on a call]
- [Second bullet with outcome illustration, not a keyword list]
[Job title] | [Prior employer], [City] | [Mon YYYY] to [Mon YYYY]
- [Bullet tied to sector or regulation the req mentions]
Pair this runbook with UK CV format ATS can read when you need layout rules that apply outside Greenhouse alone.
Mistakes that skip the gate tests
Running all five edits then uploading once. You cannot tell which change fixed the import, and you often reintroduce a table in step four while fixing dates.
Stuffing keywords before step two passes. A dense skills paragraph at the bottom does not repair employers imported out of order.
Using UK address formats in a header graphic. Put postcode and mobile on plain lines in the body so field detection can grab them.
Trusting the Word print preview only. Preview lies. Notepad paste is the cheap truth serum for Greenhouse reading order.
Fixing dates while leaving a skills table intact. Step four cannot pass if step two still hides employers inside grid cells. Return to the failed gate instead of forcing ahead.
Assuming mobile uploads behave differently. The same parser runs on phone and desktop. Gate tests on the file you will upload from your laptop, then upload from either device.
Uploading the same designed PDF to every req. Tailor bullet one after step five passes, not before you flatten columns.
Tools after step five passes
Run the ATS checker on the .docx you'll upload. You're looking for missing sections and scrambled order, not a new template.
Use job match score once every gate is green. Low match with clean parsing means bullet one needs the posting's stack or sector language, not another design pass on the template.
Generate a cover letter for the portal field after the CV file passes step five. Letters do not repair a failed paste test on the CV upload.
Upload once with a boring file that passed every gate
Greenhouse ATS resume optimization UK CVs rewards plain exports tested after each edit. One column, standard headings, Mon YYYY dates, gate checks, then keyword alignment in bullet one. This will not fix applications where you lack must-have credentials. It stops a qualified CV from dying in the import before a human can reply.
Save the Notepad paste that passed step five next to your application screenshot. When a recruiter calls six weeks later, you'll know exactly which file they parsed.
If you maintain a master CV and role-specific exports, run the gate tests on each export before you batch apply. One broken sidebar in the master copy will clone into every tailored file until you fix step two at the source.
Read more
Frequently asked questions
Upload .docx from a single-column Word file when the portal allows it. If only PDF is accepted, export from Word with no security lock and no image-only pages. Scanned CVs and Canva image exports often import as blank experience blocks. After upload, open any Greenhouse preview the employer shows and confirm your current role is row one.
Page count is fine. Sidebars and tables are not. A two-page CV with skills in a left rail can dump employer names into the wrong field. Keep every job title, employer, and Mon YYYY date in one vertical column on both pages.
Use plain labels recruiters recognise: Profile or Summary, Experience, Education, Skills. Creative headings like Career Journey or Core Competencies often map to nothing, so the parser skips entire blocks. Spell out degree names once, then abbreviate if you need space.
Pick Mon YYYY everywhere, for example Jan 2022 to Present. Do not mix 01/2022 on one role and March 2022 on the next. If you took a career break, write the gap on its own line with plain words rather than hiding dates inside a table cell.
Stacking keyword edits on a two-column file wastes time because the parser still reads skills before employers. A sixty-second paste test after each step tells you whether the last change worked before you rename sections or rewrite bullets. You apply once with a file that passed every gate, not five times with guesses.