Greenhouse CV Parsing Fix for European IT Roles

By Peter Miller · Published March 24, 2026 · Last updated: September 15, 2026

11 min read · Fix parsing before you hit submit

Greenhouse CV parsing issues usually mean the file looks fine to you and empty or scrambled to the parser. You've exported a polished PDF from a European template. The portal accepts it. Then the preview shows your oldest internship first, your Skills block landed in Education, or the text field stays blank. That's not a mystery rejection. It's format.

Check your resume for free on the export you'll actually attach. Greenhouse sits behind many European scale-up and corporate career pages from Berlin to Dublin to Amsterdam. The fix path is the same whether you're applying in London or remote across the EU: text-select test, single-column Experience, DOCX fallback when PDFs scan as images.

You don't need a new template site. You need five concrete steps, two edge cases, and a copy-paste Experience block that won't scramble when tables collapse. Job searching's already slow. Don't lose a week wondering if they ghosted you when the upload never parsed.

If you're reading this after a failed upload, don't resubmit the same Canva PDF. Run step one below before you touch apply again. It takes two minutes and tells you whether you're fighting parsing or something else. You'll know in one pass if the file is text or a picture.

When the posting asks for a letter alongside the CV, generate a cover letter in plain text that names your current title once. Letter and CV should agree on scope after Greenhouse parses both fields.

What Greenhouse does when you upload a European IT CV

I've opened Greenhouse candidate profiles where the PDF attachment looked perfect and the parsed timeline showed a 2016 internship above a 2024 principal engineer role. Greenhouse ingests your file, extracts text, and maps blocks into its candidate record. European CVs built in design tools often arrive as images. Two-column layouts and Europass-style tables read columns out of order. Headers and footers sometimes repeat company names into every section.

The recruiter view depends on parsed order, not your PDF layout. When Experience imports with internships on top of senior roles, keyword scans miss your current title. When Skills dump without job context, you look junior even with fifteen years in the field.

European IT candidates face a specific trap: the CV looks professional because HR in your home market expects two columns, photo headers, and dense skills matrices. Greenhouse does not read magazine layout. It reads text stream order. A right-hand date column imports before the job title sitting in the left column. Your most recent role ends up buried under graduate placement lines.

Edge case: the employer enabled manual review only. Parsing still matters because sourcers search inside Greenhouse by job title strings. Edge case: you already applied with a broken file. Upload a corrected DOCX on a fresh application if the portal allows reapply. Do not assume the first broken parse fixed itself.

Read avoiding common ATS errors in Greenhouse when you also apply through UK portals. The single-column rule travels across systems even when the vendor stays the same.

Five steps to optimise your CV for Greenhouse ATS in European IT roles

Work in order. Each step ends with a pass/fail check so you know whether to continue or stop and rebuild the file.

Step 1: Run the upload text test

Open your PDF in a desktop reader. Select all text. Paste into Notepad or TextEdit plain mode.
Before: Paste shows empty box or random symbols. Greenhouse will see the same blank field.
After: Paste shows employer names, titles, and dates in reading order. Parser has raw text to work with.
Fail here? Rebuild in Word or Google Docs. Export DOCX first, then PDF from that DOCX if you still want PDF.

Step 2: Collapse two-column and table layouts

Before: Dates sit in a right table column. Skills live in a coloured sidebar. Greenhouse reads dates before titles.
After: Each role is four lines: Title | Employer | City or Remote | Month Year to Month Year. Bullets sit directly under that block.
Remove text boxes, icons, and chart graphics. Multinational recruiters expect linear Experience, not magazine layout.

Step 3: Standardise Month Year dates

Mixed formats scramble sort order. 03/2024, March 2024, and 2024 alone in the same file make current role detection unreliable.
Pick Month Year everywhere: March 2021 to Present. Put dates on the same line as employer or directly under title. Never isolate dates in a footer row.
Edge case: concurrent contract roles. List both with honest overlapping ranges instead of stacking in one table cell.

European candidates often keep a local date style from an old CV. Convert DD/MM/YYYY style to March 2024 before upload. Slashes and dots confuse parsers that expect spelled months. If you relocated recently, keep city and country on the employer line so remote roles do not import as blank location fields.

Step 4: Export DOCX and test upload preview

Save Firstname-Lastname-CV.docx from Word or Download as DOCX from Google Docs. Upload to Greenhouse on the employer's apply page without submitting yet.
Scroll the parsed preview. Current job should appear first. Education should not contain Skills keywords.
If DOCX parses clean and PDF does not, submit DOCX. Keep the PDF for email attachments only when humans request it.

Watch file size caps. Greenhouse employers sometimes set a 5 MB limit. Compress images inside the CV or remove them entirely. A headshot in the header can push a two-page file over the limit and fail silently. Plain text CVs rarely hit the cap unless you embedded high-resolution graphics.

Edge case: mobile upload from Google Drive preview. Download the file to your phone storage first, then attach. Streaming previews occasionally send a link wrapper instead of the document bytes. Edge case: browser autofill overwriting parsed fields after upload. Re-read the preview after autofill runs. Correct job title manually if the browser inserted an old title from a saved form.

Step 5: Align CV bullets with posting keywords once

Parsing fixes get you into search. Bullet one under current role still carries the match. Highlight three must-haves from the posting. Rewrite bullet one so one must-have lands in the first eight words.
Do not stuff a keyword block at the bottom. Greenhouse may file it as Skills without job proof.
Copy-paste Experience skeleton after you fix layout:

[Job Title from posting] | [Employer] | [City, Country or Remote] | [Month Year] to [Month Year or Present]
• [Outcome with number and year tied to posting must-have].
• [Tool or method from posting used on this job].
• [Scope line: team size, systems owned, or territory].
Repeat newest role first. No tables. No sidebar.
            

For deeper bullet work on European IT roles, read US vs UK CV format differences before you add metrics Greenhouse might strip from garbled lines.

What breaks most often in Greenhouse uploads

Canva and slide-deck PDFs. They look sharp and parse as images. Rebuild in a word processor.
Hyperlink-heavy contact lines. Linked URLs sometimes import as separate paragraphs above your name. Use plain email and phone on line one.
Graphics for Skills. Star ratings and progress bars do not become searchable text. Spell skills in a simple list or inside bullets.

Header repetition. Running headers with your name inject into every section break. Turn off headers except page one.
Multiple file uploads. Uploading CV plus portfolio PDF when only one field exists can attach the wrong file as primary. Read the label.
Password-protected PDFs. Greenhouse cannot open them. Remove protection before upload.

Section labels as graphics. EXPERIENCE spelled in a text box does not always map to Experience. Type section headers as plain bold text in the body.
Bullet icons from special fonts. Custom wingding bullets paste as odd characters. Use standard round bullets from Word.
Compressed PDF from online tools. Some compressors rasterize text. Re-export uncompressed from the source DOCX.

Before: Europass-style two-column CV with photo header and skills matrix in a left sidebar. Greenhouse imports 2017 internship dates above 2024 senior architect title.
After: Single-column DOCX with Month Year dates, current role first, skills spelled inside delivery bullets under each employer.

Before: PDF exported from LinkedIn profile download with sparse Experience and duplicated headline text in the body.
After: Purpose-built CV file with full tenure, four-line role blocks, and no duplicated profile summary above Experience.

Edge case: academic CV uploaded to a corporate IT req. Drop publications to an addendum PDF if allowed. Keep Experience to roles relevant to the posting.
Edge case: multilingual CV with mixed language section headers. Pick English section labels for multinational employers unless the posting specifies otherwise.
This won't fix applying when you lack must-have years. It stops qualified European IT candidates from looking entry-level because Experience order inverted on upload.

Parse-check before you hit apply on Greenhouse

Paste the job description into the free ATS resume checker with your DOCX export attached. Low continuity scores usually mean date or column fixes, not more keywords in Skills.

Need a clean single-column base file? Build your resume and download DOCX before you test the Greenhouse preview. Same structure, fewer layout surprises.

Upload once with a parser-proof CV

Greenhouse CV parsing issues clear when you treat the portal like a text importer, not a design showcase. Run the paste test, flatten columns, standardise Month Year dates, and fall back to DOCX when PDF previews scramble Experience order.

Open your last export tonight. If Notepad stays empty, rebuild before you apply again. If preview shows old roles on top, fix order in DOCX and re-upload. One clean file beats three retries with the same image PDF.

Save the working DOCX as your master apply file for every Greenhouse employer this month. Tailor bullet one per posting, not the whole layout. Parsing fixes are one-time work. Keyword tweaks are per req. Mixing the two is how candidates burn hours redesigning a file that already failed the upload text test on step one.

When a colleague asks why Greenhouse ate their CV, send them the text test first. Most Greenhouse parsing errors disappear before step three once the PDF is actually text, Experience is one column, and Month Year dates sort correctly.

Before your next batch of applications, check your resume for free against the posting so bullet one and the parsed Experience block tell the same story.