11 min read
Your PDF looks sharp. Greenhouse shows half your employers. That's the gap Greenhouse ATS resume optimization closes for European mid-level IT CVs: layout order, not keyword stuffing. You're not losing on years or stack depth. You're losing when dates sit in table cells and Kubernetes lives in a sidebar the parser never attaches to your current role. Dublin, Berlin, and Amsterdam tech employers run Greenhouse on high-volume backend, platform, and QA reqs. The file they screen is the import preview, not your Canva export.
Before you rewrite bullets for the fifth time, check your resume for free with the posting pasted in. You'll see whether tools still sit in readable lines and whether your title line landed above the right employer block.
Job hunting across EU markets while you're on notice or relocating is already draining. You don't need a lecture on personal branding. You need a fix order that works on every Greenhouse form: flatten layout, align the title line, move tools into bullets. I've screened European IT files where the PDF was two pages and the imported profile showed one job and a skill cloud.
Country norms differ on photo, nationality, and page count. Parser rules don't. A single-column master file with Month Year dates serves UK, DACH, and Benelux uploads alike when the careers site runs Greenhouse.
Two pages is normal for mid-level IT in Europe when every line carries scope. Page count won't break Greenhouse. Tables, icon skill rows, and Europass blocks will. Build the boring file first, then tailor bullet one for each posting.
Quick Wins
- Strip tables and two-column templates before any keyword edits.
- Job title on its own line directly above employer name.
- Tools in bullet one under the role where you used them.
- Month Year dates on every role, same format throughout.
What Greenhouse does to a European mid-level IT CV
Greenhouse reads your file as a text stream and chunks it into employer, title, dates, and bullet fields. It does not recreate your design. A right-rail Skills section often imports between job blocks or drops entirely. Dates trapped in table cells can attach to the wrong company or show as blank ranges in the recruiter view.
The import preview is the CV recruiters screen. European candidates often build in Europass, Canva, or country-specific Word templates with photo blocks and language bars. Those look fine on screen. On import, bullet order scrambles and your latest title can land under a certification line.
Mid-level IT roles add another layer. You list twelve tools across four years. When those tools sit in a sidebar, Greenhouse cannot tell which stack belongs to which employer. Recruiters ctrl-f Kubernetes inside a job block. If it only appears in Skills, you look like you named it once without scope.
Photo and nationality lines are not parser poison by themselves when they sit in plain text at the top. Tables wrapping contact details are. Keep visa or work-authorization notes on one plain line under email. Do not put them inside a header table with icons.
US multinationals in Europe and local scale-ups both use Greenhouse on engineering reqs. The fix is not switching to a US resume myth. It is exporting a boring single-column file that survives the same importer whether the label says CV or resume.
Freelance and agency stretches confuse parsers when client names float without Month Year lines. Spell the payroll employer or agency on one line, then the client in parentheses if the posting would recognize that brand. Greenhouse needs a company string to attach bullets.
Certifications belong below Experience, not in the header beside your name. When AWS or Kubernetes certs sit in a sidebar, they can import as your current job title. Keep certs on plain lines after your last role block.
For how parsers match text after layout is clean, read how ATS matches resumes to job descriptions . Layout first. Matching language second.
Greenhouse ATS resume optimization: five steps for European IT CVs
Work in this order. Flattening after you keyword-stuff a table layout wastes an hour. Each step below includes a mid-level IT example you can mirror.
Step 1: Flatten layout to one column
Remove tables, text boxes, icon skill rows, and portfolio strips. Greenhouse reads top to bottom. Sidebars become floating skill clouds with no job anchor.
Before: Two-column Canva CV. Dates in a left table column. Python, Django, and PostgreSQL in a right-rail icon row.
After: Single column. Backend Developer | January 2021 to Present on one line under employer name. Bullet one names Python and Django on the payment API migration you owned.
Step 2: Align the title line above each employer
Put job title on its own line directly above company name. Do not bury title inside a table cell beside a logo. Greenhouse maps title to employer by proximity in the text stream.
Before: DevOps Engineer tucked in a header table with company logo. No clear employer string on the same line block.
After: DevOps Engineer on line one. CloudScale GmbH, Berlin on line two. March 2020 to Present on line three. Bullet one: Owned Kubernetes cluster for twelve microservices; cut deploy failures from nine per month to two in Q2 2024.
Step 3: Move tools into dated Experience bullets
Name stacks in bullet one under the role where scope was largest. Skills line is backup, not proof. Recruiters search inside job blocks before they read a summary paragraph.
Before: QA Automation Engineer role with Selenium and Cypress only in a Skills cloud. No tool names in bullets.
After: QA Automation Engineer | June 2019 to Present. Built Cypress regression suite for checkout flow; cut release defects 14% in H1 2025. Earlier role bullet names Selenium on the API test harness you maintained.
Step 4: Standardize Month Year dates
European CVs mix DD/MM/YYYY, 03/2021, and Present in one file. Pick Month Year everywhere. Greenhouse date parsers handle January 2021 to Present more reliably than split table cells.
Before: 15/03/2019 to 30/11/2021 in a table beside employer logo. Contract role with no month on end date.
After: Data Engineer | March 2019 to November 2021. FinTech client via agency name spelled as on contract. Bullet ties Spark and Airflow to the pipeline you ran in that window.
Step 5: Export, paste test, upload once
Save DOCX when the form allows it. Paste full text into Notepad on Windows or TextEdit plain mode on Mac. If employer order looks wrong there, Greenhouse will agree. Export PDF from Word only after the paste test passes.
Spell employers the way the careers site and contract paperwork do. Recruiters notice when your CV says SAP but Greenhouse auto-filled SAP SE from an old parser read.
Name the file with your surname and the word CV or resume to match the form label. That small detail helps recruiters when they download fifty attachments from one req. Inside the file, keep section headings as plain text: Experience, Education, Skills. Avoid decorative section bars that split the text stream.
After upload, open any preview Greenhouse exposes on the employer careers site. Count employers in preview versus your source file. One missing block means a table row or text box still survived your flatten pass. Fix and replace the file once.
Copy-paste block: European IT CV skeleton for Greenhouse
YOUR NAME
City, Country | phone | email
Work authorization: [EU citizen / Blue Card / sponsorship needed]
Languages: English (fluent), [local language level]
Profile
Two lines max. One posting keyword in sentence one.
Experience
Employer Name (legal spelling), City
Job Title | Month Year to Present
• Posting keyword in first eight words + stack + outcome with number
• Second bullet with tool tied to same role
Earlier Title | Month Year to Month Year
• Bullet with metric
Education
Degree, University | Year
Certifications
AWS Solutions Architect, etc. with year
Skills
Plain comma list only if tools are not already in Experience
For file-type choice after layout is flat, see PDF vs Word resume for ATS . The same export rule applies to European Greenhouse uploads whether the form label says CV or resume.
When a flat European IT CV still breaks on Greenhouse
Exceptions matter because candidates are told to stand out visually in markets that still run plain Word behind the scenes.
GitHub link replaces employer name. Greenhouse needs a company string. Put repo links in bullet two, not where the employer line should be.
Contract roles without agency or client name. European mid-level IT work often mixes payroll employers and client sites. Label each stretch with the name on the contract or the client brand the posting would recognize.
Mixed EU and UK date styles on one page. March 2021 beside 03/21 tells the importer two different stories. Pick one format for the whole file.
Photo embedded as a floating object. Some templates wrap the headshot in a shape that breaks text flow. Use a plain top line for contact data. Skip the photo on global tech postings that strip images.
Edge case: public-sector Europass required. When the portal mandates Europass, submit their template there and use your flat single-column export on the company's Greenhouse link if they run parallel tracks.
Edge case: Greenhouse re-compresses your PDF. Preview may look wrong even when your DOCX is clean. Re-upload DOCX on the company site or email one plain file when a recruiter requests it.
This will not fix applying to roles where you lack work authorization or a must-have stack. It stops a qualified mid-level engineer from looking empty because the parser ate the dates.
Test your CV before the next Greenhouse upload
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 tools sit in readable lines.
When the role is a stretch but your track record is strong, run score your job match after the layout pass. Format fixes visibility. They do not invent skills the posting lists in bullet one.
If the Greenhouse form has a cover letter field, draft one with the cover letter generator using the same job description. Repeat employer names and work-authorization line exactly as they appear on the CV so nothing contradicts the parsed file.
Do this now: Flatten to one column, align title lines, move tools into bullets, fix Month Year dates, paste into Notepad, then submit once.
What to do now
Greenhouse ATS resume optimization for European IT CVs is boring on purpose: one column, title line above employer, tools in dated bullets, Month Year everywhere. That is what parsers and recruiters both read before they judge fit.
- Strip tables and sidebar skill rails from the master file.
- Put posting keywords in bullet one under your current role.
- Label contract and agency blocks with honest Month Year lines.
- Paste into Notepad before you trust the PDF preview.
- 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 stack, and send one clean upload.
Read more
Frequently asked questions
Try DOCX when the portal allows it. European CV templates from design tools often export as image-heavy PDFs that Greenhouse reads out of order. A plain Word file with built-in heading styles keeps employer blocks intact. If the employer requires PDF, print to PDF from Word after you strip tables and sidebars, not from Canva. Paste the export into Notepad before you submit so you see the same order recruiters get.
Match the posting and upload label. UK, Ireland, and DACH employers often say CV. US-headquartered tech firms in Europe may say resume on the same Greenhouse form. The parser rules do not change: single column, Month Year dates, tools in Experience bullets. File name can follow the label on the form so nothing looks mismatched in the recruiter inbox.
In Experience bullet one under the employer where you used them, then repeat in a short Skills line if needed. Greenhouse weights dated bullets higher than undated sidebar lists. Python beside a backend role in 2023 beats Python in a right-rail icon row with no job anchor. If the tool appears in three roles, name it in the bullet where scope was largest.
Europass uses tables and fixed blocks that Greenhouse often flattens wrong. Dates can land under the wrong employer and language skills can detach from contact lines. If a company asks for Europass, still run a plain single-column export for Greenhouse uploads when the form accepts attachments. Keep Europass for public-sector portals that require the template.
Yes when the portal lets you replace the file or a recruiter requests an updated CV. Rebuild with flat layout, correct title line, and tools in bullets, paste into Notepad to confirm order, then upload once. Note in one sentence that you fixed formatting so scope parses cleanly. Do not resubmit five versions without a real change.