11 min read
When Lever ATS resume troubleshooting for US IT roles comes up, the fix is almost always the same: export a single-column file, put contact info and GitHub in the body as plain text, and fill every Lever work-history field even when your PDF is attached. Keywords won't save a layout the importer reads out of order. Your local Preview pane is not the recruiter view.
You're not failing some secret score. You're uploading a file built for human eyes into a portal that stores a flattened text copy beside empty form rows. Before you send the next startup application, check your resume for free against the posting. If Python lands under an internship line in the parse preview, a human won't see your current role first either.
Job searching in US tech is already noisy. You don't need another lecture about tailoring. You need to know why Lever garbles the same resume Word opens perfectly, which of four breaks is yours, and what you'll change in the next ten minutes.
Quick Wins
- Copy your PDF into Notepad. If skills jump above your current job, rebuild single-column.
- Write github.com/username in plain text. No buttons, no icons, no header zones.
- Fill Lever employment rows even when the resume upload is required.
- Use Month Year dates and 11-point Calibri or Arial in one column.
Why Lever stores a different file than the one you uploaded
Lever is common at US startups and growth-stage tech companies. The apply flow looks simple: attach a resume, answer a few questions, submit. Behind that screen, the system keeps two versions of you. One is the PDF thumbnail you recognize. The other is a text extraction the recruiter search bar actually queries.
When those two versions disagree, your strongest bullet is invisible. A composite backend engineer uploads a two-column template with Kubernetes in a left skill rail. On screen, the layout looks modern. In the Lever profile, those skills attach to a college help-desk role and the current employer block shows no stack at all.
IT resumes trigger this more than most because they pack dense tool strings, repo links, and contract titles into tight space. Parsers read left to right, top to bottom, often as one stream. Side-by-side columns, icon grids, and text boxes built for designers do not survive that read order.
Lever also splits file upload from structured fields. Candidates treat the attachment as the real application and skip the employment rows because the work is already on page one. Recruiters opening the profile first see blank dates and a missing phone number. That gap is structural, not proofreading.
This will not fix applying to staff-level roles when your scope is mid-level. It stops a qualified engineer from dying because the portal could not read the layout. For a fast pre-flight after you rebuild, read the 30-second ATS audit before submitting and compare it to the parse preview you get locally.
Lever ATS resume troubleshooting for US IT roles: four breaks and fixes
Most Lever parsing pain for US IT candidates falls into four buckets. Match your fix to the bucket before you download another template or stuff more keywords into a sidebar. I've opened Lever profiles where the PDF thumbnail looked sharp and the parsed skills block was empty because the stack sat in a left column the importer skipped.
Break 1: Skill grids and two-column layouts reorder your stack
Tech resumes love side-by-side skill tables and left rails with Python, AWS, and Terraform on display. Parsers read that rail as body text and dump it near the wrong employer. Your current role bullets can end up last in the profile.
How to tell this is yours: Canva, Novoresume, or a Word template with a colored sidebar. Notepad paste puts Skills above Experience or merges sections into one block.
Before: Two-column design. Left rail lists Python, PostgreSQL, Docker, AWS. Current role bullet: Responsible for backend services and deployments.
After: Single-column DOCX in 11-point Calibri. Bullet opens: Built Python microservices on AWS ECS, cutting deploy time from 45 to 12 minutes in Q2 2025. Skills section below Experience lists tools in plain comma-separated lines, no table.
Fix: Rebuild single-column. Put posting terms in the first eight words of role bullets. Keep Skills as a simple list under Experience, not a parallel column.
Break 2: Repo links and contact lines sit where Lever does not read
Headers, footers, and hyperlink buttons are tidy on a PDF. Many importers skip header and footer zones entirely. A GitHub URL behind the word Profile disappears. A phone number in a Word header never reaches the recruiter inbox.
How to tell this is yours: You cannot select your email when you click the header area. The Lever form still shows empty phone and website fields after upload.
Before: Name block in body. Phone and github.com/handle hidden in footer. Lever website field blank.
After: Contact block directly under name: city, phone, email, github.com/handle, portfolio URL spelled out. Same fields copied into Lever structured rows.
Fix: Move every contact line into the body. Spell URLs in full. Mirror the same strings in Lever form fields before submit.
Break 3: Empty Lever employment rows with a resume attached
Upload-only habits hurt here. Lever asks for employer, title, and dates in separate boxes while also accepting a file. Candidates attach the PDF and skip the rows because the work is already written. Recruiters sorting by current title see an incomplete profile.
How to tell this is yours: Your PDF is gorgeous. The Lever sidebar shows one job with no end date and two blank prior roles you meant to include.
Before: Senior Software Engineer PDF attached. Lever experience section: one row filled, two prior employers missing, dates as 03/2021 to Present.
After: Three Lever rows filled with Month Year dates. Titles match the resume exactly. Same metrics in bullets and in the description box when character limits allow a shortened version.
Fix: Treat upload plus form as one task. Fill the last three roles line by line. Use March 2021 to Present, not mixed numeric formats.
Break 4: Image PDFs and design exports with no selectable text
Portfolio sites, some LaTeX exports, and scanned files store text as pictures. Lever accepts the file size. The parser sees blank space. Tech candidates hit this when they export from a design tool or print-to-PDF a fancy theme.
How to tell this is yours: You cannot highlight individual words in the PDF. Copy-paste into email produces empty space or odd symbols.
Before: Designed one-page PDF from a visual resume builder. No selectable text. Lever profile shows employer name missing.
After: Google Docs rebuild of the same content, exported as text-based PDF. Bullet: Migrated 14 Node.js services to Kubernetes on EKS, holding p99 latency under 180ms through peak traffic in 2024.
Fix: Re-type into Word or Google Docs. Export only after the highlight test passes. Keep a plain DOCX master for every application.
Composite example: DevOps engineer, Series B startup
Posting wants Terraform, AWS, and on-call ownership on a platform team. Lever apply flow with separate experience fields.
Before: Icon grid for tools. On-call bullet buried under a left column. Lever rows empty except upload.
After: Single-column file. Bullet: Owned Terraform modules for 40 AWS accounts, cutting drift incidents from 6 to 1 per quarter in 2025. Lever rows list the same title and March 2023 to Present dates.
Composite example: data engineer with contract history
Posting searches Spark, Airflow, and Snowflake for a US remote data platform role.
Before: Contract months hidden inside one employer block. Skills in a three-column table. Dates as 2022 to 2024 with no months.
After: Separate lines for contract agency and client with Month Year ranges. Bullet: Built Airflow DAGs ingesting 2TB daily into Snowflake, reducing pipeline failures 15% in Q4 2024. Skills listed plain text below Experience.
Composite example: frontend developer with project URLs
Posting wants React, TypeScript, and accessibility keywords for a product engineering team.
Before: Project links as blue hyperlinked text only. Two-column header with title on the left and contact on the right.
After: Bullet: Shipped React and TypeScript checkout flow, lifting accessibility score to 98 on Lighthouse audits in 2025. Portfolio URL written as plain text under Skills. Single-column header.
Ten-minute tell: which break is yours
Run four checks in order. Highlight one word in a bullet. If you cannot, start with Break 4. If you can, paste all text into Notepad. Wrong order means Break 1. If Notepad looks fine but Lever fields are empty, Break 3. If contact or GitHub is missing in the profile, Break 2. You can hold more than one. Fix layout first, then fields, then links.
Diagnostic order: (1) Highlight test in PDF. (2) Notepad paste for column order. (3) Header and footer contact check. (4) Lever field row audit. (5) Re-export single-column. (6) Re-submit before the req closes.
Copy-paste block: Lever IT export checklist
{`Before you hit Submit on Lever:
[ ] Single column, no tables, text boxes, or icon grids
[ ] Contact name, phone, email, city in the body (not header/footer)
[ ] github.com/username and portfolio URL in plain text
[ ] Dates as Month Year (March 2021 to Present)
[ ] PDF text highlights word by word (not a scan)
[ ] Notepad paste matches visual order
[ ] Lever employment rows filled for last three roles
[ ] Posting keywords in first eight words of current-role bullet
[ ] File name: FirstName-LastName-Resume.pdf (no "final_v9")
[ ] One file type per posting instructions`}
Pair the checklist with why your resume breaks after submitting online when the same file fails on Greenhouse or Workday after you fix Lever. The layout rules overlap; only the form fields change.
Edge case: LaTeX or academic CV export
CS graduates sometimes apply with a multi-page CV full of publications and course tables. For industry Lever roles, swap to a one- or two-page industry resume in Word. Keep the CV for faculty postings. Parsers treat dense academic tables like skill grids.
Edge case: staff engineer with a long project appendix
When you are past two pages, cut the appendix from the upload. Keep five strong bullets on the current role. Put the longer architecture write-up on your portfolio site and link it in plain text. Lever is not the place for a fifteen-line microservice diagram in the PDF margin.
Edge case: referral link with a shortened apply URL
Referrals still run your file through the same parser. Do not send a designed version to a friend and a plain version to the portal. One master DOCX, one export per req. Mismatched versions confuse both the referrer and the recruiter who opens the wrong attachment from email.
When a plain layout still fails in Lever
Chasing keyword density on a file the parser skips. Fix structure first. Put Terraform and Kubernetes in bullets the importer can read, not inside a table it ignores.
Trusting the PDF thumbnail. Mini previews lie. Run highlight and Notepad tests instead of eyeballing margins.
Upload-only with empty Lever rows. Fill employment fields even when the attachment is required. Recruiters live in the structured view.
Special characters in tool strings. Pipes, plus signs, and slashes in a single Skills line can merge oddly. Split tools into separate bullets or comma lists instead of Python | Go | Rust in one table cell.
Creative section titles. Use Experience, Education, and Skills. My Engineering Journey parses worse than a standard label every time.
Exception: when the posting asks for a cover letter in a free-text box, paste three plain-text bullets there that repeat metrics from your resume. Do not introduce tools the file does not support. Keep employer spelling identical between upload and form.
Another exception: some Lever reqs include a mandatory diversity or work-authorization question before upload. Answer those first, then run the checklist. A perfect file still stalls if required attestations are blank.
Test the file before your next Lever upload
A clean Lever application starts with a file the checker reads the same way a portal would. Upload your resume and the job description to HireFlow's free ATS resume checker and fix layout gaps before you touch keyword density. If your GitHub line or current title disappears in the parse preview, it will disappear in the recruiter view.
When the startup posting also asks for a short note and you want prose that matches the rebuilt bullets, use the cover letter generator with the same job description. Repeat the metric from bullet one. Do not claim on-call ownership in the letter if the resume still reads ticket triage only.
Do this now: Paste your PDF into Notepad, note what moved, rebuild single-column, fill three Lever employment rows, run the checker, then submit one clean export.
Lever ATS resume troubleshooting for US IT roles: what to fix tonight
You do not need a new design theme. You need Lever to read the file you already wrote and the form rows to match it.
- Name your break: column reorder, hidden contact, empty Lever fields, or image PDF.
- Run highlight and Notepad tests before any startup upload.
- Rebuild single-column with body contact info, plain GitHub text, and Month Year dates.
- Fill three employment rows even when the resume attachment is required.
Open the Lever posting you want most. Run a free ATS check on the file you plan to attach, fix the first structural gap, and submit one clean export. That is how you stop losing screens to a garbled upload instead of a weak background.
Read more
Frequently asked questions
Follow the posting. When Lever accepts both, a single-column DOCX exported from Word or Google Docs often pastes more cleanly than a designed PDF. When the posting says PDF only, export a text-based PDF you can highlight word by word. Never upload a scan or a portfolio export with icons baked in.
Hyperlinks hidden behind button text and contact lines tucked in Word headers are common drop points. Write github.com/username in plain text in the body. Put phone and email directly under your name, not in a header or footer zone the importer skips.
Yes. Treat the upload and the form as one task. Recruiters often open the structured Lever profile first. Empty employment rows with a pretty PDF attached still look incomplete. Copy dates and titles from your file into each field line by line.
Multi-column skill grids are a frequent reorder trigger. Skills in a left rail can land under an old internship. Move posting terms into the first eight words of role bullets, then list tools in a plain single-column Skills section below Experience.
When the req still accepts edits, re-upload a fixed single-column file and update the structured fields to match. If the posting is closed, reply to the confirmation email with three plain-text bullets and offer a corrected attachment. Fix the master file before the next startup application so the same break does not repeat.