9 min read
Your CV isn't failing because you're underqualified. It's failing because the Greenhouse preview can't map employers to dates when the layout fights read order.
Check your resume for free on the exact DOCX or PDF you'll attach. If job titles import blank, fix structure before you tweak summary wording again.
Tonight you'll rebuild one master CV, walk six upload steps, and read the Greenhouse field preview like a recruiter would. You won't need a new template shop subscription or a keyword stuffing tool.
This won't turn a mismatch role into an offer. It stops a qualified UK IT file from dying because the parser read your skills column before your current employer.
Quick wins
- Move phone and email out of Word headers into the first body lines.
- Replace icon skill rows with a plain Skills section and hyphen bullets.
- Re-export after Find/Replace swaps smart quotes and odd dashes to ASCII.
What Greenhouse extracts from a UK IT CV
Greenhouse careers pages pull your upload into structured fields: name, contact, work history, education, and sometimes skills. UK IT CVs often look fine on screen yet import with employers stacked under the wrong dates when tables or columns change read order.
The preview panel is your real first impression. Recruiters notice when your latest title shows under a university row.
Greenhouse ATS resume optimization for UK IT CVs is mostly structural. You are not gaming a hidden score. You are making sure each role block survives copy/paste into their grid.
Before: Contact details only in a footer band and job dates inside a two-column Canva row.
After: Email and mobile on line two of the body, each role as Company, Title, Jan 2022 to Mar 2025, then bullets.
UK norms still apply. You can skip a photo, keep A-levels concise, and spell licence with British forms. But the parser does not care about politeness. It cares whether strings arrive in order.
If you've never opened the field preview, read Greenhouse resume formatting: what breaks and why for symptom photos before you rewrite bullet verbs tonight.
Contract and IR35 roles still need clear client names and engagement dates in the same block. Do not hide consultancy stints inside a generic Projects header without employer strings, or Greenhouse may treat them as hobbies.
Graduate and career-switcher IT CVs follow the same parser rules. Your bootcamp projects go under a dated Education or Projects block with Month Year, not as floating tiles above Experience.
Open-source contributions help when you tie them to a bullet under the job where you had employer time to maintain them. A standalone GitHub heatmap image still will not import as work history.
Six steps before you hit Apply on Greenhouse
Work in order. Each step ends with something you can see in plain text or in the upload preview.
Step 1: Freeze a single-column master
Open your CV in Word or Google Docs exported to DOCX. Turn on formatting marks. If you see table gridlines around experience, rebuild that section as stacked lines. Delete text boxes that hold summaries or skills.
Before: Skills row built from Font Awesome icons in a three-column table.
After: Skills heading with lines like Python, Terraform, and AWS on separate rows.
Step 2: Standardise UK job blocks
For each role use Company on its own line, Title on the next, then Month Year to Month Year using words, not slashes. Keep location optional on the company line. Bullets sit underneath, not beside dates in a margin column.
Illustration bullet for a fictional platform engineer: Built internal developer portal in TypeScript, cutting deploy lead time from forty minutes to twelve for twelve squads in Q2.
Step 3: Scrub punctuation that breaks parsers
Paste the full CV into Notepad or TextEdit once. If bullets turn into question marks or titles jump above names, fix encoding before upload. Replace smart quotes, non-breaking spaces, and fancy dashes with straight quotes, normal spaces, and hyphens.
UK keyboard layouts still produce curly apostrophes in words like team's or manager's. Run Find/Replace in Word on apostrophe variants until plain ASCII sticks. That five-minute pass prevents random line breaks in Greenhouse.
Step 4: Mirror posting language in dated bullets
Highlight three must-have tools from the Greenhouse posting. Place each term once in the first bullet under the job where you used it. A skills cloud without dates does not rescue a thin experience import.
Pair this with Score your job match if you're unsure which req strings you're missing on page one.
Step 5: Choose DOCX or text PDF for this employer
Save both exports. Upload the one that keeps selectable text when you highlight in Preview. If neither works, rebuild from a blank Word doc instead of a design export.
Mac Preview and Adobe Reader behave differently on the same PDF. Test on the laptop you'll use to apply. A file that selects cleanly on phone often fails on desktop upload widgets.
Step 6: Read the Greenhouse preview like a recruiter
After upload, scroll every imported field. If education swallowed your latest title, fix the block above it and re-upload. Do not submit while dates show Not Available.
Copy-paste UK IT CV skeleton (edit brackets only):
[Full Name]
[City, UK] · [Phone] · [Email] · [LinkedIn URL plain text]
Professional Summary
Two lines naming role family plus one proof metric from a recent job.
Professional Experience
[Company Name]
[Job Title]
[Month Year] to [Month Year]
- Bullet with posting keyword in first ten words
- Bullet with scope and tool
Education
[University]
[Degree title]
[Month Year] to [Month Year]
Skills
[Tool], [Tool], [Tool]
Certifications
[Certificate name] ([Exam code]), [Year]
I've screened Greenhouse queues where the PDF looked designer-clean and the imported profile showed an empty latest title; the fix was always moving dates out of a table, not adding more adjectives.
Edge case: if the posting asks for a cover letter in the same Greenhouse form, upload the CV you tested first. Do not tweak layout between files in one sitting unless you rerun the preview on both.
Remote-first UK roles still need a city or region on line one so recruiters know timezone overlap. Do not put that string inside a map widget or footer icon row.
Security clearance lines belong near the summary, spelled exactly as the posting, but keep them as plain text. Badge graphics often break the line after Security so clearance words attach to the wrong section.
When you maintain a master CV, duplicate it before tailoring keywords. That way a bad experiment on one export cannot corrupt the parser-safe skeleton you already verified.
Layout traps UK tech CVs still use
- Using a Europass-style table for languages and accidentally nesting job dates inside it.
- Putting GitHub links only as icon buttons without plain URL text nearby.
- Listing every sprint tool in a word cloud while the latest employer imports without dates.
- Saving PDF from Figma or Canva when the posting allows DOCX, then blaming Greenhouse.
- Duplicating the same keyword ten times in white text (recruiters notice, parsers may strip it).
- Leaving A-level grades inside a nested table while job history sits outside it, splitting parser loops.
When you fix one trap, rerun the preview before you batch apply to similar Greenhouse boards. The same parent company sometimes reuses one broken template across subsidiaries.
Before: Two-column CV with skills on the left rail and jobs on the right.
After: One column with Skills after Experience so read order matches how Greenhouse loops roles.
For broader UK layout rules outside Greenhouse, see CV formatting recruiters actually read after you fix the parser preview.
Preflight tools that match the upload
Run checks on the same bytes you'll attach. A profile PDF from a social site is not the same file as your upload.
Run the free ATS check on your DOCX or PDF. If titles and employers populate, keep the layout. If only Skills fills, rebuild job blocks before you apply again.
If you're rebuilding from scratch, build your resume in a single-column shell, paste your dated roles back in, and export once. Fewer exports means fewer chances to reintroduce tables.
Optional: draft a short cover letter after the CV preview passes using the cover letter generator so both files stay plain text. Do not let letter formatting delay fixing empty Experience fields.
Save a screenshot of a clean Greenhouse preview with personal details cropped. Next time you tailor keywords, compare imports so you notice the first field that breaks.
Ship the boring file
Greenhouse rewards CVs that look almost dull in Word: one column, plain headings, ASCII dates, keywords inside dated bullets. Fancy layout is for humans holding paper, not for the preview pane beside the Apply button.
Run the six steps once on a master file, then tailor bullets per posting without touching structure. You'll spend less time guessing why silence happened and more time on interviews you actually want.
Job searching is draining enough without fighting your own margins. Fix the preview, submit, and move on to the next req with the same skeleton.
Keep a one-line note per apply with the export type you used and whether the preview passed. Patterns show up fast: one agency template might always break dates even after you fix keywords.
And if a recruiter asks for a Word version after you already uploaded PDF, send the same parser-safe DOCX you tested, not a quick export from a design tool you used for a profile page.
Read more
Frequently asked questions
Upload whichever export keeps selectable text and preserves a single-column read order. Many UK tech employers accept both. If the Greenhouse preview garbles employers after a PDF upload, retry with DOCX saved from Word without text boxes. If DOCX strips your spacing, switch to a text-based PDF exported from Word, not from a design tool.
Default to British spellings on UK applies, but mirror the job ad when it uses US terms for stack names. Greenhouse search still depends on exact strings in the posting. Match Terraform, Kubernetes, and product names literally. Do not swap organise for organize in a bullet if the req repeats the US form three times.
Titles often break when they sit in a table cell, a text box, or a two-column header row. The parser reads left to right and may attach your title to the previous employer. Move title, company, and Month Year range into plain stacked lines in the body, then re-upload and read the preview fields.
Yes, if both pages stay one column and section headers repeat clearly. Length matters less than whether each role block imports with dates. Cut older hardware support bullets before you shrink fonts or switch to a cramped template that hides dates in a margin column.
List certifications as their own section with plain lines, not icons or badge graphics. Put exam codes in the same line as the certificate name. If the posting names AWS Solutions Architect or CKA, echo that string once under a dated job bullet, not only in a sidebar skills cloud.