11 min read
Export a single-column Word CV with standard section headers and no tables. That's Greenhouse ATS UK CV optimization in one sentence. The parser reads your file top to bottom and pairs each job title with the next employer line it finds. Sidebars, skill grids, and fancy headers break that pairing.
Check your resume for free before you reformat. If employer names already land in the wrong Greenhouse fields, keyword edits won't put your current title back on the right company. Layout first. Tailoring second.
Below you'll see why UK CV habits trigger parsing errors, which conventions you can keep, what to do tonight, and where optimizing resumes for Greenhouse ATS still fails after a pretty redesign. You're not alone if role two already looks wrong in the portal preview. Job searching's draining enough without a silent parser swap on role two.
Quick Wins
- Paste your CV into plain text; fix any jumbled employer order.
- Delete sidebar skills columns; name tools inside experience bullets.
- Stack employer, title, and dates on consecutive lines per role.
- Use Work Experience, Education, Skills as section headers.
Why Greenhouse scrambles UK CV layouts
Greenhouse doesn't read your CV like a hiring manager scanning a two-page pack. It extracts plain text in file order and maps chunks into fields: name, employer, title, dates, education.
The pairing rule: each job title attaches to the next employer name the parser finds. When a Canva sidebar lists Excel and SQL on the left while your analyst role sits on the right, the tools can parse as your most recent job.
UK CVs invite that failure. You might have A-levels and degree on page one, a skills table mid-page, and contract roles in text boxes. Greenhouse stores a profile where the last three employers look swapped even though your PDF looked fine to you.
A composite operations analyst still uploads a two-column graduate template with contact icons in a coloured header. The human recruiter opens Greenhouse and sees role one at the wrong bank. That's not a keyword problem. It's field order.
Optimizing resumes for Greenhouse ATS starts with making the parser's job boring. Single column. Standard headers. Vertical stacks per role. Everything else is secondary.
UK conventions you can keep: two pages is normal for experienced candidates. Month-year dates parse fine. Pound amounts inside bullets are fine. Professional memberships belong on the CV when they're on one line under your name, not in a table beside your photo.
UK conventions to drop for Greenhouse: skill grids that sit left of experience, creative section titles, text boxes for freelance projects, and PDF exports from design tools that flatten your bullets into images.
And if you're coming from a US resume habit, read US vs UK CV format differences before you upload. American one-page resume templates with a skills rail cause the same pairing failures on UK applications.
Greenhouse ATS UK CV optimization: fix your file tonight
Work through these steps on the CV you plan to upload next. Exceptions for photos and two-page length are below. The procedure is the same for graduate and mid-level UK applicants.
Step 1: Plain-text damage check
Open the CV in Word. Select all, copy, paste into Notepad or TextEdit. If employer names and job titles alternate in the wrong order, Greenhouse will see the same chaos.
Before: You assume the PDF looks correct so the parser must be fine.
After: You fix anything that reads out of order in plain text before export.
Step 2: Collapse to one column
Remove sidebar columns, text boxes, and floating project blocks. Drag every bullet into the main body. You lose some visual polish. You gain correct employer-title pairing.
Edge case: you use a UK CV with a photo. Keep the photo if the employer expects it, but move name, phone, email, and city to plain lines. Don't trap contact details in a table cell beside the image.
Step 3: Standardise section headers
Use Profile or Personal Statement, Work Experience, Education, Skills. Greenhouse maps those labels reliably. Creative headers like "My Journey" land in unlabeled blobs.
Before: Career Highlights · Key Competencies · Roles & Responsibilities
After: Profile · Work Experience · Education · Skills
Step 4: Rebuild each role as a vertical stack
Employer on line one. Title on line two. Dates on line three. Bullets below. No tables aligning dates to the right margin. Month-year dates like "Mar 2021 to Present" parse fine when they sit on the same line as the title or directly under it.
Before: Analyst | Big Four firm (table cell) | 2021 to Present
After: Big Four firm · Analyst · Mar 2021 to Present · three bullets below on plain lines.
Edge case: contract and permanent roles in the same year. List both with honest months instead of merging them into one fictional employer. Greenhouse handles overlap when each block is a clean stack.
Copy-paste UK CV header block
Copy-paste this skeleton into Word and replace bracketed lines:
[Your Name]
[City], United Kingdom · [phone] · [email]
Profile
Work Experience
Education
Skills
Before/after: graduate analyst CV
Before: Responsible for supporting the finance team with reporting and analysis tasks as required.
After: Built weekly management accounts pack in Excel for 3 cost centres; automated variance flags and cut prep time from 6 hours to 3 in Q2.
Before/after: mid-level project manager CV
Before: Managed multiple stakeholders and delivered projects on time across departments.
After: Delivered 4 infrastructure upgrades on schedule for £2.1M capex programme; held RAID log reviews weekly with vendor and internal sponsors.
Step 5: Export and test both formats
Save DOCX from Word. Export PDF from that same file if the posting allows PDF. Run both through a parser check. Upload the format that keeps employer-title pairs intact.
Before: You upload a Canva PDF because it looks more polished.
After: You upload the plain Word export that still reads correctly in Notepad.
Read chronological vs functional resume in 2026 before you switch to a functional layout to hide gaps. Functional CVs often break Greenhouse pairing worse than a honest chronological stack.
Pair with resume rejected by ATS when you never hear back and need to tell parser failure from keyword mismatch.
Common Greenhouse parsing errors on UK CVs
Skills sidebar before experience. Tools listed in a left column parse as a job title. Move SAP, Excel, and SQL into bullets under the role where you used them.
Header credential and contact tables. Name plus degree plus phone in one row splits contact fields across columns.
KPI or module tables mid-CV. Row labels like "Revenue" or "Team size" become phantom job titles.
Right-aligned date tabs. Tabs align nicely in Word and reorder employers in plain text. Put dates on the title line or directly beneath it.
Design-tool PDF exports. PowerPoint and Canva PDFs often flatten to image layers. The parser sees blank space where your bullets were.
Mixing US section labels on a UK file. "Professional Experience" and "Work Experience" on the same CV can split parsing across duplicate blocks. Pick one label and use it for every role.
Listing every GCSE subject. Long education tables push your first job below the fold in plain text and bury employer lines under exam boards. Keep education to degree, institution, and graduation year unless the posting asks for more.
I've opened Greenhouse profiles where a strong UK candidate's second role showed a university module name as the employer. The PDF looked professional. The parser read the skills table first.
Before: Skills table row: Excel, VBA, SQL, Power BI, SAP, listed with no job context.
After: One bullet under the analyst role: Built weekly revenue bridge in Excel and VBA for the FP&A team, cutting manual rework on the Friday pack.
Before: Freelance projects in a shaded text box between two permanent roles.
After: Client name · Freelance Analyst · Jun 2023 to Sep 2023 · two bullets, stacked like any other role in Work Experience.
Edge case: you're applying through a referral link that pre-fills Greenhouse fields. Upload the same clean DOCX you'd use on the public posting. Referrals don't bypass parser order.
Edge case: the employer asks for a "CV" and the portal label says "Resume." The file rules are identical. Single column, standard headers, stacked roles. Don't rebuild in a US template just because the button says resume.
Edge case: you completed a recent certification and added it to a header table. Move the credential to one line under your name or a Certifications section with one entry per line so Greenhouse does not treat the acronym as an employer.
Verify the CV before you tailor keywords
Run the free ATS checker on the DOCX and PDF you plan to upload. Confirm employer names and job titles land in the right order before you spend an hour mirroring posting language.
If you need a letter in the same portal, generate a cover letter from the same plain template family. Matching headers between CV and letter reduces sloppy signals on a quick recruiter screen.
Your next Greenhouse upload
Greenhouse ATS UK CV optimization is a layout job. Single column, standard headers, stacked roles, plain-text test, then keyword tailoring. That order stops qualified UK candidates from losing screens to a parser that read their skills rail as a job title.
Rebuild one role tonight as a vertical stack. Paste to Notepad. Export DOCX. Run the checker. Submit the version that keeps employers paired with titles, not the prettiest PDF in your folder.
When you're tailoring after the layout pass, mirror posting language inside bullets under the correct employer block. Keywords in a sidebar won't attach to the job Greenhouse thinks is current. Bullets under the right stack will.
Save two exports in a folder named after the employer: one DOCX master and one PDF exported from that same file. Upload the format the checker parsed cleanly. If both parse the same, default to PDF when the posting allows it and DOCX when the portal warns about PDF.
This won't fix applying to roles you're not qualified for. It does stop strong files from dying silently when Greenhouse stores the wrong company next to your current title.
Read more
Frequently asked questions
DOCX exported from Word usually parses most cleanly when you built the file in Word with one column and no text boxes. PDF is fine when it is text-based and exported from that same Word file. Scanned PDFs and Canva exports often drop bullets or reorder employers. Test both if the portal allows a choice.
Yes. Page count is not the failure mode. Sidebars, skill tables, and multi-column templates are. A plain two-page single-column CV with standard section headers parses the same as a one-page file when the layout is clean.
A small photo rarely breaks parsing by itself. The problem is header tables that pack photo, name, credentials, phone, and email into one row. Move contact details to plain lines under your name and keep the photo optional for UK employers that still expect one.
The parser reads top to bottom and pairs each job title with the next employer line it finds. Sidebars, text boxes, and right-aligned date columns reorder that sequence. Stack employer, title, dates, and bullets in one vertical column per role.
No. If role two shows the wrong company, adding skills will not repair the pairing. Fix layout first, then place keywords inside bullets under the job where you used them. Keyword edits on a misparsed file waste tailoring time.
