14 min read
When Lever garbles your US tech resume, export a single-column DOCX, spell every date as Month Year, put job title and employer on plain separate lines, and move Python, AWS, or Kubernetes from a sidebar into the body text. Don't trust the designed PDF that looked sharp on your screen. Re-upload once, read the Lever application preview line by line, then submit. That's the fix most qualified engineers skip because the file looked fine locally. It won't fix a weak posting match, but it stops a strong resume from looking empty.
You're not losing because you lack projects. You're losing ground when the importer drops React, Postgres, or contract dates and a recruiter sees a half-empty profile. Before you send another application, check your resume for free with the posting pasted in. The checker flags whether your stack tags still sit in readable lines.
Job hunting in Austin, Seattle, or remote US tech is draining enough. You don't need a lecture on personal branding. You need a resume layout that survives Lever import and still reads like an engineer wrote it. I've screened US tech files in Lever where the preview showed half the stacks the PDF carried.
Quick Wins
- Single column. No skill tables in the margin.
- Month Year on every role. Same format throughout.
- Posting keyword in bullet one under your current job.
- Read the Lever application preview before you click Submit.
What Lever does to US tech resumes before a recruiter opens them
Lever does not read your resume like a hiring manager skimming pull requests. It chunks the file into employer, title, start date, end date, education, and bullet text. US tech resumes often arrive with two-column headers, GitHub links in icon rows, and stack tags tucked in text boxes. The parser reads those blocks out of order or drops them.
The application preview is the resume recruiters screen. When Kubernetes vanishes from Skills and lands nowhere, or your contract stint shows as a blank employer line, you look underqualified next to a candidate with a boring layout and the same tools spelled in plain text.
Tech hires sit in an awkward spot. You're expected to show craft, but the first gate is a parser built for plain Word files. A dark-mode sidebar that works on PDF often scrambles dates on import. So does a Figma template with invisible tables holding contact details.
Mid-level and senior engineers carry enough roles that date drift matters. Four years as Backend Engineer at one SaaS shop plus a startup step-up is a story. When Lever merges both into one undated block, the recruiter sees flat tenure instead of scope growth.
Stack names make it worse. Python, AWS, React, Postgres, and Terraform need to sit next to the job where you used them. A Skills cloud at the bottom is where parsers leave keywords when the Experience section used tables for layout.
US norms add small friction. You might list a bootcamp beside a CS degree. You might call a role Staff Engineer while the posting says Senior Software Engineer. None of that is fatal if the body text is single column and headings match common strings: Experience, Education, Skills.
For keyword placement after layout is clean, read how ATS matches resumes to job descriptions . Parsing fixes come first. Matching language second.
When Lever asks for a cover letter, draft one with the cover letter generator using the same job description. Repeat employer names and date strings exactly as they appear in Experience so nothing contradicts the parsed resume.
Six steps to clear ATS resume errors Lever US tech jobs throw up
Work through layout before you rewrite bullets. One pass on structure saves a night of keyword tweaking that the importer never reads.
Step 1: Strip columns and tables from the master file
Open the Word or Google Doc source, not the PDF you sent last month. Delete sidebar skill grids, two-column contact rows, and text boxes around your summary. Contact details belong in the body: name, city, phone, email, one plain GitHub line.
If you only have a designed PDF, rebuild in Word before you apply again. Copying text into a new doc often leaves hidden table cells that Lever still reads as separate blocks.
Step 2: Lock Month Year dates on every role
Pick one format: January 2022 to Present, or Jan 2022 to Present. Use it everywhere. Mixed 01/22, 2022, and Present on the same page tells the importer three different stories.
Put employer on one line, title on the next, dates on the third. Avoid cramming title and company into one cell separated by a pipe unless both strings are plain text outside a table.
Step 3: Backend engineer at a US SaaS company
Posting wants Python APIs, Postgres, and on-call ownership for a Lever employer in San Francisco.
Before: Two-column PDF from a design tool. Skills sit in a right rail with Python and AWS icons. Dates show as 01/20 and Present in mixed formats.
After: Nimbus Analytics, San Francisco. Backend Engineer | January 2020 to Present. Built Python REST services handling 2.1M daily events; cut p95 latency 18% after Postgres index pass in Q3 2025. Software Engineer | June 2017 to December 2019. Owned on-call rotation for billing API; reduced Sev-2 pages from six monthly to two through runbook updates.
Step 4: Full-stack engineer after agency contract
Posting lists React, Node, and AWS for a fintech using Lever in New York.
Before: React and Node buried in a Skills table. One employer line reads Client Project with no dates.
After: LedgerPath Inc, New York. Full-Stack Engineer | March 2023 to Present. Shipped React checkout flows on Node microservices; held AWS spend flat while traffic rose 24% in 2024. Full-Stack Engineer (via Apex Talent, converted March 2023) | August 2021 to February 2023. Delivered KYC dashboard in React for two fintech pilots; average engagement nine months per client.
Step 5: DevOps engineer with stacked internal title
Posting wants Terraform, Kubernetes, and CI/CD pipeline ownership.
Before: DevOps Engineer listed twice under one date range with identical bullets copied from the junior stretch.
After: StreamVault, Austin. Senior DevOps Engineer | May 2022 to Present. Led Terraform modules for EKS clusters across three regions; cut deploy time 22 minutes to nine in 2024. DevOps Engineer | August 2019 to April 2022. Built GitHub Actions pipelines for twelve services; held change failure rate under 4% through automated smoke tests.
Step 6: Export, preview, fix gaps, submit once
Save as DOCX when Lever allows it. Upload, then open the application preview. If employer blocks are blank or bullets merged, fix the source file and upload again. Don't stack five versions in one day; fix the master and send one clean file.
Spell employers the way the careers site does. Recruiters notice when your resume says StreamVault while the form auto-filled StreamVault Inc from an old parser read.
Copy-paste block: US tech resume skeleton for Lever
YOUR NAME
City, ST | phone | email
GitHub: github.com/yourhandle
Summary
Two lines max. One posting keyword in sentence one.
Experience
Employer Name, City
Job Title | Month Year to Present
• Posting keyword in first eight words + measurable outcome
• Stack name (Python, AWS, React) tied to result
Earlier Title | Month Year to Month Year
• Junior-scope bullet with metric
Education
Degree, University | Year
Skills
Plain comma list only if tools are not already in Experience bullets
Export that skeleton from Word, not a design tool, when Lever offers DOCX upload. If you're PDF-only, print to PDF from Word so the text layer stays selectable. Scanned exports fail before a human opens the file.
For file-type questions after you flatten layout, see PDF vs Word resume for ATS . The same rules apply to US tech uploads even when the portal label says resume.
When a plain tech resume still fails the Lever preview
Exceptions matter because engineers are told to stand out visually. Sometimes the fix is not more design. It's knowing which rules bend and which ones don't.
Portfolio links only in a header icon row. Parsers skip icon links. Put one plain URL on its own line under contact details: Portfolio: yoursite.dev/projects. Keep case study prose off the resume unless the posting asks for it.
Mixed date formats on one page. March 2022 beside 03/22 beside 2022 tells the importer three different things. Pick Month Year everywhere. Spelling the month avoids US-style confusion on day-first reads.
Creative job titles HR never used. Code Ninja or Cloud Wizard might be your internal string. Mirror the posting title once in parentheses: Senior Software Engineer (Platform Lead). The parser needs a recognisable title line.
Education blocks without plain text. B.S. Computer Science, University of Washington, 2019 is fine. A centred crest image with no text layer is not. Write the qualification in plain text even if you keep a portfolio PDF for human readers.
Keyword stuffing in white font or tiny footer text. Lever still reads hidden strings sometimes, and recruiters flag the file when they open the native PDF. Put each tool once beside the role where you used it.
Edge case: some employers run an older Lever build that strips PDF hyperlinks but keeps plain text. If your preview drops linked repo URLs, paste the URL as visible text once. Don't rely on blue underlined text alone.
Edge case: if you applied through a third-party board that re-uploads your file, the board may compress formatting before Lever sees it. When the preview looks wrong and your source DOCX is clean, re-apply on the company careers site with the same file.
This won't fix applying to roles where you lack must-have stack experience. It stops a qualified US engineer from looking empty because the parser ate the dates.
Test your resume before the next Lever upload
Upload your flattened DOCX and the posting to HireFlow's free ATS resume checker . You'll see whether Experience still carries distinct Month Year ranges and whether stack tags sit in readable lines.
When the role is a stretch but your shipping record is strong, run score your job match after the layout pass. Parsing fixes visibility. They don't invent skills the posting lists in bullet one.
Do this now: Flatten to one column, fix Month Year dates, move Python and AWS into dated bullets, export DOCX, read the Lever preview, then submit once.
What to do now
Avoiding common ATS resume errors in Lever for US tech job applications comes down to boring structure and specific dates. One column, Month Year strings, tools beside the job that used them, and a preview read before Submit.
- Strip tables, icon skill rows, and text boxes from the master file.
- Put posting keywords in bullet one under your current role.
- Label contract and agency blocks with honest Month Year lines.
- Export DOCX from Word when Lever allows it.
- Run a free ATS check after export, not before you fix dates.
Open the posting you want most. Run a free ATS check , confirm the importer shows your latest title and stack tags, and send one clean upload.
Read more
Frequently asked questions
DOCX is the safer default when Lever accepts it. A plain Word file with single-column headings survives the application preview better than a designed PDF exported from Figma or Canva. If the posting lists PDF only, export from Word with standard fonts and no text boxes, then read the Lever preview before you submit.
Page count alone does not break the importer. What breaks it is two-column contact rows, skill tables in the margin, and icons where plain text should sit. A dense two-page resume with clean Month Year dates imports fine. A one-page resume with a sidebar of Python and AWS tags often does not.
Yes, if it sits on its own plain text line under your email, not inside a header icon row. Parsers skip linked icons. Write GitHub: github.com/yourhandle once. Put repo names and languages inside dated Experience bullets where Lever attaches them to roles.
Label contract work honestly: Software Engineer (via TalentBridge, converted June 2024) with Month Year dates on each line. Recruiters flag hidden agency periods. A clean label beats a gap that looks like unemployment when the preview strips your employer block.
When Lever shows a cover letter field, use it. The resume proves tools and dates. A short letter names the product surface the posting wants and repeats employer spelling exactly as it appears in Experience. Mismatched company names between files are a common reason recruiters pause even when parsing looks fine.