Greenhouse ATS UK IT CV: Avoid Parsing Issues

8 min read

You didn't miss the req because your stack is wrong. You might've missed it because Greenhouse imported your contract role under a bootcamp line while your Kubernetes skills sat in a sidebar the parser skipped.

Before you rewrite bullets for the fifth time, check your CV for free on the exact file you'll attach. Tonight's job is avoidance: stop the formatting choices that trigger parsing issues, then tailor keywords on text Greenhouse actually stored.

If you're applying from a phone, don't assume the preview you saw in Drive matches what Greenhouse parsed. Download the DOCX, upload from desktop when you can, and read the imported profile before you celebrate a submit. That quick check really beats a week of wondering whether anyone opened your file, or could even read it properly at all.

When Greenhouse misreads UK IT CVs

UK IT candidates often use slick templates with skill meters and project grids. Greenhouse maps fields in upload order. A right-hand skills column can import before your current employer, which makes keyword screens look like you left industry years ago.

The tell is the preview pane. If your mobile number is missing or your headline became a blob of punctuation, the human recruiter may never see the proof you already have the stack they asked for.

A composite backend developer keeps a two-column CV with AWS icons in the margin. Greenhouse accepts the upload. Parsed view lists cloud tools under Education and drops the last contract employer. Recruiters who search Platform Engineer never see the string because the parser filed the title under an old apprenticeship block.

Another pattern: the data engineer who exports a portfolio PDF from a design tool for speed. Upload completes. Text fields stay blank. The human recruiter opens the attachment later, but automated filters already skipped the profile because required fields never populated.

Greenhouse isn't scoring your personality. It's trying to slot text into Experience, Education, and Skills boxes. When those boxes are empty, downstream search behaves like you never held the job you listed in the PDF attachment.

I've screened Greenhouse imports for UK tech roles, and the CV that survives is dull on purpose: one column, plain headings, dates glued to titles, no icons pretending to be skills.

For how tables scramble reading order across ATS platforms, pair this page with why tables break ATS parsing . For keyword work after preview passes, see tailoring CVs for European IT job match scores .

Greenhouse ATS optimization for UK IT CVs before you upload

Work through these six steps in order. Don't jump to keyword edits until step five shows a clean preview.

Step 1: Run the paste test

Open your PDF or DOCX, select all, paste into Notepad or TextEdit. If job titles arrive before employers and dates sit on their own lines, you passed. If text lands as gibberish or blank, rebuild in Word with default styles before you touch Greenhouse again.

Before: Canva PDF export, paste test empty, Skills block missing in preview.
After: Plain DOCX, paste test shows employers in order, preview lists current role first.

Step 2: Kill columns and text boxes

Turn on formatting marks in Word. Delete tables used for spacing. Move skills under a Skills heading as a simple list. Side projects belong under Work Experience or Projects, not in a floating box.

If you built the CV in Google Docs, use File then Download as DOCX before upload. Some browser PDF exports flatten oddly compared with Word's Save As PDF on the same single-column source.

Step 3: Rename section headings

Swap My Journey for Work Experience. Use Education, Skills, and Certifications exactly. Creative headings score points with humans in email, but Greenhouse may dump that block into Notes.

Keep Certifications separate from Skills even when both lists mention cloud platforms. Issuer names and years help humans scan quickly and give parsers a clean anchor line to grab.

Step 4: Standardise dates on the title line

Write Senior Platform Engineer, FinTech Ltd, Jan 2022 to Present on one line, then bullets below. Mixed formats like 01/22 and January 2022 in the same file confuse timeline imports.

Copy-paste Work Experience skeleton after you flatten columns:

[Job Title from posting] | [Employer] | [City or Remote] | [Month Year] to [Present or Month Year]
• Delivered [system or product] using [tool from posting] for [user or volume scope].
• Cut [incident or ticket type] by [illustrative % in your own metric] through [method].
• Partnered with [team] on [delivery outcome tied to posting must-have].

[Prior Title] | [Prior Employer] | [Location] | [Month Year] to [Month Year]
• [Bullet continuing reverse chronological order].
              

Step 5: Upload once and open preview

Submit the application far enough to see the parsed profile. Scroll Experience top to bottom. If order is wrong, fix the source file instead of uploading the same export three times.

Screenshot the preview when the current title appears first. That image saves you from doubting whether Greenhouse changed between Monday and Thursday when you're juggling multiple reqs.

Before: CV with right-hand date column, internships float above current contract.
After: Dates inline with titles, reverse chronological order in preview, mobile number in Contact block.

Step 6: Patch empty fields manually

When preview drops a degree or cert, paste plain text into the Greenhouse form fields. Keep the cleaned DOCX as the attachment recruiters download so everyone sees the same story.

Optional free-text questions are a second chance to restate your current title and top stack when the parser mangled the attachment. Answer in short sentences with the same keywords you used in bullet one.

Edge case: overlapping contract roles. List both with honest Month Year ranges instead of stacking roles in one table cell. Edge case: career pivot into IT. Fix layout before you rewrite bullet one; parsers won't wait for your story to make sense in a sidebar.

Formatting traps common on UK IT CVs

Resubmitting the same designed PDF with a new filename. Renaming doesn't add a text layer. Rebuild once in DOCX and stop burning req IDs.

Keyword stuffing after a failed parse. Extra Skills lines don't help if Work Experience never imported. Layout first, bullet one second.

• Competency wheels and star ratings instead of spelled-out tools.
• Contract vs permanent roles in a table with client names in the right column.
• LinkedIn icons instead of the full profile URL in Contact.
• UK spelling mixed with US spelling in the same skills list.

Before: Third upload of the same sidebar template because the progress bar looked faster.
After: One DOCX rebuild, parse check pass, single submit with preview screenshot saved in your tracker.

Pick UK English throughout if the posting uses organise and programme. Consistency helps human reviewers even when the parser is forgiving on spelling.

Treating silence as rejection is expensive when the fix was visible on the review screen. Open preview, read the imported timeline, and only then decide whether the req is a long shot.

If you're switching from a creative CV to a parser-safe version, keep the polished PDF for networking email. Attach the boring DOCX to Greenhouse so humans and parsers see the same facts in the order search tools expect.

Tools that fit this workflow

Run tools on the exact export you'll attach: parse check, layout fix, second parse check, then upload. Don't batch ten portals before you confirm text copies.

After step one passes, compare your CV to the posting with the job match score tool so you edit keywords on text that will actually import.

If you're rebuilding from scratch, build a single-column CV before you return to Greenhouse.

Upload once with a file Greenhouse can read

Greenhouse ATS optimization for UK IT CVs isn't about hiding experience. It's about presenting it in a flat order parsers can map before a recruiter searches your title string.

• Run the paste test before any UK apply block tonight.
• Save a screenshot when preview lists current role first.
• Log req ID, file version, and parse pass in your tracker row.

When the posting asks for a cover letter, draft it after bullet one matches the req using the cover letter generator so the letter repeats proof instead of filler.

You won't fix every employer-side bug from your laptop. You can stop submitting files that fail the same paste test three nights in a row.

When you're ready to compare wording against the posting, run the match score on the DOCX that passed preview, not on an older PDF that never imported. That single habit stops most false "ATS hates me" spirals.

For broader Greenhouse layout rules beyond UK IT CVs, bookmark Greenhouse resume formatting: what breaks and why and return to it when a new template tempts you mid-search.