12 min read
All three parsers strip your resume to plain text first. They're not judging your template. Workday maps that text into enterprise profile fields and punishes header contact blocks hardest. Greenhouse tolerates varied section labels but doesn't forgive two-column rows. Lever keeps employer lines intact when dates sit on the same line as titles. One single-column DOCX with Month Year dates beats a designed PDF here.
Check your resume for free before you pick a portal. You're not choosing a winner among ATS brands. You're choosing a file shape that survives whichever link the job posting sends you to. We'll compare tables, section headers, date formats, and PDF vs DOCX so you know what each system reads differently before you upload.
Workday shows up at Fortune 500 employers and large hospitals. Greenhouse and Lever dominate US tech and growth-stage companies. The recruiter screen looks different in each tool. The parser step is similar: extract text, guess field boundaries, store a searchable profile. Where they disagree is what breaks first when your layout isn't boring anymore.
Job searching across multiple ATS portals is draining. This won't fix applying to roles where you're missing core requirements. It stops a qualified file from dying because Workday dropped your phone number or Greenhouse attached your dates to the wrong employer. That's the workday vs greenhouse vs lever parsing gap in one sentence: same file, different broken field.
Quick Wins
- Paste your PDF into Notepad. No selectable text means fix the export before any portal sees it.
- Use Work Experience, Education, Skills as plain headers. Fancy labels cost you in Workday filters.
- Put Company, Title, and Month Year on consecutive lines. Tables and side columns split employers in Greenhouse.
Why Workday, Greenhouse, and Lever read the same file differently
Every upload starts as a text extraction job. None of these platforms reward design. They reward reading order. Workday pushes parsed text into structured candidate profiles built for compliance-heavy employers. Greenhouse and Lever surface a cleaner recruiter view with faster keyword search, but they still read left to right, top to bottom, like a typewriter.
The shared rule: if two pieces of information sit in separate layout boxes, the parser may never pair them again. Your job title and your dates are married on the page. The ATS does not know they're related unless they land on adjacent lines in the extracted text.
Recruiters filter parsed fields before they open attachments. A missing current employer in Workday can hide you from a headcount report. A Greenhouse keyword search on Salesforce won't find a skill trapped inside a graphic. Lever recruiters often scan the parsed timeline first, then click through to a portfolio link if extraction caught it.
Workday vs Greenhouse vs Lever parsing: field-by-field contrast
The table below is what changes in US screening when the same resume hits each parser. These are layout outcomes, not ranking scores. No ATS publishes a secret pass rate.
| Element | Workday | Greenhouse | Lever |
|---|---|---|---|
| Table layouts | Often drops right-column dates; nested tables scramble order | Splits company from title when columns divide the row | Reads tables as plain lines but may orphan date cells |
| Section headers | Expects Work Experience and Education; nonstandard labels may parse as body text | Accepts Professional Experience or similar; still prefers plain bold lines | Flexible on labels; inconsistent headers can merge sections |
| Date formats | Month Year most stable; mixed 06/19 and 2019-06 on one file breaks tenure fields | Same Month Year pattern; date ranges in footers often vanish | Handles Month Year well; functional resumes lose dates when blocks are skill-first |
| PDF vs DOCX | DOCX from Word safest; image PDFs parse empty in strict tenants | Both accepted; preview pane is the truth test | Both accepted; hyperlinks in PDF usually survive when text is selectable |
Read resume formatting errors that break ATS parsing for layout failures that hit every platform. This page is the three-way split once your file is already single-column.
Edge case: you already applied in Greenhouse and the same company posts a role in Workday after an acquisition. Reuse the flattened file, not the old two-column template. Merger stacks often add Workday parsing rules overnight. Edge case two: a referral link pre-fills Greenhouse while your resume still carries a footer phone number Workday will ignore. Put contact info in the body for the Workday version even if Greenhouse caught it last time.
Some employers ask for a cover letter in the same portal. If the posting mentions one and the form allows upload, generate a cover letter from the same employer names and dates as your resume so the parsed record stays consistent.
Where each parser breaks first (and the exceptions)
The pattern: the resume looks fine in Preview on your laptop. The parsed profile is missing a current title. The fix is never keyword stuffing. It is flatten layout, standardize dates, and re-upload until the preview matches.
Workday: headers, footers, and enterprise field mapping
Workday tenants love contact data in the document body, not the Word header or footer. Phone and email in the header bar often never reach the parsed contact block. Recruiters running compliance reports then see an incomplete profile before they read bullet one.
Before: Name and email in the Word header; jobs in a three-column table with dates right-aligned.
After: Name, phone, email, city on line one through four in the body. Acme Corp, Operations Analyst, Jan 2021 to Present, then bullets on plain lines below.
Exception: some Workday career sites offer a manual profile editor after upload. If you see editable fields, fix employer and date rows there before submit. Do not treat that screen as permission to keep a table resume. The recruiter's default view still shows the broken parse.
Greenhouse: two-column rows and preview trust
Greenhouse is the system where recruiters most often quote the parsed preview back to candidates. When the left column lists employers and the right column lists dates, extraction reads across the row. Your 2023 title can inherit a 2019 end date from the row above.
Before: Sidebar skills column beside a narrow experience column; dates floating in the margin.
After: Skills section below experience as a simple comma list or bullet block. Each role block: Company, Title, Jun 2020 to Aug 2023, bullets.
Exception: Greenhouse sometimes maps a labeled Skills section cleanly even when experience tables fail. That is not a reason to keep columns in experience. Keyword filters still run on job bullets first. A skills sidebar does not replace a precise bullet under your current role.
Lever: functional layouts and PDF hyperlinks
Lever handles hyperlinks in text-based PDFs better than most peers when portfolio URLs sit on the contact line. Functional or skills-first resumes are where Lever struggles. Dates detached from employer names produce empty tenure fields even when the skill keywords extract fine.
A career-change candidate with a Skills Summary block above a sparse job list often sees perfect tool tokens and blank years. Recruiters scanning tenure assume a gap you did not have. Chronological blocks with Month Year on every role fix that in Lever before you argue about keyword match.
Exception: Lever's upload preview is not enabled on every employer config. When preview is missing, run the Notepad paste test and apply from desktop. Mobile uploads skip the check you need most.
PDF vs DOCX across all three
DOCX exported from Word or Google Docs is the default safe choice when the posting accepts both. Text-based PDF from the same source usually parses identically. Designed PDFs from layout tools, Canva, or Illustrator often fail the Notepad test. Workday empty-parse cases are the harshest. Greenhouse and Lever may show partial text with employers out of order.
Scanned paper resumes are image files. OCR in portals is inconsistent. Type the document. Do not photograph it. File names with emoji or version strings like final_v9 sometimes fail on older browsers. Use Firstname-Lastname-Resume.docx or .pdf.
I've screened the same attachment in Workday and Greenhouse the same week; the parsed employer order never matched the PDF line for line. That is normal. Your goal is complete fields, not pixel-perfect layout in the ATS.
What to do now: one export that survives all three
You don't need three resumes. You need one flattened master file, then bullet-one tweaks per posting. Run these four checks in order before you click apply on any Workday, Greenhouse, or Lever link.
Step 1: Pass the Notepad test
Open your export. Select all text. Paste into Notepad on Windows or TextEdit plain mode on Mac. Employers, titles, and dates should appear in reading order with no huge gaps. If paste fails, flatten columns and remove text boxes before any portal sees the file.
Before: Canva PDF with skill icons. Notepad shows random words and blank lines.
After: Word DOCX, 11-point Calibri, single column. Notepad shows Bright Labs, Product Manager, Mar 2022 to Present on consecutive lines.
Step 2: Standardize headers and dates
Use Work Experience, Education, and Skills as plain bold lines. Pick Month Year for every role: Jan 2022 to Present, not 01/22-Present mixed with 2022-January. Put the date range on the same line as the company or directly under the title. Never in a far-right column or footer.
Step 3: Choose PDF or DOCX from the preview
Upload to the portal you're using. Read the parsed preview when the employer enabled it. If employers scramble, switch from PDF to DOCX or the reverse, then re-upload. Submit only when company rows and date ranges align with your source file.
Tailor bullet one under your current role so a required tool from the posting lands in the first eight words. That helps keyword search in Greenhouse and Lever the same way it helps Workday filters. Skills list repeats are backup, not the main signal.
Step 4: Mirror form fields to the resume
Legal name, email, phone, and work authorization in the portal should match the resume header exactly. Mismatches flag manual review. Custom questions about start date or salary write to the same record as parsed text. Answer directly. Blank required fields block submit or save incomplete profiles recruiters cannot filter.
Copy-paste universal parser checklist
Run this list beside the open careers page before submit:
[ ] Notepad paste shows employers and dates in order
[ ] Contact info in body, not Word header/footer
[ ] Work Experience / Education / Skills as plain headers
[ ] Month Year dates on every role, one style only
[ ] No tables, text boxes, or two-column layout
[ ] Portal preview shows intact employer rows (or Notepad passed if no preview)
[ ] Bullet one names a required tool from the posting
[ ] Form name and dates match the attached file
Edge case: you're batching five applies across mixed ATS links in one evening. Save one master DOCX and five bullet-one variants with company slugs in the filename. Cross-uploads happen when tabs multiply. Edge case two: internal transfer portals in Workday sometimes skip resume upload entirely. Still keep a parser-safe file ready; hiring managers often request it later in the workflow.
Test the file before the portal upload
Run the export through a checker with the job description pasted in. You're confirming table and column warnings are gone, not chasing a perfect score. Fix missing employers and header/footer contact issues first.
Run a free ATS check on the DOCX or PDF you'll attach. If warnings mention tables, columns, or missing employers, fix those before Workday, Greenhouse, or Lever sees the file. Then score your job match against the posting to confirm bullet one carries a skill the description repeats.
Edge case: the posting does not say which ATS powers the link. You still win with the same boring file. Parser differences matter at the margin, not as an excuse to keep a designed template.
Pick your export and apply once
Open your master resume. Paste it into Notepad. If text copies cleanly, standardize headers and Month Year dates, move contact info into the body, and kill every table. Upload to whichever portal the posting uses. Read the preview. Submit once when employer rows match.
Workday vs Greenhouse vs Lever parsing differences show up at the margins: header contact in Workday, column splits in Greenhouse, functional date gaps in Lever. The universal fix is the same boring single-column DOCX with plain section labels. Fancy layout is not a flex when the recruiter's first screen is extracted text.
Keep a confirmation screenshot after submit. If you don't hear back in two weeks, you still know the parser saw the employers and dates you intended. That beats wondering whether a right-aligned date column attached your current title to the wrong company in Greenhouse.
Batch similar roles the same evening if you want momentum. Swap bullet one per posting. Don't swap filenames in a hurry and upload the wrong company's version. Name files with the employer slug before you open the first careers tab.
And if preview fails twice on the same template, stop applying with that file. Flatten the doc, re-export, and test again. Third time is not lucky on parser errors. Fix the layout, then submit once the preview or Notepad paste is clean.
Read more
Frequently asked questions
Workday is usually the least forgiving with table layouts because enterprise tenants map parsed text into rigid profile fields. A row with company in the left cell and dates in the right cell often becomes two unrelated lines. Greenhouse and Lever still break on tables, but Greenhouse sometimes keeps the company name while dropping the date. Flatten every role to plain lines: Company, Title, Month Year, then bullets.
Upload whichever format produces selectable text when you highlight it in the portal preview. DOCX exported from Word is the safest default across all three when you do not know the employer config. Text-based PDF from Word usually matches DOCX. Designed PDFs from layout tools often parse as images. If the preview shows scrambled employers, switch formats before submit.
Yes, but Greenhouse and Lever forgive more variation than Workday. Workday recruiters often filter on standard Experience and Education blocks. Labels like Professional Journey or Where I Worked may still parse as body text without a clean section break. Use Work Experience, Education, and Skills as plain bold lines. Avoid icons or colored bars as section dividers.
Month Year on one line with the employer block is the most reliable pattern: Jan 2022 to Present or June 2019 to March 2023. Mixed numeric formats like 06/19 and 2019-06 on the same file confuse tenure fields. Pick one style and apply it to every role. Put the date range on the same line as the company name or directly under the title, never in a far-right column.
One boring single-column file can pass all three when text is selectable, headers are standard, and each job block is plain lines. You do not need three versions unless you are optimizing bullet one per posting. You do need to verify the upload preview in whichever portal you are using. A file that parsed cleanly in Lever last month can still break in Workday when contact info sits in the Word header.