11 min read
When Greenhouse UK IT uploads look fine in Word but break in preview, flatten tech stacks out of sidebar grids into plain Experience lines, spell every date as Month Year on its own row, and move AWS or Kubernetes into bullet one under the employer that used them. Re-upload once and read the preview before Submit. That's the fix. Dates import blank while Skills still lists Terraform because the parser read your layout grid before your job block.
You're not under-qualified for the platform or DevOps req. You're watching a CV that looked sharp on screen turn into a profile with empty tenure fields and tools floating nowhere. You don't need a fancier template. Before you rebuild from scratch, check your resume for free with the posting pasted in. You're confirming employer order and whether sprint bullets still carry dates, not guessing which buzzword failed.
UK tech hiring on Greenhouse moves fast around funding rounds and product launches. Recruiters don't have time to reverse-engineer a scrambled import. Job searching while you're still shipping features is brutal enough. This page is about export order and field mapping, not a lecture on personal branding.
Below you'll see why two-column CVs fool UK engineers, the exceptions where a plain file still fails, formatting pairs you can paste tonight, and what to run before you hit Submit again. I've screened stacks of these in Greenhouse where the preview showed Kubernetes and no contract dates.
When the portal asks for a cover letter after upload, don't repeat lines Greenhouse already misread. Generate a cover letter from the flattened file so employer names match the corrected preview.
Quick Wins
- Single-column Word file. No skill tables or icon rows.
- Month Year on every role. Same format throughout.
- AWS and Terraform inside the dated bullet that used them.
- Contract clients on separate plain lines with agency noted once.
Why Greenhouse ATS resume optimization UK IT starts with layout, not keywords
Greenhouse does not read your CV like a hiring manager skimming a sprint retro. It chunks the upload into employer, title, start date, end date, education, and bullet text. UK IT templates love two-column skill rails, certification badges, and shaded project callouts. Those elements often parse before your current contract line.
The preview screen is what many recruiters screen first. When microservice bullets sit inside table cells, Greenhouse frequently imports the bullet text without the Month Year range on the same row. Skills still lists AWS because the left-rail grid parsed cleanly. You look like a tool-heavy candidate with no dated delivery experience.
UK CV design fights the importer on purpose. Badges for AWS, Azure, and CKA look credible on PDF. Icon rows for Python, Go, and Terraform signal stack fluency. The parser treats those blocks as early text. Your current employer line can land fourth while Kubernetes attaches to a phantom first job.
London and Manchester tech reqs repeat the same language: CI/CD, microservices, platform ownership, incident response. That language belongs in dated Experience bullets tied to the employer that ran the service. When it lives only in a Skills table, the preview shows keywords without the team that shipped the release. Recruiters can't tell which product you owned.
Contract and IR35 stints make it worse. A block that lists Various clients with no Month Year tells Greenhouse one long employer with a blank range. Recruiters assume a gap even when the PDF shows four logos in a row. Each client needs its own dated line with the agency in parentheses once.
Footer contact bands cause the same scramble. Phone and email in a Word footer often parse before body text. Greenhouse maps them into name or summary fields while your first job title drops under Education. Move contact once into the body under your name on line one.
For file-type choices after layout is clean, read how resume file type impacts screening . Parsing order comes first. Export format second.
Formatting fixes UK engineers paste tonight
Work through layout before you rewrite bullets. One pass on structure saves a night of keyword tweaking the parser never reads in the right field.
Backend engineer at a fintech scale-up
Posting wants microservices, AWS, and payment APIs for a Greenhouse employer in Shoreditch.
Before: AWS and Kafka in a right-rail Skills grid. Project metrics in a two-column table. Dates show as 03/21 and Present in mixed formats.
After: NovaPay Ltd, London. Senior Backend Engineer | March 2021 to Present. Built payment APIs on AWS handling 2.4M daily transactions; cut p99 latency 18% after migrating three services to event-driven Kafka flows in 2024.
DevOps contractor after agency rotation
Posting lists Terraform, EKS, and on-call ownership for a platform team in Manchester.
Before: Terraform buried in Skills. One block reads Cloud Engineering with no Month Year lines.
After: RetailCo (via Apex Digital, contract converted July 2023) | January 2022 to Present. Owned Terraform modules for EKS clusters across four environments; reduced deploy time from 45 to 12 minutes. Platform Engineer, MediaStream Ltd | June 2019 to December 2021. Led on-call rotation for twelve services; cut MTTR 22% after runbook standardisation.
Full-stack developer at a healthtech startup
Posting wants React, Node, and NHS integration experience for a Series B company.
Before: React in an icon badge row with no project pairing. NHS work inside a shaded KPI box with no employer line.
After: CareBridge Health, Bristol. Full-Stack Developer | September 2022 to Present. Shipped patient portal in React and Node used by 14 GP practices; integrated HL7 feeds for NHS spine lookups with zero downtime during go-live week.
Data engineer on fixed-term contract
Posting searches Spark, dbt, and warehouse migrations for a retail analytics team.
Before: Contract months hidden under the client logo only. Spark appears once in Skills with no date anchor.
After: BigShop Retail (via DataHire Ltd) | April 2023 to March 2024. Migrated legacy SQL jobs to dbt on Snowflake; cut nightly pipeline runtime 31%. Data Engineer, FinLedger | January 2021 to March 2023. Built Spark pipelines ingesting 800GB daily trade data for compliance reporting.
Security engineer with stacked internal title
Posting wants SOC tooling, ISO 27001, and cloud hardening for a regulated employer.
Before: Security Analyst listed twice under one date range with identical bullets copied from the junior stretch.
After: SecureBank Group, Edinburgh. Security Engineer | May 2021 to Present. Hardened AWS accounts for ISO 27001 audit; closed 47 critical findings in Q2 2024. Security Analyst | August 2018 to April 2021. Tuned SIEM rules that cut false positives 15% while maintaining alert coverage for cardholder data flows.
Copy-paste block: UK IT CV skeleton for Greenhouse
YOUR NAME
City, UK | phone | email | LinkedIn URL (plain text)
Experience
Employer Name, City UK
Job Title | Month Year to Present
• Posting keyword in first eight words + stack used (AWS, Kubernetes)
• Delivery outcome with a number from your actual sprint or release cycle
Earlier Title (via Agency Name, if contract) | Month Year to Month Year
• Scope bullet with metric
Education
Degree, University | Year
Certifications
CKA, Month Year (or AWS SAA, Month Year)
Skills
Optional comma list only for tools not already in Experience bullets
Export that skeleton from Word, not a design tool, when Greenhouse offers DOCX upload. If you're PDF-only, print to PDF from Word so the text layer stays selectable. Scanned exports fail before a human opens the file.
Spell employers the way the careers site and Companies House filings do. Recruiters notice when your CV says TechCo while the application auto-filled TechCo Ltd from an old parser read.
For date-format questions after you flatten layout, see month year vs year only on resume dates . UK contract roles need Month Year on every line the importer maps to tenure.
Mirror posting language in bullet one under your current job. Platform ownership belongs on the role that ran the service. Incident response language belongs on the employer that owned on-call. Skills-only lists do not carry that context in Greenhouse preview.
Keep section headings boring: Experience, Education, Certifications, Skills. Creative strings like Technical Journey or Core Stack sometimes map to the wrong field on older Greenhouse builds. Plain headings survive import and still read fine to humans.
Run a plain-text pass before export. Paste the Word file into Notepad or a blank text editor and read top to bottom once. That order is what Greenhouse approximates. If Terraform appears before your name, flatten again.
When a flat UK IT CV still fails the Greenhouse preview
Exceptions matter because engineers are told polished design signals seniority. Sometimes the fix is not more formatting. It's knowing which rules bend and which ones don't.
Certification without a date. Greenhouse and recruiters both need Month Year on CKA, AWS, or Azure lines. A badge with no date reads like a missing field. In progress belongs on the same plain line: CKA expected November 2026.
Mixed date formats on one page. March 2021 beside 03/21 beside 2021 tells the importer three different stories. Pick Month Year everywhere. Spell the month to avoid day-first confusion on UK reads.
Internal job titles HR never posted. Code Ninja or Cloud Wizard might be your team string. Mirror the posting title once in parentheses: Senior Engineer (Platform Lead). The parser needs a recognisable title line recruiters can search.
Acronyms without context. K8s and IaC in a Skills cloud mean nothing without the employer block. Write Kubernetes cluster migrations for four production namespaces in the bullet under the role that ran them.
White-font keyword rows or tiny footer skill strings. Recruiters flag the native PDF when they open it. Put each stack once beside the dated role where you used it. One honest line beats twelve hidden repeats.
Exception: some employers run an older Greenhouse build that strips PDF hyperlinks but keeps plain text. If your preview drops GitHub URLs, paste the URL as visible text once. Don't rely on blue underlined text alone.
Exception: if you applied through a job board that re-uploads your file, the board may compress formatting before Greenhouse sees it. When the preview looks wrong and your source DOCX is clean, re-apply on the company careers site with the same flat file.
This won't fix applying to roles where you lack must-have stack requirements. It stops a qualified engineer file from looking empty because the parser ate the dates while Skills still lists AWS.
Verify the import before the next Greenhouse submit
Upload your flattened DOCX and the posting to HireFlow's free ATS resume checker . You'll see whether Experience still carries distinct Month Year ranges and whether sprint bullets stayed out of table cells.
When the role is a stretch but your delivery history is strong, run score your job match after the layout pass. Parsing fixes visibility. They don't invent platform ownership the posting lists in bullet one.
Do this now: Flatten to one column, move stack proof to plain lines, fix Month Year dates, export DOCX, read the Greenhouse preview, then submit once.
What to do now
Greenhouse ATS resume optimization UK IT comes down to boring structure and honest dates. One column, Month Year strings, delivery bullets on plain lines, and cloud tools beside the job that used them. Read the preview before Submit.
- Strip tables, KPI boxes, and skill grids from the master file.
- Put posting keywords in bullet one under your current role.
- Split contract clients onto separate dated lines.
- Export DOCX from Word when the portal allows it.
- Run a free ATS check after export, not before you fix dates.
Open the posting you want most. Run a free ATS check , confirm the importer shows your latest title and contract dates, and send one clean upload.
Read more
Frequently asked questions
Sidebar skill grids and two-column layouts often parse before Experience. Greenhouse attaches AWS, Kubernetes, and Terraform to a phantom employer row while project bullets trapped in table cells import without Month Year dates. Flatten to one column, move cloud tools into the dated bullet that used them, and put every role on plain lines with start and end months spelled out.
DOCX from a single-column Word source is the safer default when the careers page allows it. Canva and design-tool PDFs hide tables that scramble employer order. If the req requires PDF, export from the same flat Word file and open the Greenhouse preview when offered. Scanned PDFs fail before a recruiter opens the attachment.
Two pages is fine when every line earns space. Page two should not repeat Skills from page one or bury your latest title under certifications. Keep Month Year on every contract stint and put the posting's must-have stack in bullet one on your current role. Greenhouse still parses linearly regardless of page count.
On plain Experience lines with the end client named, the agency in parentheses if relevant, and Month Year dates on each stint. A single block that says Various clients with no dates tells recruiters nothing and often imports as one employer with a ten-year blank range. Split each engagement onto its own dated row.
No. Recruiters flag hidden text when they open the native PDF. Put each posting keyword once in bullet one under the employer that used it. Parsing order and honest layout come first. Keyword tricks after a clean preview rarely change the outcome and can cost trust if someone opens the source file.