Workday is the applicant tracking system behind roughly 60% of Fortune 500 companies and more than 11,000 enterprises worldwide, according to Workday's own 2025 investor materials. If you have ever uploaded a resume only to find every field in the application form auto-filled with scrambled text, truncated job titles, or education dates attached to the wrong school, you have met the Workday parser. Unlike most ATS platforms, Workday does not just scan a resume into a searchable document. It extracts structured data and pre-populates a candidate profile, and whatever comes out of that parse is what the recruiter sees first. This guide covers what Workday's parser actually reads, the specific formatting patterns that break it, and how to structure a resume so the profile you submit is the one the recruiter reviews.

How the Workday Parser Actually Works

Workday's resume parser is a two-stage system. Stage one is document ingestion: the uploaded file is converted to plain text, layout elements are stripped, and the raw text is passed to stage two. Stage two is entity extraction: Workday tries to identify structured fields (contact info, work history, education, skills) and map them to its internal candidate profile schema. The recruiter never sees your original resume in the profile view; they see the parsed data in Workday's own layout. Your PDF is still attached, but screening happens against the parsed fields.

This matters because a beautifully designed resume can parse into a mess, and a plain resume can parse perfectly. Workday is not evaluating your layout, it is evaluating whether it can correctly identify your last three job titles, employers, dates, and degree. If any of those come out wrong, the candidate profile is wrong, and the recruiter is screening a scrambled version of you.

The two-stage parse pipeline
  • Stage 1 (ingestion): File converted to text. DOCX is read natively. PDF is run through a text extraction layer that works reliably for text-based PDFs but fails on scanned or image-based PDFs.
  • Stage 2 (extraction): A named-entity recognition model identifies section headers, employers, dates, titles, and skills. Fields are written to the candidate profile schema.
  • What the recruiter sees: The structured profile first, your original PDF second, and the keyword search results from the parsed text.
The core principle: Workday does not reward clever design. It rewards correctness of extraction. Every formatting decision should be evaluated by one question: does this make the parser more or less likely to identify the field correctly?

File Format: PDF vs. DOCX on Workday

Workday accepts PDF, DOC, DOCX, RTF, and TXT. Based on Workday's public help documentation and widely documented community reports, DOCX has historically parsed more consistently than PDF because the XML structure of a Word document exposes heading levels, paragraph styles, and table boundaries that the parser can use as signals. PDF parsing is reliable only when the PDF was generated from a text source (Word, Google Docs, LaTeX) rather than scanned or exported from a design tool like InDesign or Canva.

File Format Parse Reliability Common Issues Recommendation
DOCX High Style-based layouts work well; rare issues with nested tables Preferred for Workday
PDF (text-based, from Word) Medium-High Reading order can break with multi-column layouts Acceptable if single-column
PDF (exported from Canva, InDesign, Figma) Low Text stored as vector paths, sections parsed out of order Avoid
PDF (scanned image) None No extractable text, profile will be empty Never use
RTF Medium Legacy format, inconsistent style mapping Fallback only
TXT High for content, low for structure No formatting signals at all, relies entirely on NER Last resort
Recommendations based on Workday's public help center documentation and long-standing community reports from Workday-run career sites.

If you are applying to a Fortune 500 company through their Workday portal and can only submit one file, upload DOCX generated from Microsoft Word or Google Docs (File > Download > Microsoft Word format). If DOCX is not accepted, export a single-column PDF from the same source file.

Sections and Fields the Parser Expects

Workday's profile schema has fixed fields. The parser is trying to fill those fields from your resume. If your section headers match the names the parser recognizes, extraction is dramatically more reliable. Use exact, conventional section names and put them on their own line.

Section names Workday recognizes
  • Experience / Work Experience / Professional Experience
  • Education
  • Skills
  • Certifications
  • Languages
  • Summary / Professional Summary
Section names that confuse the parser
  • "Where I've Been" instead of Experience
  • "Academic Journey" instead of Education
  • "What I Bring" instead of Skills
  • "Career Highlights" as a substitute for Experience
  • Merged sections like "Experience & Projects"

Contact information block

Workday's parser looks for contact details in the first 10 to 15 lines of the document. Put your name on the top line by itself, then phone, email, city and state, and LinkedIn URL, each on its own line or separated by a plain pipe or comma. Do not put contact information inside a header or footer region of the document; many Workday tenants strip headers and footers during text extraction, so an email in the header can disappear entirely from the parsed profile.

Work experience block

Each work experience entry should follow a strict pattern so the parser can identify all five fields (title, employer, location, start date, end date). The safest pattern is title on one line, employer and location on the next, dates on the third, and bullets beneath. Write dates in "Month YYYY" format (e.g., "March 2022 – Present") because numeric-only formats like "3/22" can be misread as fractions.

Workday-specific quirk: If you list multiple titles at the same employer as a single entry ("Software Engineer, promoted to Senior Software Engineer"), Workday often captures only the first title and attributes the full date range to it. List each title as a separate entry with its own date range so promotions are preserved in the profile.

Parser Failure Modes: What Breaks Workday

Most Workday parse failures fall into a small number of predictable patterns. Every item below has been documented repeatedly in Workday community forums, Reddit's r/recruiting and r/jobs threads, and Workday's own help center as known issues with specific document patterns.

1. Multi-column layouts

A two-column resume with a sidebar for skills and a main column for experience almost always parses out of order. The text extractor reads top-to-bottom, left-to-right, and concatenates your sidebar content into the middle of your work experience. Use a single-column layout for Workday submissions, period.

2. Tables for layout

Using a table to create a two-column effect (job title left, dates right) can work, but nested tables or tables without consistent row structure frequently cause employer names to be concatenated with dates from the next row. Prefer paragraph-based layouts with tabs or simple indentation. If you must use a table, keep it to a single row per job and avoid merging cells.

3. Text inside images or graphics

Any text embedded in an image (logo, infographic skill bar, custom header) is invisible to the parser. Skill bars and rating graphics are the worst offender because candidates believe they are communicating skill levels while the parser sees nothing at all. Write skills as plain text in a comma-separated list.

4. Decorative fonts and custom typefaces

Fonts not embedded in the PDF can be substituted, and decorative fonts (script, handwritten, display) sometimes cause ligature issues where pairs of letters are read as single characters. Stick to standard fonts: Calibri, Arial, Helvetica, Georgia, Cambria, or Garamond. See our guide on ATS friendly resume fonts and styles for the full list.

5. Headers, footers, and text boxes

Workday often strips headers and footers during parse. Name and contact details in the document header can disappear. Text boxes (which appear in many designer templates) are frequently ignored entirely because they sit outside the main text flow. Keep everything in the main body.

6. Date format inconsistency

"Jan 2020 – Present", "01/2020 - Present", and "January 2020 to Now" can each be parsed differently. Pick one format and use it for every role. The most reliable pattern is "Month YYYY – Month YYYY" with a real en dash or a simple hyphen between them, and the word "Present" (not "Now" or "Current") for ongoing roles.

The Workday Auto-Fill Profile Flow

After you upload your resume to a Workday application, you are taken to a series of pages that pre-populate with whatever the parser extracted. This is the most important moment in a Workday application and the one most candidates skip. Every field on those pages is what the recruiter will see in their dashboard, not your uploaded PDF.

Critical step most candidates skip: Carefully review every auto-filled field and correct any errors before submitting. If the parser truncated your most recent title, moved dates to the wrong employer, or dropped your degree, the recruiter sees the broken version unless you fix it manually in the form.
Auto-fill review checklist
  • Name spelled correctly, email and phone formatted correctly
  • Every work experience entry has title, employer, location, start date, end date
  • Job descriptions are not truncated at 500 or 1,000 characters
  • Education includes degree, school, and graduation year
  • Skills section reflects the skills from your resume, not a random subset
  • No duplicate entries (the parser occasionally creates two entries for one role)

If you find yourself rewriting half the form, that is a signal to go back, fix your resume structure, and re-upload before submitting. The upload step can be repeated until you are satisfied with the parse.

Keyword Strategy for Workday Searches

Workday recruiters search the candidate database using boolean and natural language queries against the parsed text. If a recruiter searches for "Python" and your resume says "Py3" or "python3", you may not match. The keyword list in the job description is the most accurate map of what the recruiter will search for.

For a deep look at how ATS scoring works across the major platforms, see our ATS resume score guide and our explainer on ATS scoring for developers. For Workday specifically, three rules matter most.

1. Spell acronyms both ways

Use "Customer Relationship Management (CRM)" on first mention, "CRM" thereafter. Workday search handles both forms if both are present in the parsed text.

2. Match job description language

If the posting says "Agile scrum," write "Agile scrum" verbatim. Do not paraphrase it to "iterative development methodologies" and expect a match.

3. Skills in the Skills section

Workday's skills field is populated from a dedicated Skills section on your resume. Bullets inside work experience contribute to keyword search but not to the structured skills field on the profile.

Workday-Ready Resume Checklist

Use this pre-submit checklist before uploading to any Workday portal. It captures the formatting rules that matter most for a clean parse.

Pre-upload checklist
  • Single-column layout, no sidebars
  • Standard section headers: Summary, Experience, Education, Skills, Certifications
  • File saved as DOCX (preferred) or single-column text-based PDF
  • Contact info in the body, not in a header or footer
  • One title per work entry (promotions listed as separate entries)
  • Dates in "Month YYYY – Month YYYY" format, "Present" for current role
  • No tables with merged cells, no nested tables, no text boxes
  • No skill bars, rating graphics, or icons containing text
  • Standard fonts only: Calibri, Arial, Helvetica, Georgia, Cambria, Garamond
  • Keywords from the job description present verbatim
  • Acronyms spelled out on first mention
After upload: Always review the auto-filled profile and fix any extraction errors before hitting submit. The profile is what the recruiter sees.

Workday is one of the "big three" enterprise applicant tracking systems alongside Oracle Taleo and Greenhouse. Each parses resumes differently and rewards different formatting decisions. If you are applying to roles across multiple systems, these companion guides cover the other two.

Taleo Resume Format Guide

Oracle Taleo dominates enterprise and legacy Fortune 500 tech stacks. Known for its aggressive copy-paste-to-form flow and keyword density quirks. Read the Taleo resume format guide.

Greenhouse ATS Resume Guide

Greenhouse is the default for mid-market tech companies and is generally more parser-friendly than Workday or Taleo. Read the Greenhouse ATS resume guide for the differences.

For a broader selection of parser-tested templates you can download and adapt, see our roundup of the best ATS friendly resume templates.

What to Do Next

Before you submit your next Workday application, run your resume through an ATS scoring tool to confirm it parses cleanly. Our free ATS resume checker extracts your resume exactly as a parser would, flags formatting issues that break Workday ingestion, and compares the extracted content against the job description for keyword coverage. If the checker cannot find your most recent job title, Workday probably cannot either.

Check my resume against Workday

Frequently Asked Questions

Workday accepts both, but DOCX has historically parsed more consistently because Word's XML structure exposes paragraph styles and heading levels the parser can use as signals. Text-based PDFs exported from Word or Google Docs work nearly as well. Avoid PDFs exported from design tools like Canva, InDesign, or Figma, because those store text as vector paths and frequently parse out of order.

The most common causes are multi-column layouts (sidebars that get concatenated into the main column), tables used for layout with merged cells, text boxes that sit outside the main text flow, and contact information placed in a document header or footer that Workday strips during ingestion. Switching to a single-column layout with standard section headers fixes most scrambling problems.

You cannot skip it, and you should not want to. The auto-filled candidate profile is what recruiters see first in their dashboard. Your original PDF is still attached, but screening happens against the parsed fields. If you submit without reviewing and correcting the auto-filled fields, you may be screened on a scrambled version of your resume.

If you list multiple titles as a single combined entry (for example, "Software Engineer, promoted to Senior Software Engineer, 2020 to 2024"), Workday's parser often captures only the first title and attributes the entire date range to it. To preserve promotion history, list each title as a separate work experience entry with its own date range, even if they share an employer.

Workday boolean and keyword searches run against the parsed text of your resume, which populates both the structured profile fields and a searchable text index. Your uploaded PDF is attached to the profile but is not the primary search target. This is why keyword coverage in the parsed text matters more than the visual design of your PDF.

No. Skill rating bars, circles, and progress indicators are graphical elements with no extractable text. The parser sees nothing in the space where the bar appears, and the skill associated with it is often lost as well. List skills as plain text in a comma-separated list inside a dedicated Skills section.

Use conventional section names: Summary or Professional Summary, Experience or Work Experience, Education, Skills, Certifications, and Languages. Avoid creative substitutions like "Where I've Been" or "Academic Journey" because they fail to map to the parser's expected schema. Put each section header on its own line with no other text.

Related Articles

Taleo Resume Format Guide: Fields, Keywords, and File Types | Resume Optimizer Pro
Taleo Resume Format Guide: Fields, Keywords, and File Types

How Oracle Taleo parses resumes. The paste-to-form flow, keyword density ranking, file types, and the section headers Ta...

Read More
Greenhouse ATS Resume Guide: What the Parser Sees | Resume Optimizer Pro
Greenhouse ATS Resume Guide: What the Parser Sees

How Greenhouse parses resumes, why it is the friendliest of the big three enterprise ATS platforms, and the specific pat...

Read More
9 Free ATS Resume Templates (.docx) Tested on Workday and Taleo (2026) | Resume Optimizer Pro
9 Free ATS Resume Templates (.docx) Tested on Workday and Taleo (2026)

Download 9 free, ATS-tested resume templates in .docx format. Each template was parsed through Workday, Taleo, and Green...

Read More