Greenhouse vs Workday Resume Parsing: What Differs and What Works on Both

Correction, 17 October 2026. Earlier versions of this article said we ran the same resumes through both Greenhouse's and Workday's parsers, and reported side-by-side results (an unnamed Workday record, a "64% match" in Greenhouse), market-share and Fortune 500 figures, which employers use which system, and descriptions of each vendor's internal software, including a claim that Workday uses the Aspose library. We have no records of that test, the figures had no source, and we do not know what software either vendor runs, so we have removed them. We have never submitted files through Greenhouse or Workday. This version covers what you can see as an applicant, how text extraction works, and one format that reads cleanly anywhere.

Greenhouse and Workday are two of the applicant tracking systems you are most likely to meet when applying to established companies. People often ask which one is "stricter" and whether a resume needs to be tuned for each. The honest answer: the visible differences are in the application flow, not in anything either vendor publishes about its parser, and one well-built resume works for both.

Why these two come up so often

Workday is widely used by large employers, and Greenhouse is common among technology and fast-growing companies. Many other employers run Oracle Taleo, iCIMS, Lever, SAP SuccessFactors or others; Taleo is covered in how to get your resume past Taleo. The broader point, that nearly all Fortune 500 companies use an ATS, is why formatting for the parser matters at all.

You can usually tell which one you're in from the application address: myworkdayjobs.com for Workday, boards.greenhouse.io or job-boards.greenhouse.io for Greenhouse.

What differs, from the applicant's side

Neither vendor publishes how its resume parser works, and we haven't tested either one. What any applicant can see is how the application itself works, and that does differ:

Workday career sites usually ask you to sign in or create an account, then offer to fill in your profile from your resume. You step through several pages (contact details, work history, education, and so on) and review what was pre-filled before you submit. Exactly which steps appear depends on how the employer has set it up.

Greenhouse job boards usually show a single application page: your details, a resume upload, sometimes a cover letter and a few questions set by the employer. Some forms also offer to autofill fields from your resume.

The practical consequence: on Workday, you often see what the parser made of your file. If your job titles land in the wrong boxes or dates go missing, that is a direct sign the file is hard to extract, and you can correct the fields before submitting. On a Greenhouse form you usually see less of that, so it pays to check the file before you apply.

What both have in common: text extraction

Whatever happens inside each system, every resume parser starts the same way: it pulls the text out of your file. That step is where most formatting problems start, and it works the same in principle everywhere:

1. Text is read in the order it sits in the file, not the order your eye follows on the page. In a two-column design, the sidebar can come out first or be interleaved line by line with your work history.
2. Headings help the software find sections. "Experience", "Education" and "Skills" are easy to recognize; "Where I've Made an Impact" is not.
3. Fields are worked out from the text: job title, company, dates, bullets. If the order is broken, the fields are wrong.
4. Images have no text. A name drawn as a graphic, or a scanned PDF, gives a text parser nothing to read.

Some parsers are cleverer than others at recovering from a messy layout, but you can't know which one a given employer runs or how it is configured. The safe move is to give any parser clean text.

What we have seen in our own parser

We can't show you Greenhouse's or Workday's output. We can show what designed files do in our own parser, which uses pdf.js-based text extraction:

• In our Canva-style resume test, a sidebar design scored 80/100 in our scanner. The sidebar was read before the work history, icons turned into stray characters, and a languages table glued into "EnglishNative".
• In our six-layout benchmark, the same resume in two columns was the only layout to draw a critical reading-order flag.
• In our ChatGPT and Claude resume test, AI tools' own PDF exports of a resume with a skills table scored 84 to 85 with glued cells; the same content as a Word file scored 99 to 100.

In each case the words mostly survived. What broke was order and the boundaries between words, which is exactly what any system that fills profile fields from your text depends on.

What this means for your resume

Don't try to tune a resume for one system. Build one file that gives any parser clean text:

1. Single-column layout only. Two columns are the most common cause of scrambled reading order.
2. Name as plain text on line 1. Not rendered as an image or styled graphic.
3. Standard section headers. "Experience", "Education", "Skills". You lose nothing by using the common words.
4. Skills as comma-separated text, not a visual grid with dots or bars. "Python, Java, SQL" survives extraction; a glued "PythonJavaSQL" won't match a search for "Python".
5. Dates next to the job title and company. Don't put dates in a sidebar away from the role they belong to; reading order can attach them to the wrong job.
6. Plain bullet characters (- or •). Icon-font bullets can turn into stray characters.
7. Built in Microsoft Word or Google Docs, exported as PDF, or submitted as .docx. Heavily designed templates are the files most likely to extract out of order.
8. Standard fonts. Calibri, Arial, Garamond, Times New Roman, Cambria. Unusual display fonts can extract as the wrong characters.

The same rules apply on the other major ATSes too: Lever, Taleo, iCIMS, SAP SuccessFactors, SmartRecruiters and Ashby. None of them can be promised a perfect parse, but clean text is the best start in all of them.

The format that works on both, what it looks like

A resume that gives Workday, Greenhouse and any other parser clean text:

• One column, top-to-bottom flow.
• Name in plain text, 14–18pt, on line 1.
• Contact info on lines 2–3: email, phone, city, LinkedIn. In the body, not the page header.
• "PROFESSIONAL SUMMARY" or "SUMMARY" section header.
• "EXPERIENCE" or "PROFESSIONAL EXPERIENCE" section header.
• Each role: Job Title | Company, Location | Date Range, with a bold title.
• Bullets with - or • under each role.
• "EDUCATION" section header.
• "SKILLS" section header with skills listed as a comma-separated line, not a visual grid.

It looks less striking than a designed template. But the text a system extracts from your file, and the fields it fills from that text, are what recruiters search and often read first. A plain file keeps those clean. Keep a designed version for people: networking, interviews, email.

What about non-PDF formats?

Both Workday and Greenhouse application forms commonly accept .docx and .pdf, and some accept .doc or .txt; the accepted types are listed on each form. In general:

1. .docx keeps text in reading order by design, so it is usually simple to extract from. In our ChatGPT and Claude test, the Word version of a skills-table resume scored 99 to 100 in our parser while the tools' PDF exports scored 84 to 85.
2. Text-based .pdf (exported from Word or Google Docs) extracts cleanly if the layout is simple.
3. Image-based .pdf (scanned, or "save as image" exports) has no text layer. A text parser gets nothing; only OCR could recover it, and you can't count on that.
4. .txt extracts perfectly but loses all formatting, so it reads poorly when a person opens it.

If the form allows both .docx and .pdf, either is fine when the file is clean. If you send a PDF, export it directly from Word or Google Docs; don't print to an image, flatten, or compress to "minimum size".

How to check your resume before you apply

ATS Verification runs your resume through our own parser, not Workday's or Greenhouse's, and shows the extracted text and the structural problems it finds, such as reading-order scrambles, glued words, a missing name or contact details in the page header. That tells you whether the file itself gives a parser clean text. The checks are explained on the methodology page.

For more on each platform: see our Workday ATS guide, Greenhouse ATS guide, and Lever ATS guide. For Workday's PDF handling specifically, see Will Workday Read My PDF Resume? and the 12 patterns that commonly break Workday applications. And for how recruiters sort and review you inside these systems, see the recruiter's view of Workday, Greenhouse, Lever and Ashby.

The cleanest summary

We can't tell you exactly how Greenhouse and Workday differ inside, and nobody outside those companies can verify it either. What we can say: both start by extracting the text from your file, and a single-column, plain-text-formatted resume with standard headings gives that step clean input. Anything fancier adds risk on whichever system you meet.

If you've been applying without callbacks, check the file before you assume it's your qualifications. The fix is mechanical: rebuild the structure once, then every application you send starts from a clean file.

Quick action steps

1. Check your current resume free with a scan and read exactly what our parser extracts.
2. If the scan flags a two-column layout, a name it can't find, or glued skills, fix those first. They are structural and will follow you to every system.
3. Build in Word or Google Docs: single column, standard fonts, plain bullets.
4. If you don't want to rebuild manually, our $5 ATS-safe Rebuild produces a clean single-column .docx with your same content.
5. Re-scan the rebuilt resume and read the extracted text before re-applying. On Workday, also check the pre-filled fields before you submit.

→ See what a parser reads from your resume, free