11 min read
You've exported a sharp graduate CV and uploaded it to a UK tech req on Greenhouse. The preview shows your skills rail as your current employer and your placement at a fintech under Education with no bullets. You're not imagining it. The parser read your layout in an order you didn't intend.
Before you rewrite every bullet for keywords, check your resume for free with the posting pasted in. You're confirming whether employer names and placement dates imported, not chasing a perfect score. A Greenhouse ATS UK entry-level IT CV that parses cleanly is boring on purpose: one column, standard headings, Month Year on every role.
Job hunting right after uni is draining enough. This page won't debate whether ATS is fair. It shows what parse-safe graduate files look like, before/after pairs across IT roles, what broken uploads share, and a copy-paste block you can use tonight.
And when the portal asks for a cover letter after upload, don't paste lines that repeat the same scrambled order. Generate a cover letter from the corrected CV text so the note matches the employer lines you fixed in Word.
Quick Wins
- Flatten two-column graduate templates to one column before export.
- Move phone and email out of headers into the body under your name.
- Label sections Experience, Education, Skills. Not My Journey.
- Month Year on placement, internship, and part-time bar work lines.
The bar fixing parsing issues in Greenhouse ATS expects from UK IT CVs
Greenhouse is not a PDF viewer. It extracts text into profile fields recruiters scan in list view. Fonts and accent colours disappearing is normal. Your placement employer pairing with your degree title is not.
The standard your file is judged against: plain-text export reads top to bottom the way a recruiter would skim: name and contact, optional one-line summary, Experience with Month Year dates, Education, then Skills. Each employer line stays attached to its job title and bullets.
A composite computer science graduate whose left-rail skills list parses first looks like their top job is Python, Git, and Docker. The real placement at a payments startup drops to row four. Same person, same modules. Different screen because layout drove parse order.
UK graduate CVs often carry a photo, a skills sidebar, and creative section titles from university careers templates. Greenhouse reads those the same way it reads US two-column resumes: left column or top box first, body second. I've passed on strong juniors when the preview showed an empty Experience block and a wall of tools with no employer attached.
Read how resume file type impacts screening when PDF and DOCX behave differently on the same layout. Format the column structure first, then argue about file type.
Naming Greenhouse is allowed. Claiming how it ranks candidates is not. This teardown sticks to what you can observe: preview order, field mapping, and plain-text paste. Fix those and you stop losing screens to layout while your placement bullets never reach a human.
Graduate CVs in the UK often run two pages with module lists on page two. That is fine when page two is plain text. It fails when page two reintroduces a two-column skills grid or a photo header that restarts parse order. Scroll the entire document before export, not only page one.
Edge case: applicants with both freelance GitHub work and a sandwich placement should list the paid placement first under Experience. Freelance can sit second with Month Year dates. Parsers and humans both weight employer lines above project boxes.
If your careers service insists on a personal statement paragraph, keep it to two lines under the contact block and repeat none of the tools already in bullet one. Duplicated stacks waste the only space recruiters read before they decide to scroll.
Before/after pairs across UK entry-level IT roles
Each pair is a layout choice, what Greenhouse tends to do with it, and the export fix. Swap in your employers and modules. Illustrative titles only.
Pair 1: Computer science graduate with Canva sidebar
Before: Left column: Technical Skills, Certifications, Languages. Right column: Education and one placement paragraph. Purple accent bars.
After: Single column, 11-point Calibri. Placement gets its own Experience line: Software Engineering Placement, PayFlow Ltd, Leeds | September 2024 to June 2025. Skills appear inside bullets, not a rail.
Pair 2: IT support apprentice with skills table
Before: Three-column Word table: Hardware | Software | Soft Skills with twenty cells above Experience.
After: IT Support Apprentice, Regional Council, Birmingham | September 2023 to August 2024. Bullet one: Resolved 40+ tier-one tickets weekly in ServiceNow; imaged Windows 11 laptops for 120 staff across three sites.
Pair 3: Data graduate with projects in a text box
Before: Shaded text box titled Uni Projects floating beside the name with three capstone lines and no dates.
After: Projects subsection under Education with Month Year: Customer churn model in Python and scikit-learn, dissertation | October 2024 to April 2025. Tools named in the same line as the outcome.
Pair 4: Cyber security graduate with badge graphics
Before: CompTIA Security+ and Cisco CCNA logos as embedded images in a two-column Certifications grid.
After: Certifications as plain text under Education: CompTIA Security+ (2025), Cisco CCNA (2025). No images. Credential name spells the same way as the job description.
Pair 5: DevOps placement student with GitHub in the footer
Before: github.com/handle on every page footer. Kubernetes and Terraform icons in a left margin.
After: github.com/handle on line three under email in the body. Kubernetes and Terraform inside the placement bullet with Month Year dates on the employer line.
Pair 6: Web developer bootcamp grad with creative headings
Before: Section titles: What I Build, My Stack, Where I've Been. Bootcamp projects listed with no employer.
After: Experience header. Freelance Web Developer, self-employed, Bristol | January 2025 to Present. Bullet: Delivered three client sites in React and TypeScript; largest build cut page load from 4.2s to 1.8s on Lighthouse.
Copy-paste block: Greenhouse-safe UK graduate CV header
Copy-paste block: single-column graduate layout
[Full Name] [City, UK] · [Phone] · [[email protected]] · github.com/[handle] [Optional one line: Junior software engineer with placement in payments APIs] Experience [Employer], [City] | [Job Title] | [Month Year] to [Month Year or Present] • [Verb] [scope] using [tool]; [outcome with number if you have one] Education [BSc Computer Science], [University] | [Month Year] to [Month Year] [Relevant modules or grade if worth listing] Skills [Comma-separated tools also named in bullets above]
Export PDF from this file only. Open the Greenhouse preview if the portal offers one. If employers still scramble, switch to DOCX upload from the same source.
See how to test your resume on Greenhouse before applying for the plain-text paste test that works on UK portals too.
What weak Greenhouse ATS UK entry-level IT CV uploads still share
Trusting the PDF because it looks fine on your screen. Recruiters may never open it. The parsed profile already buried your placement under Education.
Using the university careers template unchanged. Many include invisible tables and a photo block. Greenhouse still reads the grid.
Listing every module as a skill with no employer context. Agile, Scrum, and Jira in a sidebar do not replace a dated placement line.
Hiding short part-time retail work with year-only dates. Month Year on a six-month bar job reads honest. A fuzzy 2023 to 2024 band next to a placement invites gap questions.
Stuffing keywords into the sidebar after a failed upload. More text in the wrong column makes parse order worse. Flatten first, then tailor bullet one.
Uploading a scan of a printed CV from the careers fair. OCR guesses characters. Employer names and dates are the first casualties.
Edge case: EU candidates applying to London roles should still spell months in English for UK Greenhouse reqs. Write September 2024, not 09/24, when the employer is UK-based.
Edge case: sandwich-year students with overlapping uni and placement dates should show both with Month Year boundaries. Overlap is fine when it is real. Label placement clearly in the title line.
Before: BSc Computer Science 2022 to 2026 with placement paragraph embedded under the degree.
After: Software Engineering Placement, FinTech Ltd | September 2024 to June 2025 listed under Experience, then BSc Computer Science, University of Leeds | September 2022 to June 2026 under Education.
Leaving LinkedIn URL only in a QR code or image. QR blocks do not parse. Type linkedin.com/in/yourhandle on the contact line in plain text if you want recruiters to click through.
Mixing UK and US spelling in the same file. Pick UK spelling for UK reqs: organised, centre, programme. Mixed spelling rarely breaks parsers but signals carelessness on a graduate screen.
This will not fix applying to senior roles with a graduate CV. It stops a qualified junior from losing screens because Greenhouse thinks Docker is their employer.
Verify parse order before you hit submit
Run the export through HireFlow's free ATS resume checker with the job description pasted in. You're confirming employer-title pairing and whether your placement landed in Experience, not debating aesthetic preference.
When you're rebuilding from a sparse graduate file, build your resume in a single-column layout before you tailor for the posting. Parse order first. Keywords second.
Do this now: Flatten to one column, paste into Notepad, read employer order top to bottom, upload once, read the Greenhouse preview before Submit.
What to do now
Fixing parsing and formatting issues in Greenhouse ATS for UK entry-level IT CVs comes down to parse order, not bad luck. Flatten graduate templates, move contact into the body, kill floating boxes and badge images, and read a plain-text paste once before upload.
- Convert your two-column CV to single column tonight.
- Give placement and internship their own Month Year Experience lines.
- Replace creative section titles with Experience, Education, Skills.
- Run a plain-text paste before export.
- Confirm the Greenhouse preview matches your real history.
Open the next UK IT req on your list. Run a free ATS check , fix any scrambled employers, and submit one clean upload.
Read more
Frequently asked questions
Upload whichever format the posting accepts, then open the Greenhouse preview if the employer shows one. Text-based PDFs exported from a single-column Word file usually parse cleanly. Design-heavy PDFs from Canva or scanned exports often scramble employer order. If the preview drops your placement employer, try DOCX from the same flattened source before you reformat keywords.
No photo is required for UK corporate IT applications and photos can break parsing on some Greenhouse builds. Two-column layouts are common on UK graduate templates but Greenhouse often reads the left column first, so your Python and AWS lines can appear as your top job. Single-column plain text wins the parser even when a two-column PDF looks sharper to you.
List each project under a dated Education or Projects heading with Month Year boundaries, not inside a floating text box. Tie tools to a line a recruiter can search: Built inventory API in FastAPI during Code Academy capstone, September 2025 to November 2025. Avoid My Builds as a section title. Greenhouse maps standard labels to profile fields more reliably than creative headers.
Give the placement its own employer line with Month Year dates: Software Engineering Placement, FinTech Ltd, Manchester | September 2024 to June 2025. Do not bury the placement inside a degree block with 2022 to 2026 only. Recruiters calibrate graduate depth from placement length, and year-only bands make a nine-month placement look like a four-year job.
No. Layout fixes stop a qualified CV from dying because Greenhouse attached your React project to the wrong employer line. You still need relevant tools in bullets for the role you want. Flatten first, then tailor the first bullet under your placement or internship to the posting's stack.