11 min read
You've shipped features, cleared on-call pages, and still get silence from UK scale-ups that run Lever. Your CV looks sharp on screen. The parser read your AWS and TypeScript sidebar between two contract blocks, so your current employer landed under your BSc and the recruiter timeline shows a gap that isn't real.
Check your resume for free with the posting pasted in. You'll often see stack terms flagged as matched while Work Experience is empty or out of order. That's a layout problem on a UK IT file, not a missing keyword. Lever doesn't fail you because you forgot one more acronym. It fails when columns scramble employer order.
Below you'll walk through five fixes with before/after pairs for software, DevOps, and graduate roles, two edge cases for contractors and bootcamp CVs, mistakes that still break Lever imports, and a copy-paste skeleton you can use tonight. Job searching is draining. This page is about what to change on the file before you upload again.
Quick Wins
- Switch to one column before you add another tool to Skills.
- Put Python, AWS, or Kubernetes in bullet one under the dated role.
- Paste your PDF into Notepad and confirm employer order.
- Move phone and email out of the Word header into body text.
What Lever reads before a UK recruiter opens your file
Lever doesn't grade your CV like a certification exam. It extracts fields: employer, title, dates, degree, skills. UK tech recruiters search those fields and skim the attachment. When a two-column template puts Kubernetes in a left rail, the parser reads across the page and stitches lines in the wrong order. Your strongest contract can end up listed after a university project.
The bar your file has to clear: one vertical stream, standard section labels, stack proof inside dated Work Experience bullets, text you can copy into Notepad in the same order a human would read it, and Month Year dates on every role.
A composite backend developer whose CV opens with a purple sidebar still lists Terraform in Skills. Lever imports Terraform under a 2020 internship because the sidebar sat between two Employment blocks. The keyword matched. The career timeline didn't.
UK IT CVs often carry more detail than US resumes: A-levels, certifications, contract stints, and a GitHub line. That's fine in the attachment if it stays in one column. It becomes noise when tables split contact details from the body or when icons replace section headers.
Recruiters still open the PDF after the import. They ctrl-f for tools from the posting and scan bullet one under each title. A parse that drops your latest employer makes you look between jobs when you're not. Fixing layout is faster than sending a follow-up explaining the timeline.
Lever is common across UK fintech, SaaS, and scale-up engineering hiring. The portal auto-fill fields come from the parser, not from your design choices. When those fields disagree with the attachment, recruiters trust the structured view first.
Read Flow CV layout tips that pass ATS for the general single-column rule. This page applies it to Lever uploads from UK IT candidates specifically.
Lever ATS optimization UK IT CV: five parsing fixes
Step 1: Flatten to a single column
Open your CV in Word or Google Docs. Remove text boxes, tables, and sidebar columns. Skills move below Work Experience, not beside it. If you're using a template with a coloured left rail for your tech stack, ditch the template. Parsers follow visual order, not your intent.
Zoom out to 50% view. If content sits in two vertical bands, you're not done. The goal is one river of text from name to Skills. UK engineers sometimes resist this because the sidebar "looks more technical." Lever doesn't reward the look when Employment imports wrong.
Before: Two columns with Languages and Cloud in a left sidebar; contract roles in the right column with icon bullets.
After: One column: Name and contact lines, Profile (three lines max), Work Experience with Month Year dates, Education, Skills as a comma list.
Step 2: Put the stack inside dated roles, not a skills rail
UK IT postings search for Python, Java, AWS, Azure, Kubernetes, Terraform, and CI tools inside Experience, not only in a footer cloud. Move each tool to the bullet where you used it. Skills becomes an echo list after roles, not page-one wallpaper.
Before: Page one is only a 24-line Skills block; first employer appears mid page two.
After: Software Engineer | Brightwave | Jun 2022 to Present leads with a bullet naming Python, FastAPI, and AWS in the first eight words; Skills echoes those terms below dated roles.
Step 3: Rename sections to labels Lever maps
Use Work Experience, Education, and Skills. UK headings like Employment History usually parse, but creative merges break mapping. Drop emoji section titles, ALL CAPS decorative headers, and merged blocks like Technical Profile & Stack.
Before: Section titled Engineering Journey with star icons; certifications in a table above any employer name.
After: Profile stays as three lines under the name; roles sit under Work Experience with company, title, and Month Year on readable lines.
Step 4: Export a text-based PDF or DOCX
Save as .docx or export PDF from Word or Docs, not from a design tool that flattens text into shapes. Open the PDF, select all, paste into Notepad. If employer names scramble or vanish, Lever will struggle too.
DOCX uploads sometimes preserve hyperlinks recruiters click. PDFs are safer when you've had font embedding issues. Either format works if the paste test passes. Avoid password-protected files and avoid print-to-PDF from a browser preview of a portfolio site.
I've screened UK engineering CVs in Lever where the PDF looked crisp but pasted as symbol blocks because the candidate exported from a graphics app. The fix was retyping two contract roles in Word, not adding more keywords.
Before: Canva PDF with curved skill badges; paste shows random blocks between dates.
After: Word export at 11-point Calibri; paste shows employer, title, and Month Year dates in order.
Step 5: Run a parse check before you upload
After flattening, run the same file against the posting. You're checking whether Work Experience imported with employers in reverse chronological order, not whether one more acronym appears in Skills.
Before: Upload the designed PDF immediately after keyword edits.
After: Notepad paste test, then a free ATS check, then upload when employer lines match your Word file.
Before/after pair: backend software engineer
Before: Table layout with company logos; Python and PostgreSQL only in a chart; dates as DD/MM/YY without month names.
After: Backend Engineer | Northwind Pay | Mar 2021 to Present with four bullets naming Python, PostgreSQL, and Redis in the lines; Skills lists those terms after the role block; dates read Mar 2021 to Present throughout.
Before/after pair: DevOps engineer
Before: Sidebar lists Terraform, Kubernetes, GitHub Actions; jobs on the right with hyphen bullets copied from a README.
After: DevOps Engineer | Cloudscale | Jan 2023 to Present opens with cut deploy rollback rate from 8% to 2% using GitHub Actions and Terraform on 40 microservices; Skills echoes below.
Before/after pair: graduate developer
Before: Education spans two pages with every module; internship buried under A-level grades in a table.
After: Work Experience leads with Software Intern | City Bank | Jun 2025 to Aug 2025 and two bullets naming Java and Spring; Education shows degree and graduation month only; A-levels on one line.
Copy-paste UK IT CV skeleton for Lever
Your Name
City | [email protected] | phone | linkedin.com/in/you | github.com/you
Profile (2-3 lines, no table)
Work Experience
Company Name, Job Title
Month Year to Month Year
- Bullet with stack and outcome from posting (scope + metric)
- Second bullet with CI/CD or on-call proof if relevant
Education
University Name, Degree
Month Year
Skills: language, cloud, tool (comma list, no icons)
Paste that into Word, fill your lines, and export. If your posting wants a cover letter, mirror the same employer order there so nothing contradicts the CV.
Edge case: contractor with six short gigs
Contract-heavy UK IT CVs scare parsers when each stint sits inside nested tables. Stack each client with Month Year dates on plain lines. Put the posting's top stack terms in bullet one for the most relevant contract, not in a page-one skills matrix.
Before: Six contracts in a three-column table with logos; skills duplicated in a header ribbon.
After: Contract Software Engineer | Client A | Jan 2024 to Jun 2024 with two bullets; repeat for each client in one column; Skills echoes tools once at the bottom.
Edge case: bootcamp graduate with skills-first layout
Bootcamp CVs that lead with twelve course modules push Employment off page one. Trim courses to one line under Education. Put React or Node proof in bullets under a project role or internship, even if it was unpaid.
Before: Page one is only bootcamp modules and Udemy lists; first paid role on page three.
After: Junior Developer | Retail Group | Sep 2025 to Present with bullets naming React and Node from the capstone; bootcamp name sits under Education on one line.
Read resume upload mistakes that instantly disqualify you when the portal rejects the file before parsing even starts.
Where UK tech CV layouts still break in Lever
Keyword edits on a broken layout. Adding Kubernetes or stakeholder management to Skills while employers import out of order wastes an evening. Flatten first, then tailor bullets under the right company line.
Tables for alignment. Candidates use invisible tables to line up dates beside titles. Lever reads cell by cell and splits job titles from companies. Use plain lines instead.
Fancy bullets and icons. Checkmarks, arrows, and custom fonts often paste as squares. Stick to hyphen or dot bullets in Calibri or Arial at 10 to 12 point.
Scanned PDFs from print shops. A clean scan is still an image. Recruiters cannot search it and parsers cannot extract dates. Retype in Word even if it feels old-fashioned.
GitHub and portfolio links as icons only. A glyph with no plain URL drops the link on import. Write the full github.com path in text recruiters can copy.
Mixing UK and US date styles on one CV. 03/2024 and March 2024 on different lines confuse both parsers and humans. Pick Month Year everywhere. Don't alternate mid-document.
Leaving Present off the current role. Open-ended dates sometimes parse as blank end dates. Write Month Year to Present on the job you're in now so Lever doesn't think you left last spring.
See why Lever strips symbols and icons for the same class of problem on US uploads. The fix is identical: plain text, one column, standard headings.
Verify the file before Lever upload
After the five steps, run the posting and your exported PDF together. You're confirming Work Experience text matches what pasted into Notepad, and that must-have tools from the ad appear inside dated bullets, not only in a footer.
When a skill still misses, add it to the role where you used it, not as a twelfth comma in Skills. When dates look wrong, standardize every line to Month Year before you tweak another word.
Run a free ATS check with the description pasted, then score your job match on the same file before you upload to Lever tonight.
Flatten the column, then tailor the stack
Optimizing your CV for Lever ATS in UK IT roles starts with import order, not keyword density. One column, stack proof inside dated bullets, standard headings, text-based export, and a Notepad paste test beat another Skills edit on a sidebar template.
Open your CV tonight. Delete the sidebar. Move Terraform and TypeScript into bullet one under your current title. Export from Word. Paste into Notepad and confirm your latest employer sits at the top of Work Experience. Run a free ATS check before you upload again. When the portal asks for a letter, generate a cover letter that repeats the same employer order as the CV.
This won't fix applying to staff engineer roles when your scope was junior support. It does stop qualified UK IT candidates from losing screens because Lever read their skills column as a job history glitch.
And if you're keeping a designed PDF for networking, fork the file. Pretty version for humans, boring single-column version for Lever. Same career, different layout.
Read more
Frequently asked questions
No. Lever reads left to right across the page. A left-rail stack list often lands between two employer blocks, so your current company imports under Education. Use one column. Put Python, AWS, Kubernetes, or TypeScript inside dated bullets under the role where you used them. Echo the same terms once in Skills after Work Experience.
Either works when the file is text-based, not a scan. Export from Word or Google Docs. Open the PDF, select all, paste into Notepad. If employer names and Month Year dates paste in order, Lever will likely read them the same way. Avoid Canva exports, portfolio-site print-to-PDF, and password-protected files.
Two pages is normal for mid-level engineers with multiple contracts. Keep page one for Work Experience starting with your current role. Push A-levels, module lists, and interests toward the bottom. Lever still parses top to bottom. A dense skills cloud on page one pushes your latest employer down the import stack.
Plain text URLs parse reliably. Write github.com/yourhandle on its own line near contact details, not inside a clickable icon or a table cell. Hyperlinked anchor text sometimes drops the URL entirely. Same rule for LinkedIn. Recruiters ctrl-f the posting stack in Experience first; the repo link is a bonus, not a substitute for dated proof.
Paste the PDF into Notepad first. Employer names should appear in reverse chronological order with dates beside each title. Then run the same file through a free ATS check with the posting pasted in. If Work Experience is empty, jumbled, or missing your current company, flatten columns before you blame keyword density.