11 min read
You uploaded a sharp two-page CV to a London fintech req on Lever. The confirmation email landed. Your PDF still looks perfect on your laptop. Two weeks later, nothing. You're not imagining a gap between what you sent and what the hiring team sees.
Job searching is already draining when you're mid-level and competing on skills you can prove. You don't need another lecture about keyword density. You need a short diagnostic to fix parsing issues Lever ATS UK mid-level tech CVs run into: which failure mode is yours, what the recruiter view probably shows, and what you'll change before the next upload.
Before you reapply, check your resume for free against the posting you just used. If the parser can't read your layout, tailoring won't matter. We'll walk the symptom, three causes, how to tell which one is yours, and the fix for each.
Quick Wins
- Copy your PDF text into Notepad. If skills jump above your current role, rebuild single-column before you upload.
- Export from Word or Google Docs. Skip Canva sidebars and LinkedIn one-click PDF exports for Lever reqs.
- Put email and +44 phone in the body, not a header Lever strips.
- Use Month Year dates on their own line under each job title.
The symptom: your CV looks fine, the Lever profile does not
A composite backend engineer uploads a polished CV through Lever for a Series B SaaS role in Manchester. On screen, TypeScript and AWS sit in a left column beside four years of platform work. In the recruiter view, those skills attach to a university placement from 2018 and the current employer line reads blank. The candidate keeps tweaking the personal statement. The parser never got a readable structure.
Breakage rarely announces itself. You won't always get an error toast. Lever accepts the file. The ATS stores a flattened text version. A recruiter opens a profile where dates float, section headers vanish, or your strongest Kubernetes bullet reads last. That is the gap between your Preview pane and their shortlist.
The pattern that shows up most: qualified mid-level engineers blame fit or luck while the upload silently scrambled their best proof.
This won't fix applying to roles you're not qualified for. It stops a strong UK tech CV from dying because Lever could not read the layout. For a fast pre-flight on any portal, read the 30-second ATS audit before submitting after you run the diagnostic below.
How to fix parsing issues Lever ATS UK mid-level tech CVs hit: three failure modes
Most Lever upload breakage falls into three buckets. Your fix should match the bucket, not a generic template swap. Work through the telltales before you download another Canva theme or add a fourth page of skills.
I've opened candidate files in Lever where the PDF thumbnail looked designer-clean and the parsed text block was one long paragraph. The single-column export fixed the screen without touching a single metric.
Cause 1: Two-column layouts and tables reorder your text
Side-by-side columns, icon grids, and invisible tables are built for human eyes. Parsers read left to right, top to bottom, often as one stream. A Technical Skills rail on the left can attach to the wrong job. A two-column header can drop your email entirely.
How to tell this is yours: your CV uses Canva, a Word template with a sidebar, or a table for contact info. When you select all text in the PDF, React skills jump above your current platform role or contact lines sit at the bottom.
Before: Two-column design with Skills in a left rail. Top bullet under current employer: Responsible for API maintenance and code reviews.
After: Single-column PDF in 11-point Calibri. Same role opens: Shipped payment APIs in Node.js and TypeScript, cutting p99 latency from 420ms to 180ms across 12 services in 2024. Technical Skills section sits below Experience with posting terms in bullets, not a sidebar.
Fix: Rebuild in a single column. Standard headings: Experience, Education, Technical Skills. No text boxes. Run the Notepad paste test before upload.
Cause 2: The file is an image, not selectable text
Scanned paper, phone photos, and some design exports store your CV as pictures. Lever may accept the file size but the parser sees blank space or garbage characters. LinkedIn PDF exports and some portfolio site generators do this when fonts embed oddly.
How to tell this is yours: you cannot highlight individual words in the PDF. Copy-paste into email produces empty space or symbols. You used LinkedIn's Save to PDF button or exported from a design tool without a text layer.
Before: LinkedIn export saved as CV_final.pdf. Lever employment rows empty. Recruiter sees a thumbnail with no searchable Terraform or Python terms.
After: DOCX rebuilt in Google Docs from the same content, then exported as text-based PDF. Same candidate, platform role: Migrated three microservices to Kubernetes on EKS, holding deploy frequency at four releases per week through Q1 2025.
Fix: Re-type into Word or Google Docs. Export PDF with text you can highlight. If the posting allows DOCX, upload that instead when Lever's form accepts it.
Cause 3: UK date formats and empty Lever fields strip history
UK CVs often use DD/MM/YYYY or compact numeric ranges like 06/19 to 12/22. Parsers without locale context misread them. Many Lever flows also split file upload from paste-into-box employment fields. Fill one path and skip the other, and half your profile stays empty even when the attachment looks complete.
How to tell this is yours: your dates use slashes without month names. Lever's work history rows are blank while the PDF is attached. Recruiters report a missing phone number despite a polished file because contact info lives in a Word header.
Before: Contact line in header only. Dates as 03/21 to Present. Lever rows for last two employers empty.
After: Contact block in body under name. Each role uses March 2021 to Present. Lever fields filled for three roles even when upload is required, with city and employer spelled exactly as on your CV.
Fix: Move contact info into the body. Use Month Year dates on separate lines. Complete required Lever fields line by line. Treat upload plus form as one task, not two optional steps.
How to tell which cause is yours in ten minutes
Open your PDF and try to highlight one word in a bullet. If you cannot, start with Cause 2. If you can, copy all text into Notepad. If skills appear above your current job or contact info vanishes, Cause 1. If Notepad looks fine but recruiters still miss your phone or Lever rows stay empty, check headers and unfilled fields for Cause 3. You can hold more than one. Fix layout first, then dates and fields.
Diagnostic order: (1) Highlight test in PDF. (2) Notepad paste for column order. (3) Header and footer contact check. (4) Open Lever preview if available. (5) Re-export single-column. (6) Re-upload before the req closes.
Composite example: full-stack developer
Posting targets Full Stack Developer in Lever with React, Node.js, and PostgreSQL in Requirements.
Before: Canva template with icon skills. Left column lists React and Node. Bullet: Worked on features and bug fixes.
After: Single-column DOCX. Bullet: Built customer onboarding in React and Node.js on PostgreSQL, shipping checkout flows used by 40k monthly active users in 2024. Skills list plain text below Experience.
Composite example: DevOps engineer
Posting wants Terraform and GitHub Actions in a Lever upload with separate experience fields for a Bristol scale-up.
Before: Two-page CV with skills table. Dates 01/20 to 09/23. Lever employment rows blank. Phone in footer.
After: Word single-column file. Bullet: Automated infra with Terraform and GitHub Actions, cutting manual deploy steps from 14 to 3 per release in 2025. Lever rows filled for three roles with January 2020 to September 2023 and body contact block.
Copy-paste block: Lever upload checklist for UK tech CVs
{`Before you hit Submit on Lever:
[ ] Single column, no tables or text boxes
[ ] Contact name, +44 phone, email, city in the body (not header/footer)
[ ] Dates as Month Year (March 2021 to Present)
[ ] PDF text highlights word by word (not a LinkedIn export scan)
[ ] Notepad paste matches visual order
[ ] Lever work-history fields filled even if upload is attached
[ ] File name: FirstName-LastName-CV.pdf (no "final_v7")
[ ] Posting stack terms in first eight words of bullet one`}
Pair the checklist with the frontend developer resume writing guide when your strongest proof is component work but the posting title says Software Engineer.
Edge case: contract and IR35 stints on one CV
Mid-level UK tech CVs often list three contract roles in two years. Parsers merge them when you use nested bullets or bold sub-headings inside one employer block. Give each contract its own job line with Month Year dates and the end client name when NDA allows. Plain text sub-role lines import more reliably than visual tricks.
Edge case: GitHub and portfolio links
Lever often stores URLs as plain text, not clickable icons. Replace icon buttons with full https links on one line under contact info. Do not hide links inside a table cell the parser skips. If the posting asks for a portfolio, paste the same URL into the Lever field and the CV body so both paths match.
Edge case: degree classification and A-level lines
UK Education sections with predicted grades, A-levels, and GCSEs can push technical proof off page one. Keep degree, university, and graduation year on clear lines. Move older school detail to one line or drop it when you're five or more years out. Parsers map Education more reliably when the section heading is standard and dates use Month Year.
What broken Lever uploads share
Chasing keywords on a layout the parser skips. Fix structure first, then tune posting terms in bullets.
Trusting the thumbnail. Mini previews lie. Run highlight and Notepad tests instead.
Upload-only applications with empty Lever fields. Fill employment rows even when a PDF is attached.
Header contact blocks. Move phone and email into the body every time.
LinkedIn export as final CV. Rebuild in Word before any Lever req you care about.
Creative section titles. Use Experience and Education. Parsers map standard labels more reliably than My Engineering Journey.
Test before you upload again
A clean Lever upload starts with a file the checker can read the same way a portal would. Upload your CV and the job description to HireFlow's free ATS resume checker and fix layout gaps before you touch keywords. If the Terraform line disappears in the parse preview, it will disappear in the recruiter view.
When the posting also asks for a short letter and you want the prose to match the rebuilt bullets, use the cover letter generator with the same posting. Repeat the metric from bullet one. Do not introduce tools the CV cannot support.
Do this now: Paste your PDF into Notepad, note what moved, rebuild single-column, run the checker, then re-upload or refill Lever fields before the req closes.
Fix parsing issues Lever ATS UK mid-level tech CVs face: what to change tonight
You don't need a new design. You need Lever to read the file you already wrote.
- Name your failure mode: column reorder, image PDF, or stripped headers and empty fields.
- Run highlight and Notepad tests before any Lever upload.
- Rebuild single-column with body contact info and Month Year dates.
- Fill Lever employment fields even when a PDF is attached.
Open the file you submitted last. Run a free ATS check on it, fix the first structural gap, and reapply with one clean export. That is how you stop losing screens to a broken upload instead of weak experience.
Read more
Frequently asked questions
After upload, open any preview Lever shows or copy all text from your PDF into Notepad. If Kubernetes skills sit under a 2019 internship, if your +44 phone never appears, or if employment rows stay blank while the attachment looks fine, the parser lost structure. A clean file pastes in the same order you wrote it.
Follow the posting. When Lever accepts DOCX, a single-column Word file often imports employment rows more reliably than a design-heavy PDF. When it asks for PDF only, export text you can highlight from Word or Google Docs, not a Canva or LinkedIn export. One clean file beats uploading both formats.
Ambiguous numeric dates are the usual trigger. DD/MM/YYYY and MM/DD/YYYY look identical to a parser without context. Month Year on its own line (March 2021 to Present) imports more reliably than 03/2021. Spell the month when you can, especially on mid-level CVs with contract stints back to back.
Not every upload fails, but side-by-side columns are a common reorder trigger. Skills in a left rail can land under the wrong employer. A single-column layout with a plain Technical Skills section below Experience is the safer default for Lever unless you have confirmed the portal preview matches your PDF.
If the req still accepts edits, re-upload a fixed single-column file and note the change in your confirmation reply. If edits are locked, email the recruiter a plain-text version of your top three bullets and offer a corrected attachment. Fix the master file before the next application so the same parser error does not repeat.