11 min read
You're not failing keyword games. Your file order is wrong. Most senior platform and security CVs in Greenhouse still list AWS, Kubernetes, and Terraform in a left column that parses before the employer block.
Check your resume for free before you reformat. If employer names already land in the wrong fields, you'll need a layout pass first. Tailoring bullet verbs on a scrambled file won't put your Staff Engineer title back on the right company.
Below you'll get why the parser misreads UK IT layouts, exceptions that still work, fixes you can run tonight, and a header block you can paste. Job searching at senior level is draining enough without a silent import error, and you shouldn't have to guess whether Greenhouse read your plc name correctly.
This won't fix applying to roles you're not qualified for. It stops a qualified file from dying in the parser before a recruiter search can find your last three employers.
You'll know you're in trouble when preview search inside Greenhouse can't find a company name you typed in bold on page one. That means the text never imported, not that recruiters ignored you.
Contract and permanent senior IT CVs fail the same way. IR35 inside labels still need a vertical stack per engagement, not a client table with three columns.
Don't rebuild from a Canva export if you're on a deadline. Open Word, paste plain text, and reapply headings manually. It's slower and it's the only way you'll know the parser order.
Recruiters won't fight the parser for you. They search employer strings and move on when the field is blank. That's why layout beats polish for senior IT uploads.
Quick Wins
- Delete sidebar skills columns and move tools into experience bullets.
- Stack employer name, job title, and dates on consecutive lines per role.
- Paste all copy into Notepad and read employer-title order aloud.
Why Greenhouse scrambles senior IT CVs
Greenhouse does not read your CV like a hiring manager scanning a two-page delivery history. 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 Terraform and Ansible on the left while your Platform Engineer role sits on the right, the tools can parse as your most recent job.
UK senior IT CVs invite that failure. You have regulated client names, MSP suffixes, and holding-company structures that already look like two employers on one line. Add a metrics table for uptime, cost, and team size and the parser treats row labels as job titles.
A composite staff engineer still uploads a file where a fintech client name sits in a table cell left of the bullet about PCI scope. Greenhouse pairs the client name with whatever text sits below the table, not beside it. The human recruiter opens a profile where the last three roles look swapped.
This is not a keyword problem. Your file can mention Kubernetes twelve times and still show the wrong employer on role two. Layout and field order come first. Until those pairings are clean, tailoring will not make the recruiter see your actual last three roles.
Preview panes in the application form lie sometimes. They render your PDF nicely while the backend store holds scrambled fields. Trust paste tests and field search, not only the thumbnail.
Architecture diagrams embedded as images add zero parseable text. Move stack names into bullets under the role where you built the system. Recruiters search words, not PNG layers.
Multi-country remote roles still need one date format per file. Mixing US month-first on role one and UK month-year on role two splits dates into wrong fields on import.
UK conventions that still work in Greenhouse
You do not need a US-style one-page resume. Two pages is normal for a Staff Engineer or head of platform. Page count does not break parsing.
Month-year dates like Mar 2019 to Present parse fine when they sit on the same line as the job title or directly under it. 2019 to Present without months is also acceptable if every role uses the same pattern.
Pound or dollar amounts inside bullets are fine: Reduced cloud spend £840K annually after EKS rightsizing in FY24. The symbol is not the issue. A standalone KPI table with five years of spend is.
Certifications belong on the CV. They just should not share a table row with your phone number and email. One line under your name works: Alex Chen, AWS SA Pro, CKA.
And you can keep a short Profile section. Call it Profile or Professional Summary, not Career Narrative or Value Proposition. Greenhouse looks for familiar headers before it dumps text into an unlabeled blob.
Edge case: multiple short contract roles inside one year. Label each stack clearly: Contract Platform Engineer · Retail Bank Client via [MSP] · Jan to Jun 2025. One vertical block per engagement beats nested tables.
Edge case: cleared or regulated work you cannot name. Use Employer · Sector descriptor · dates, then bullets with scope language your clearance officer already approved. Do not leave a blank employer cell that collapses two roles together.
Edge case: you're returning from a career break. Keep one continuous Profile sentence, then stack roles vertically. Gap explanations belong in Profile text, not in a timeline graphic.
Edge case: dual UK and EU offices on one CV. Pick one address line for applications to London reqs. Two address blocks in a header table often parse as two names.
Greenhouse ATS parsing errors UK senior IT CVs: fix order tonight
Work top to bottom. Skip a step and you'll tailor keywords on a file that still pairs titles with the wrong plc.
Step 1: Paste into plain text and read the damage
Open your CV in Word. Select all, copy, paste into Notepad. If employer names and job titles alternate in the wrong order, Greenhouse will see the same chaos.
I've rejected senior IT profiles in Greenhouse when role two showed a skills rail as the employer because the sidebar parsed first. Fix the column layout before you argue about keyword match.
Step 2: Collapse to one column
Remove sidebar columns, text boxes, and floating architecture diagrams. Drag every bullet into the main body. If you lose visual polish, that is the trade for a parseable file.
Step 3: Standardise section headers
Use Contact, Profile, Work Experience, Education, Certifications, Skills. Greenhouse maps those labels reliably. Creative headers like Technical Journey land in unlabeled fields.
Copy-paste UK senior IT CV header block
Copy-paste block: plain header stack
[Your Name], CKA (or AWS SA Pro / Security+ as earned)
[City], United Kingdom · [phone] · [email]
Profile
Work Experience
Education
Certifications
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, no tabs aligning dates to the right margin.
Before: Two-column template with skills rail: Kubernetes, Terraform, Python, AWS, GCP.
After: Single column. Skills section at the bottom with one tool per line, or tools named inside bullets under each role.
Before: Staff Platform Engineer | Global Retail Group (table cell) | 2019 to Present
After: Global Retail Group plc · Staff Platform Engineer · Mar 2019 to Present · stacked on three plain lines.
Before/after: security engineer
Before: Responsible for application security, pen tests, and SOC liaison across multiple products.
After: Cut critical findings 40% in Q3 by shifting SAST left in GitLab CI for 12 microservices; led tabletop exercises with SOC vendor.
Before/after: SRE lead
Before: Managed on-call rotation and incident response for high-traffic services.
After: Drove MTTR from 47 minutes to 19 minutes over FY24 by runbook automation in PagerDuty and Grafana on-call for payments API.
Before/after: data platform engineer
Before: Built data pipelines and supported analytics teams with warehouse tooling.
After: Migrated 18 TB nightly batch to Spark on EMR; held SLA at 99.2% ingest success across 6 source systems in 2025.
Where senior IT layouts break in the parser
Design-template CVs from online builders. Two-column templates look board-ready and parse terribly. Recruiters never see the polish if the employer field is empty.
Listing every system in a skills rail. Kubernetes, Terraform, and Python belong in the bullets where you used them, not in a left column that reads first.
Right-aligned dates in a table. Tabs and table cells split dates from titles. Put dates on the same line as the title or directly below it.
Embedding logos for employers or vendors. Cloud provider logos are image layers. They add no parseable text.
Renaming Work Experience to Technical Journey. Greenhouse may still show the text, but field mapping gets worse and auto-fill on the application form breaks.
Uploading a profile PDF export unchanged. That export uses odd section breaks. Rebuild in Word with the header block above, then export fresh.
Step 5: Export and test
Save as 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.
For broader parser behaviour, read why ATS filters out most applicants . For file-type choices, see how resume file type impacts screening .
Tools after you fix layout
Run the rebuilt DOCX through the ATS resume checker once. Confirm each employer name still pairs with the right title after you moved bullets out of tables.
When you are tailoring for one role, score your job match on the posting, then rewrite the first bullet under your current title to name one required skill. Layout first, keywords second.
Optional cover letter boxes in Greenhouse reward one tight paragraph, not a second CV. Use the cover letter generator for structure, then cite one proof point that matches bullet one on your cleaned file.
Keep a changelog row in your job tracker: file version, upload date, and whether preview search found your current employer. You'll stop re-uploading the same broken PDF to five reqs.
When a posting asks for a cover letter and a CV, fix the CV first. A sharp paragraph cannot repair employer-title swaps in the attachment.
Do this now: Paste test, single column, one live req upload before you close the laptop.
Your next upload
Open your current CV in Word. Paste into plain text. If the employer names and titles are out of order, rebuild as a single column before you tailor anything for the next platform or security role.
Greenhouse ATS parsing errors UK senior IT CVs come down to file order, not flair. Boring and vertical beats polished and scrambled every time a recruiter opens your Greenhouse profile.
Save DOCX. Export PDF from the same file. Upload one live req before you close the laptop. One clean parse beats a dozen keyword passes on a broken template. Then stop tweaking for the night.
When preview search finds your current employer on the first try, you're ready to tailor bullet one for the posting. Until then, keep fixing layout, not adjectives.
Staff engineers sometimes keep a portfolio site link in the header. Plain text URL on its own line is fine. Icon buttons and QR codes are not.
If you're between contract and permanent offers, maintain two master files rather than one hybrid that mixes IR35 labels with employee titles in one table.
Greenhouse ATS parsing errors UK senior IT CVs rarely need a third page. If you're on three pages, cut duplicate skills before you add another formatting trick.
Build your resume from a single-column template if your design file fights you on every export. Starting clean beats fighting a two-column builder for another hour.
Read more
Frequently asked questions
Upload what the posting lists first. When both are accepted, a plain DOCX exported from Word with a single column usually keeps employer blocks and Month Year dates on one line on first import. Design PDFs from Canva or InDesign often scramble order even when the preview looks fine. Run a Notepad paste test on the exact file you submit, not on a screenshot.
The parser reads top to bottom and pairs each title with the next employer line it finds. Sidebars, text boxes, and table cells reorder that sequence. Stack employer, title, dates, and bullets in one vertical column per role. Skills listed in a left rail often parse as your most recent job title.
Length is fine when structure stays boring. Two pages with single-column Experience and consistent Month Year dates usually concatenate cleanly. Risk comes from tables, text boxes, and skill sidebars, not from page count alone. Keep page two under the same Experience heading string.
No. A skills sidebar often parses before your experience block, so Greenhouse thinks your top role is a list of tools. Put Kubernetes, Terraform, and Python in bullet one under the employer where you used them. Keyword density in a table cell does not rank under the right job row when the table breaks.