Lever ATS Resume Parsing Issues and How to Fix Your Resume for US Jobs

12 min read

Lever ATS resume parsing breaks when your file uses columns, tables, or icon headers. The fix for US job applications is a single-column export with plain section labels, employer and title on separate lines, and Month Year dates inline on each role row. If the import preview shuffles jobs or drops dates, you won't reach keyword scoring until the layout passes.

You upload a polished PDF. The Lever portal shows your certification where your job title should be and merges two employers into one row. You're not failing a skills test. You're failing a text extraction pass that runs before a recruiter opens your profile. It's slow enough without fighting a layout you can't see until after submit.

Before you rewrite bullets, check your resume for free against the posting and confirm what Lever actually imported. A Lever ATS resume checker pass on HireFlow catches column failures early; the portal preview confirms what recruiters will sort.

Below: why the import preview lies, what to change in the next ten minutes, the exceptions where one extra line helps, before/after rows from different roles, and a copy-paste header block you can drop into Word tonight. If you've been ghosted after perfect-on-paper applies, open the parsed view before you rewrite bullets again.

Why Lever's import preview scrambles a fine-looking PDF

Lever reads your file as a stream of text, not as a designed page. It guesses where jobs start, where dates live, and which line is a section header. When you split the page into columns or decorate headers with icons, the guesser grabs the wrong line and writes it into Title, Company, or Skills.

Most Lever rejections on US reqs start as parsing noise, not missing keywords. Recruiters search parsed fields first. If your last employer imported as a skill tag, you never appear when they filter on company name. If dates vanish, you look like you have a ten-year gap when you do not.

Canva templates, Word resume builders with colored sidebars, and PDF exports from design tools are repeat offenders. They look modern on screen. They import like someone shuffled index cards.

Before: marketing resume with a left sidebar for contact and skills, right column for jobs. Lever preview shows Title blank and Salesforce listed as an employer.
After: single column. Contact block on top. Line reads Marketing Manager | Acme SaaS | Austin, TX | Jan 2022 to Mar 2026. Bullet: "Owned ABM pipeline in Salesforce and Marketo; lifted MQL-to-SQL conversion 22% in FY2025."

Same candidate. Same work. The second file sorts into marketing searches. The first file looks like a skills dump with no job history.

Before: nurse resume with stethoscope icon beside Experience and license block in a shaded table. Lever imports Registered Nurse under Skills and leaves Title empty.
After: plain header Work Experience. Line reads Registered Nurse, Med-Surg | County Hospital | Jun 2020 to Jan 2026. Bullet: "Documented care in Epic on 32-bed unit; precepted four orientees on fall-prevention workflows."

Clinical reqs filter on license strings in parsed title and employer rows. Icons do not translate. Plain labels do.

Footers and headers are another silent killer. Email and phone trapped in a PDF header often never reach the contact field. Recruiters cannot reply even when they like the bullets.

Hyperlinks hidden behind words instead of spelled-out URLs sometimes drop entirely on import. Write github.com/yourhandle and your phone number as plain text in the body.

This is not unique to one ATS, but Lever's preview is visible on many US startup and scale-up career pages. You get immediate feedback if you know to look. Most candidates stare at the PDF they designed and never scroll the parsed view.

Read whether ATS can read PDF resumes when you need the full file-format decision tree beyond Lever alone.

Lever ATS resume checker: fix parsing in the next ten minutes

Open your master resume and the Lever posting you are targeting. You are fixing layout on one export, not rebuilding twenty years of work.

1. Run the Notepad test. Select all, copy, paste into plain text. If job blocks appear out of order or dates float alone on a line, Lever will struggle the same way. That is your signal to rebuild structure before you touch wording.

2. Collapse to one column. Remove tables, text boxes, and parallel columns. Move contact info to the top of the body. Keep section order boring: Experience, Education, Skills, optional Certifications last.

3. Replace icon and graphic headers. Delete phone, envelope, and social icons. Type Contact, Work Experience, Education, and Skills as plain words. Bold is fine. Pictures are not.

4. Lock the role header pattern. Each job gets one header line with title, employer, location if useful, and dates inline. Month Year format, US order. No end date parked in a footer.

Copy-paste role header block:

Job Title | Employer Name | City, ST | Month Year to Month Year
• First bullet names the top skill from the posting in the first eight words, with one metric or scope signal.
• Second bullet adds tool, team size, or revenue context.
• Third bullet optional; stop at six bullets per role for US corporate norms.

5. Standardize fonts and kill ornament. Calibri, Arial, or Times New Roman at 10.5 to 12 point. No text boxes, no diagonal section dividers, no skill bars filled with shading. Bullets can be simple hyphens or dots.

6. Export twice and read the Lever preview. Save DOCX and PDF from the same plain source. Upload to the application or a test posting. Open the parsed candidate view. Confirm each job shows title, company, and dates on one row. If one format wins, submit that one going forward.

Before: software engineer resume built in a two-column Canva template. Lever merges internships into one employer and drops the graduation year.
After: Software Engineer | Beta Systems | Remote | Jun 2021 to Jan 2026. Bullet: "Led migration of invoice service to AWS ECS; cut p95 latency from 800ms to 190ms across four nightly batch jobs."

Engineering screens lean on title and stack in parsed fields. A merged employer row makes you look like you never left school.

Before: operations manager resume lists tools in a four-column table under Skills. Lever reads column two as a job title.
After: Skills section as a comma-separated line: "SQL, Looker, Salesforce, Zendesk, WFM scheduling." Jobs stay in Experience with proof bullets, not grid cells.

Skill tables feel efficient on paper. Parsers treat each cell like a possible headline. A comma line in Skills plus proof in Experience is safer.

Edge case: you need a portfolio link for design or engineering roles. Put the full URL on its own line under contact. Do not embed the link only inside a bullet icon. Parsed views keep the text; they often lose the click target.

Edge case: short contract stints. List each contract as its own row with Contractor in the title or employer field. Do not merge three clients into one line to save space. Parsed timelines that look like one decade-long employer fail reference checks and recruiter date filters.

Edge case: federal or clearance lines. Keep clearance level in a plain Certifications section, not in a sidebar next to a logo. Sensitive details still belong on the resume when the req asks; they just need typed labels parsers can sort.

After layout passes, tailor keywords in bullets, not in headers. Mirror the posting's top tool in bullet one under your current role. That is how parsed skills and human skims align.

Read how ATS interprets recency in US resumes when dates parse correctly but filters still treat your last role as too old.

I've opened hundreds of Lever import previews that looked fine as PDFs and broken as parsed rows. The candidates who fix layout first stop guessing why silence follows a perfect-on-paper apply.

Keep a folder per target company: plain DOCX, plain PDF, screenshot of the Lever preview with fields visible, and the date you submitted. When a recruiter replies, you know exactly which version they saw.

If a template platform refuses to export single column, rebuild in Word or Google Docs once, save as master, and stop re-exporting from the design tool for ATS portals. The ten-minute rebuild pays for itself on the next Lever upload.

Bullets should stay under two lines each in plain export. Long wrapped paragraphs paste as walls of text in preview panes. Break achievements into separate lines so recruiters can scan in the parsed view the same way they scan your PDF.

Education belongs below Experience for most US corporate reqs unless you are a new grad. One line per degree: Degree, Field | School | Graduation Month Year. Do not nest education inside a table beside jobs.

When you rename sections, stay predictable. Professional History instead of Experience can work if the word Experience appears nowhere else. Safer to keep Experience and make the content do the work.

Spacing matters after paste. Blank lines between jobs tell the parser where one role ends. A solid block of text with line breaks only inside bullets reads as one long employer.

Re-upload after every structural edit, not only after keyword tweaks. One new text box added for a certification badge can undo a file that parsed cleanly yesterday.

Multilingual candidates sometimes split content across two language columns. Lever reads one stream. Pick English for US corporate reqs or put alternate language bullets below the English block in the same column, not side by side.

Veterans translating MOS codes should spell the civilian function in the title line and keep the military identifier in parentheses. Parsed title fields need words recruiters search, not acronyms alone.

Page length itself is not the enemy. A two-page plain export with six roles parses fine when each role header follows the same pattern. Page two fails when it restarts columns or inserts a tool table.

Track which employers use Lever on their career site. When you see the same scrambled preview twice, stop reusing the designed PDF for that stack. Swap to the plain master before the third tailor pass.

When plain text is not enough (exceptions and backfires)

Exception: the posting accepts a plain-text paste field. Some Lever flows include a free-text box. Paste the Notepad version there even when you also upload a PDF. Dual paths give recruiters a fallback when the parser stumbles.

Exception: academic CVs with long publication lists. US industry reqs still want a one- to two-page resume body. Move publications to a separate document link on your site or a shortened Selected Publications section with typed headers, not a multi-column journal table.

Exception: creative roles that require a portfolio. Keep the Lever file boring and single column. Send portfolio links as plain URLs in contact or bullet one. Do not embed critical proof only inside images the parser cannot read.

Backfire: keyword stuffing in headers. Product Manager SQL Agile Jira as a title line reads as spam in parsed Title fields and human skims alike. Put tools in Skills and proof in bullets.

Backfire: hiding employment gaps with merged headers. Consulting headers that swallow a six-month gap look clever in Word and dishonest in a parsed timeline. Honest Month Year rows beat one invented umbrella employer.

Backfire: uploading a scanned PDF. Image-only PDFs parse as empty text. Export from the source document. If you only have a scan, retype into a plain DOCX before you apply through Lever.

Backfire: trusting the resume score without opening preview. A green score on a third-party widget does not replace the Lever import pane. Open the employer's parsed view whenever the portal shows it.

Backfire: decorative skill bars and star ratings. Graphics do not map to proficiency fields. They often break the line below them. Use comma lists or plain bullets for tools you actually used on the job.

Read why your resume scores high but you still get rejected when parsing is clean and silence continues after human screen.

Check the file before you submit on Lever

After you flatten columns and fix dates, run the posting through HireFlow's free ATS resume checker. You are confirming employer, title, and dates still parse as one row per job before Lever's portal gets the file.

If the posting asks for a short note about a title change or contract stint, generate a cover letter from the same plain resume version you already checked. One extra sentence in the letter beats a third column on the resume.

Ship the plain export tonight

Lever ATS resume parsing issues on US jobs usually trace back to layout, not talent. Columns, icon headers, and floating dates break the import preview. Run a Lever ATS resume checker on the plain export, then single-column Month Year rows on each role before you submit.

Collapse your template. Type section headers. Paste the role header block under each job. Run Notepad test, export DOCX and PDF, open the Lever preview, and submit the version that shows title, company, and dates on one row.

This will not fix applying to roles you are not qualified for. It does stop a qualified file from dying because a sidebar shoved your employer name into Skills.

Save the plain master separately from your designed PDF. Tailor keywords per posting on the plain file only. Same structure, swapped bullets, no new text boxes.

When a friend sends a Canva resume that parses blank, send them the role header block, not a lecture about ATS myths. They need one column and dates on the line. You already have both on this page.

• One column, typed headers, no icons.
• Month Year dates inline on each job row.
• Lever preview screenshot saved before submit.

Run the free resume check on the plain export, then apply once. Recruiters want readable rows. Give them a file Lever can sort before you worry about perfect margins.