12 min read
Your UK IT CV looks clean in Preview. Greenhouse shows Terraform and AWS under Skills while Experience lists one employer from 2019. That gap is layout, not missing cloud keywords. Two-column templates, numeric date strings, and cert lines split from job blocks scramble what parsers extract. You didn't fail the technical screen. The file never imported your platform proof in order, and it's not because you're underqualified.
You don't need a new career story. You need a single-column export with Month Year dates and certs sitting inline with the roles that earned them. If you've been tweaking keywords without checking the upload preview, stop. Before you rewrite bullets for the next DevOps posting, check your resume for free and confirm employer names, titles, and date ranges landed in Experience, not only in a sidebar Skills block.
Job searching when qualified cloud files vanish in the portal is exhausting. This page maps upload symptoms, three parsing causes UK IT CVs hit in Greenhouse, how to tell which one's yours, and the fix for each. You won't fix a parser problem with more buzzwords. Structure first. Tailoring second.
When the posting asks for a cover letter after upload, don't paste from a column the parser skipped. We'll keep the letter short once your dates are mapped. Generate a cover letter that cites one dated bullet you verified imported under the right employer.
Quick Wins
- Rebuild in one column. Move Skills below dated Experience blocks.
- Write March 2021 to June 2024 on the same line as each job title.
- Put AWS and CKA cert lines directly under the role where you used them.
- Paste-test into Notepad before re-uploading to Greenhouse preview.
Symptoms: when Greenhouse sees a different CV than you do
The PDF on your desk lists three platform roles with pipeline bullets and cert lines. The Greenhouse preview shows Jenkins and Docker in Skills, a garbled employer name, and a site reliability engineer title paired with dates from the wrong contract. Keyword match fires on sidebar tools while your Kubernetes migration bullets never attached to the company that paid you.
Paste-test scramble is the fastest symptom check. Export your CV, select all, copy into Notepad. If cert acronyms appear before your name, or job titles sit three lines away from their Month Year ranges, layout is reordering text. Humans read the visual column. Greenhouse reads extraction order.
Other signals: screening questions ask for years of cloud experience and the number feels low because an early contract dropped off page two of a merged column. Recruiters open your PDF and it reads fine while their system profile shows half-empty Experience. I've screened stacks of UK IT uploads in Greenhouse where the Canva template looked sharp and the parser never mapped DevOps proof to dates.
UK CVs often run two pages with a photo column or skills rail on the left. US parsers treat that rail as the first text block. Tools land in Skills without tenure. Experience imports empty or out of order. For how UK layout differs from US uploads, read US vs UK CV formats: key differences . This page is the Greenhouse parse layer for IT roles.
The parser expects a linear spine: contact, optional Summary, Experience with employer plus Month Year on each role, Education, Certifications inline or grouped, Skills last. Anything that splits that spine across columns or table cells breaks import before a recruiter opens the queue.
Greenhouse ATS UK IT CV parsing: three failures cloud and DevOps roles hit
Scrambled Greenhouse imports usually trace to one of three layout patterns. Most UK IT files show a primary cause plus a secondary one. Fix structure before you tune Terraform keywords. The pairs below use composite roles only. Swap in your employers and stack.
Cause 1: Two-column layout (Skills or certs left, Experience right)
Symptom: Skills and cert blocks populate in the portal. Experience is empty, duplicated, or missing your most recent platform contract. Paste-test shows AWS, Terraform, and Python before your first job title.
Why it breaks: parsers often read down the left column completely, then the right. Your sidebar cloud stack and CKA line export ahead of employer names. Greenhouse maps that first text block to Skills and never pairs pipeline bullets with Month Year dates on the right.
Before: two-column UK IT template with AWS, Azure, and Kubernetes in a narrow left rail; platform engineer roles in the wide right column.
After: single column: name and contact, three-line Summary, Experience with each employer line, Education, Certifications with Month Year earned, Skills as a vertical list at the bottom.
Before: site reliability engineer CV where Greenhouse preview lists Prometheus, Grafana, and Helm but shows one employer from 2018.
After: same tools listed once under Skills after four dated employer blocks; Terraform named inside a March 2023 bullet about EKS cluster migration.
Fix: rebuild in Word or Google Docs with one column width. Move sidebar stack into dated bullets or a Skills block after Experience. Export PDF from that source, not from the design template. Read why columns and tables kill resume accuracy when paste-test still scrambles after a first pass.
Cause 2: Non-Month Year dates and split title lines
Symptom: dates attach to the wrong company, contract tenure looks short, or Greenhouse shows 2021 beside a 2024 job title. UK candidates often write 03/2021 to 09/2024 or list years only.
Why it breaks: numeric date strings and year-only ranges do not map cleanly to Experience fields. Parsers concatenate odd tokens. A title on one line and March 2021 to June 2024 on the next may pair with the following employer. Cloud roles with six-month contracts look like gaps when end dates misattach.
Before: Platform Engineer on line one; 03/2021 to 09/2024 on line two; employer name on line three.
After: Platform Engineer, FinTech Ltd · March 2021 to September 2024 on one line, bullets below, blank line, next employer.
Before: DevOps contractor CV with 2019, 2021, and 2024 as year-only markers beside client names in a table.
After: each client as a heading with Month Year range on the same line: Cloud Engineer (contract), Retail Bank · January 2024 to present.
Fix: spell out months. Keep title, company, and Month Year range on one line per role. For the tradeoff on year-only dates, see Month Year vs year-only on resume dates . Cloud hiring managers count platform tenure from parsed ranges, not from bullets alone.
Cause 3: Cert lines and skill grids separated from Experience
Symptom: AWS Solutions Architect and CKA appear in Skills or a cert table while the roles that used them show generic bullets. Screening questions about cloud years pass on tools but fail on mapped employers.
Why it breaks: cert tables and three-column skill grids read as undated keyword dumps. Greenhouse keyword match sees Terraform without a contract date. Inline cert lines under the employer block tie credential to tenure. A footer grid on page two injects tokens that confuse field mapping.
Before: Certifications table with AWS SAA, CKA, and AZ-104 in separate cells above Experience.
After: AWS Solutions Architect Associate, earned June 2023 on the line below Platform Engineer, SaaS Co · March 2021 to September 2024; CKA listed under the Kubernetes-heavy contract.
Before: cloud engineer CV with a skill matrix rating Docker, Jenkins, and Ansible in star-filled table cells.
After: plain comma list under Skills after Education; Docker and Jenkins named inside CI/CD bullets with pipeline scope and Month Year dates on the role line.
Fix: delete skill grids and cert tables. Write cert lines inline under the relevant employer or in one Certifications block with earned Month Year. Name tools inside bullets that prove you used them on paid contracts, not only in a sidebar.
How to tell which cause is yours
Run the Notepad paste test. If cloud tools and cert acronyms appear before your first employer, cause 1 is primary. If dates and titles sit on separate lines that do not pair correctly, cause 2 is primary. If certs and skill grids sit above Experience with no dates, cause 3 is primary.
Then open Greenhouse preview on re-upload. Experience should list employers in reverse chronological order with bullets nested under each block. If preview still fails after a single-column rebuild, check for text boxes, icons, and pipe-heavy bullet lines that split across cells. Those add a fourth layer, but columns, dates, and cert placement are the usual root for UK IT files.
Copy-paste block: single-column UK IT CV spine
[Name]
[City, UK] · [phone] · [email] · [LinkedIn URL plain text]
SUMMARY (optional, 3 lines max)
Platform engineer with 6 years across AWS and Kubernetes in regulated fintech.
EXPERIENCE
Platform Engineer, FinTech Ltd · March 2021 to September 2024
• Migrated 14 microservices to EKS; cut deploy time from 45 to 12 minutes via GitLab CI
• Built Terraform modules for VPC and IAM; passed SOC 2 audit with zero infra findings
AWS Solutions Architect Associate, earned June 2023
DevOps Engineer (contract), Retail Bank · January 2024 to present
• Owned Jenkins pipelines for 8 teams; reduced failed builds 22% in Q1
EDUCATION
BSc Computer Science, University of Manchester · July 2018
CERTIFICATIONS (optional if not inline above)
CKA · March 2023
SKILLS
AWS, Terraform, Kubernetes, GitLab CI, Python (list once; also named in bullets)
Before and after: cloud engineer two-column template
Before: colourful two-column CV with AWS and Azure badges in a left icon column; contract history in a table on page two.
After: plain single-column PDF for Greenhouse uploads; badges removed; contract work as dated lines with pipeline bullets, no table grid.
Before and after: DevOps CV with pipe-heavy bullets
Before: bullet reads Built CI/CD: Jenkins | Docker | Ansible | K8s with pipes splitting tokens across parse cells.
After: Built GitLab CI/CD for 8 repos using Docker and Ansible; deployed to Kubernetes clusters on AWS EKS with zero-downtime rollouts.
Edge case: IR35 contract roles listed as one consulting block. Split each client into its own employer line with contract Month Year ranges. Recruiters cannot count platform tenure when five clients sit under a single heading with no dates.
Edge case: UK CV with photo column. Strip photo for Greenhouse uploads; photos sit inside table cells and push Experience text out of order. Keep a photo version for human networking if local custom expects it.
For Greenhouse-specific tailoring after layout fixes, read how to tailor resume for Greenhouse applications . Same rules apply when the posting is UK-based but the portal is Greenhouse.
Patterns that keep UK IT CVs broken in Greenhouse
Flattening columns fixes most cloud files. These add-ons keep Greenhouse ATS UK IT CV parsing accuracy low even after you remove the obvious grid.
Skill bars and star ratings in table cells. Icons become empty cells or garbage characters. Replace with a comma list or plain bullets.
Header/footer contact tables. Email and phone trapped in a header object parse as body text and duplicate across pages. Type contact lines once at the top as plain text.
Multiple tiny tables per contract. Four two-row grids read as four disconnected fragments. One employer block per role parses cleaner than four micro-grids.
Exporting from design PDF without editing source. Flattening in Acrobat does not restore reading order. Rebuild text in Word or Docs, then export a fresh PDF.
Tweaking cloud keywords before layout. Adding Kubernetes twelve times in a sidebar table does not help if Experience never imported. Structure first, tailoring second.
Before: every bullet starts with Responsible for across three platform roles.
After: each bullet opens with a different verb from the posting: migrated, automated, documented, scaled, owned.
This will not fix applying to principal engineer roles when your parsed tenure shows two years. It stops qualified platform engineers from losing because Greenhouse paired a 2023 title with a 2020 end date.
Test the flattened CV
After you rebuild single column with Month Year dates and inline certs, upload the same posting to HireFlow's free ATS resume checker and confirm Experience blocks show employers with date ranges before Skills. You are validating parse order, not chasing a keyword score on a broken spine.
Then run score your job match on the same pair. You are checking whether Terraform and Kubernetes appear under dated contracts, not only in a cert table the parser treated as undated Skills.
Do this now: Paste-test your current CV, flatten one column, write Month Year on each title line, re-upload to Greenhouse preview, then tailor bullets on the version that parsed.
Fix parsing before you tailor
Greenhouse ATS UK IT CV parsing fails when parsers read file order, not design intent. Fix the spine: one column, employer lines with Month Year on the title row, cert lines inline with the roles that earned them, Skills after proof. Tailoring scrambled text only rearranges words the system already misfiled.
Paste-test tonight. Match your symptom to cause one, two, or three. Re-upload once and read the Greenhouse preview. When Experience lists platform contracts in order, then mirror posting language inside dated bullets.
Save a master single-column CV and a tailored copy per req. Cloud candidates who stop fighting sidebar templates move faster than those who keep adding AWS keywords to a layout Greenhouse never mapped correctly.
- Flatten to one column before any keyword work.
- Write Month Year on the same line as title and company.
- Place cert lines under the contract that used them.
- Replace skill grids with comma lists and bullet proof.
- Read Greenhouse preview before screening questions.
Open the DevOps or platform posting you are targeting. Run a free ATS check on the flattened export and confirm employers and dates imported before you submit again.
Read more
Frequently asked questions
Upload what the posting allows. A plain single-column DOCX exported from Word or Google Docs often maps cleaner when your PDF came from a design template. If the form requires PDF only, rebuild layout in Word first, then export a text-based PDF. Scanned image PDFs fail regardless of format. Run the Notepad paste test on whichever file you submit.
Numeric month/year strings confuse parsers that expect spelled-out months. Write March 2021 to September 2024 on the same line as the job title, not 03/21 or 2021 only. Year-only ranges make tenure math look short for cloud roles that expect five-plus years across platforms. Month Year on the title row keeps employer blocks paired.
Inline on one line under the employer block where you used the skills, or in a Certifications subsection with Month Year earned. Do not trap certs in a sidebar table or icon grid. Greenhouse often maps sidebar text to Skills without dates while Experience stays empty. Example: AWS Solutions Architect Associate, earned June 2023 on the line below your platform engineer role.
The parser grabbed a two-column Skills rail or a header skill table before Experience body text. Terraform, Docker, and Jenkins landed in Skills while employer names never paired with bullets. Flatten to one column, move tools into dated bullets, and re-upload. Preview should list employers in reverse chronological order before you answer screening questions.
Not until layout parses. Adding Kubernetes twelve times in a sidebar table does not help if your platform engineer role never imported with March 2022 dates attached. Fix single-column structure and Month Year lines first, then mirror posting language inside bullets that already sit under the right employer.