11 min read
Your PDF looks clean. Lever's profile view shows React and Kubernetes in a Skills block above a 2019 internship while your Staff Engineer title sits mid-page. That's not a keyword problem. That's import order. Optimizing resume for Lever ATS US tech roles means fixing how the file reads top to bottom before you add another stack synonym.
Before you swap templates, check your resume for free on the same DOCX you'll upload. You'll see whether your current title imports first or whether a sidebar Skills column jumped ahead of Experience.
US mid and senior engineering searches are draining when you've shipped production systems and still get silence on Lever portals. You're not failing because you lack TypeScript. Your file might be asking the reader to infer stack proof from a Skills cloud the parser read before your employer block. This page walks symptom to cause to fix so you can edit tonight without another keyword list.
Pull up the req you're targeting. Don't start in Skills. Export plain text and read line one after your name. If the first job title isn't your current role, layout beats wording every time.
Quick Wins
- Flatten to single-column DOCX before any wording pass.
- Put Month Year dates on the same line as each job title.
- Move must-have stack into Experience bullets, then echo in Skills.
- Paste plain text into Notepad and confirm current role is on top.
The symptom: polished PDF, scrambled Lever profile
A composite senior backend engineer whose resume shows Node and Postgres in a left-column Skills table, a summary listing distributed systems and cross-functional leadership, and Experience bullets that open with worked on APIs and collaborated with product is the file I see every week on US tech reqs. The human view looks stocked. The Lever import shows skills without dates and duty lines without services owned.
Lever reads files roughly top to bottom in one stream. It is not guessing your career story from design intent. When a two-column template puts Skills in a narrow left rail, that rail often imports before the main Experience column. Recruiters then see tools listed above a title that should be current. I've screened stacks of these in Lever and Greenhouse sibling portals, and the files that survive the first pass almost always use single-column DOCX with stack names inside dated employer lines.
The pattern: keyword checker green while the Lever preview shows wrong chronology or Skills-first layout. Both mean the parser read structure before content. Fix import order before you chase match percentage.
Edge case one: you're Staff level with one employer for six years and multiple promotions. List each title change with Month Year dates on its own line or as separate sub-entries so promotion scope imports clearly. Edge case two: you're contracting through an agency. Put agency or client on the employer line the posting expects and keep stack proof in bullets tied to that engagement.
Edge case three: same resume worked on a Workday portal last month. Workday can still scramble tables but often preserves more cell content. Lever punishes sidebars harder. Don't assume cross-ATS parity. Test each upload path.
When you're unsure whether parsing or match is the blocker, read how ATS matches resumes to job descriptions after you flatten layout here. Structure comes first.
Optimizing resume for Lever ATS US tech roles: three causes
Diagnostic order matters. Fix column layout before you polish adjectives. Then fix Month Year date lines. Then move stack proof into Experience before Skills echo.
Cause 1: Sidebar Skills import before your current title
Two-column resume templates look modern on PDF. Lever frequently reads the narrow column first. Your React, TypeScript, and AWS rows can appear above Senior Software Engineer even when the PDF looks fine to you.
Before: Left column Skills table: React, TypeScript, GraphQL, AWS. Right column Experience starts with current role below the fold on some screens.
After: Single column. Experience first. Bullet one: Built React and TypeScript checkout flow serving 2.1M monthly users on AWS during 2024. Skills section below repeats React and TypeScript after proof exists.
Before: Skills cloud at top of page one. Bullet under current job: Collaborated on microservices improvements.
After: Senior Backend Engineer, FinTech Co, Remote · January 2021 to Present. Bullet one: Owned Node and Postgres payment ledger handling 180k daily transactions; cut p99 latency 40% in Q2 2025.
Fix: Delete sidebar tables. Move Skills below Experience. Put each must-have stack in a dated bullet before you echo it in Skills.
Cause 2: Month Year dates parse as wrong chronology
Slash dates, floating end dates in a second column, and quarter-only labels scramble order. Lever and human reviewers both assume reverse chronological Experience. If dates import wrong, you look junior or between roles.
Before: 01/2020 to 06/2024 on one line, employer name in a table cell below.
After: Staff Software Engineer, Platform Co, Austin · January 2020 to June 2024. Two bullets under that header. Next employer block follows immediately.
Fix: Spell Month Year on the title line. Export DOCX from Word. Paste into Notepad. Read top to bottom. If 2017 appears before 2024, flatten tables before any keyword edit.
Cause 3: Stack keywords in Skills without Experience proof
Mid and senior reqs ask for services owned, on-call scope, and language depth. Skills rows alone read like exposure. Recruiters ctrl-f inside employer lines for the posting's must-have stack.
Before: Skills: Python, Django, Redis, Kubernetes. Bullet: Worked on backend features for the platform team.
After: Migrated 14 Django services to Kubernetes on GKE; reduced deploy failures from 6 per month to 1 across Q1 2025 while owning on-call rotation for payments API.
Fix: Circle three must-haves from the posting. Place each in a dated bullet with scope numbers. Echo in Skills second. Skills supports bullets. It does not replace them.
How to tell which cause is yours
Run a free parse check on your upload DOCX. If Skills appears before your current title in the output, you're in Cause 1. If plain text drops your latest role below an old internship, Cause 2. If stack terms show green in Skills but not under a dated employer line, Cause 3. You can have two at once. Fix layout, then dates, then bullet proof.
Workday comparison edge case: you passed a Workday application with the same PDF last week. Workday may have preserved more text from table cells. Lever on a startup's careers page may not. Re-test on Lever with single-column DOCX even when Workday seemed fine.
Copy-paste block: Lever-safe header line
Copy-paste employer header format
[Job Title], [Company], [City or Remote] · [Month Year] to [Month Year or Present]
Example:
Senior Software Engineer, Payments Platform, Remote · March 2022 to Present
Rules:
• One line per role header, no tables
• Skills section goes BELOW all Experience blocks
• Must-have stack appears in bullet 1 before Skills echo
For bullet rewrites after layout is flat, see why weak bullet points get ignored . Lever won't score what it imported out of order.
What still fails after a keyword pass
Uploading Canva or Figma PDF exports. Design tools hide tables and text boxes that Lever reads as random order. Fix: Word or Google Docs exported to single-column DOCX, then PDF only if required.
Icons for contact and Skills. Phone and GitHub icons look tidy. Many parsers drop the adjacent text. Fix: plain text contact lines and spelled-out URLs.
Keyword stuffing after bullets stay generic. Adding Kubernetes twelve times without a dated bullet is noise. Fix: one employer line per must-have stack.
Assuming Workday success means Lever success. Different import engines, different failure modes. Fix: portal-specific plain-text paste check.
Scoring a different file than you upload. You fixed DOCX locally and submitted last month's PDF. Recruiters open what's in Lever. Fix: lock file name before submit.
Exception: academic CVs and some federal forms follow longer formats. Corporate US software engineer, platform, and infra roles on Lever still reward single-column proof in dated Experience rows with Month Year on the title line.
Parse-check before you hit apply on Lever
Upload your flattened DOCX to HireFlow's free ATS resume checker . Confirm Experience imports with current role on top, must-have stack shows in bullets recruiters will scroll to, and contact lines appear in body text.
When layout passes but match still feels thin against the posting, paste the job description into Score your job match . You're checking whether terms moved from Skills-only into dated lines, not chasing a perfect percentage on a file that still hides stack proof behind collaborate verbs.
Do this now: Single-column export, plain-text paste, fix title order, move stack into bullet one, then upload the same file you tested.
What to fix tonight
Optimizing resume for Lever ATS US tech roles isn't adding more Skills rows. It's single-column DOCX, Month Year dates on title lines, stack proof inside Experience bullets, and uploading the same file you plain-text tested.
- Flatten layout and move Skills below Experience.
- Rewrite bullet one with stack, scope, and outcome.
- Paste plain text and confirm current role is on top.
- Parse-check the DOCX before Lever submit.
Open the req you care about. Run a free ATS check , confirm import order, and send a resume that survives the Lever preview.
When the employer asks for a short note, use the free cover letter generator with the same posting. Name the stack and service scope from bullet one so the letter matches the resume a hiring manager opens next.
This won't fix applying to roles where you lack the core stack the req names. It stops qualified engineering files from dying because a sidebar Skills column imported before your current title.
Read more
Frequently asked questions
DOCX usually imports cleaner when the portal offers both. Lever reads top to bottom in a single column. Tables, icons, and sidebar Skills blocks often land out of order in PDF exports from design tools. Upload single-column DOCX at 11-point Calibri or Arial, then paste plain text into Notepad to confirm your current title sits above older roles. If the employer only accepts PDF, export from Word after flattening layout, not from Canva or Google Docs with hidden tables.
Put must-have stack proof in dated Experience bullets first, then echo the same terms in a short Skills section below. Lever frequently imports a left-column Skills list before your current job title when you use two-column templates. Recruiters ctrl-f inside employer lines. A sidebar that says React and TypeScript while bullet one says worked on frontend features reads like exposure, not ownership. One employer line per must-have stack before you add a Skills cloud.
Spell dates as Month Year on the same line as the job title: Senior Software Engineer, Acme Corp, San Francisco · March 2022 to Present. Slash dates like 03/2022 can parse as day/month or month/day depending on locale. Avoid quarters-only labels without a year. Reverse chronological order only works if the parser sees titles in the order you intended. Plain-text paste is the fastest check.
No. Workday often tolerates more table-heavy layouts but can still scramble cells. Lever tends to read linearly and punishes sidebars harder. A file that looks fine in a Workday preview can still import Skills before your current title in Lever. Test the export you will upload in each portal. Do not assume a resume that passed one ATS will pass another without a plain-text paste check.
Flatten to single column before any wording pass. Remove text boxes, icons, and table-based headers. Put employer, title, location, and Month Year dates on one line each. Move Skills below Experience. Re-export DOCX and paste into Notepad. If your 2024 role still lands under a 2018 internship, the layout is still broken. Keywords will not fix import order.