What Workday does with your resume the second you upload it

Short answer: it copies what it can into the form fields, deliberately skips two of them, hands the half-filled form back to you to correct — and at some employers it does not run at all, because the employer turned it off.

That last part is the one worth knowing, because it reframes the most common complaint about Workday. When you upload a resume and then find yourself retyping eleven years of employment history by hand, you have usually not hit a broken parser. You have hit a configuration decision made by that company's HR team.

The employer decides whether it runs

Workday's administrator documentation says this plainly: organisations "can configure job application templates to hide resume parsing for external candidates."

Read that again from the applicant's side. The same software, at two different companies, will behave completely differently — one autofills six fields, the other gives you an empty form and an attachment box. Neither is a bug. One employer left parsing on for external applicants and the other did not.

So the variance you have experienced is real, it is not your file, and there is nothing to fix on the applications where the form comes back empty. It is worth knowing simply so you stop attributing it to your resume.

What it fills, and the two it refuses

When parsing does run, Workday "populates fields from a resume" and then "enables you to review the resume data" — the review step is part of the design, not an admission of failure. The parser proposes; you confirm.

The documentation is more specific about what it will not do than what it will. It states that Workday "doesn't auto-fill fields you configure as hidden or these fields: Languages and Skills."

Workday's parsing, as its own documentation describes it

The admin guide names the exclusions explicitly and leaves the inclusions general — which is itself informative about what to check.

	What Workday does	What it means when you apply
Form fields	Populates them, then presents them for review	Proof-read before typing; the review step is by design
Languages	Never auto-filled	Fill it by hand, every time
Skills	Never auto-filled by the parser	Fill it by hand — this is what recruiters filter on
Fields the employer hid	Never auto-filled	You cannot tell which those are; check everything
Consistency	"Results can vary based on resume format and order of words"	A layout problem, not a you problem
Whether it runs at all	The employer's choice, per application template	An empty form may mean parsing was switched off

Languages and Skills being permanently excluded matters more than it looks. Those are exactly the two fields a recruiter filters on. If you skim past them because everything else looked populated, you have submitted an application that is invisible to the filter the recruiter is most likely to run.

"Results can vary based on resume format and order of words"

That is a direct quote from Workday's guide, and it is the most useful sentence the vendor has written about resumes.

Order of words. The parser is reading sequentially. A layout that puts your job title in one visual column and the dates in another produces a text stream where they are not adjacent, and the parser has to guess which date belongs to which role. It guesses wrong in the predictable way: the most recent date attaches to the wrong employer, and your current job appears to have ended in 2019.

Format. The same guide recommends you "use resumes that don't have images or image-based styles." That is not aesthetic advice. An image-based style is a heading rendered as a graphic rather than as text — common in designed templates — and a parser cannot read it at all, so the section under it becomes unlabelled prose.

A Financial Analyst with a two-column template hits both problems at once, and the tell is always the same: the form comes back with a plausible-looking first entry and nothing after it.

The skills suggestion is a separate step

There is a second thing that happens, and conflating it with parsing is why people give contradictory accounts of what Workday does.

After you apply, Workday assesses the content of your application and resume and suggests skills, which you can keep or remove. That is a different mechanism from field parsing — it is a recommendation you get to edit, and it feeds the matching that surfaces you for other roles at that employer.

The practical consequence is a small one that pays off later: read those suggestions before you submit rather than clicking through them. They are how that company's system will characterise you for every future req, and a wrong suggestion you accepted is harder to notice than an empty field.

What to actually do

Two minutes that save twenty

The order matters: check the fields the parser never touches first, because those are the ones a recruiter filters on.

1. 1
   Upload, then stop

   Do not start typing. Read what came back first — you are proof-reading a machine, and it is faster to spot three wrong fields than to re-enter twelve.

2. 2
   Check Languages and Skills

   Workday never fills these. If the form has them and they are empty, that is expected, and filling them by hand is the highest-value two minutes in the application.

3. 3
   Check the most recent role's dates

   This is where column layouts fail. If your current job shows an end date, the parser misread the file.

4. 4
   Read the suggested skills before submitting

   Keep the accurate ones, remove the rest. They persist against your candidate record at that employer.

5. 5
   Leave the attachment alone

   The file itself is what a human opens. The form is how you are searched; the attachment is how you are read.

The account you keep being asked to create

Every Workday career site asks you to create an account, and it is a separate account at every company — your login at one employer is worthless at the next, because each runs its own tenant. This is the single most-complained-about thing about applying through Workday, and the complaint is fair.

It is also worth using rather than resenting, for one reason: the account is where your candidate record lives at that employer, and Workday's Quick Apply populates a new application from your resume, CV or previous applications. The second application to the same company is materially faster than the first, and the fifth is faster still.

That changes the arithmetic on large employers. If a company has forty open reqs you might plausibly fit, the first application is the expensive one and the rest are cheap — which is an argument for applying to several roles at one big employer rather than one role each at several. It is the opposite of the advice people usually give themselves after a painful first form.

The corollary is that a mistake persists. If your first application at a company recorded your current job as ending in 2019 because of a column layout, that error is sitting in the record the next application copies from. Fixing it once fixes it for every future req there, which makes the two minutes of proof-reading on application one worth considerably more than two minutes.

Why the form exists at all

It is worth answering the question underneath the frustration: if they have my resume, why is there a form?

Because a resume is a document and a form is a database row. A recruiter with 300 applicants does not read 300 PDFs — they sort by years of experience, filter by a skill, and check who is authorised to work. None of those operations are possible against an attachment. The form exists because the attachment is unsearchable, and the parser exists to make filling in the form less miserable than it would otherwise be.

Once you see it that way, the priority inverts. The attachment is your best work and deserves the effort you have put into it. The form is data entry, and the only thing that matters there is that it is accurate and complete — a beautifully written resume attached to a record with a blank Skills field and a mangled employment date will lose to a plain resume attached to a correct one.

One caveat on all of this. The documentation quoted here is Workday's administrator guide — written for the HR team configuring the system, not for you. That is precisely why it is worth reading: it describes the behaviour without the reassurance a candidate-facing help page would wrap around it. But it also means each employer's tenant may be configured differently from the defaults, and Workday ships new recruiting features regularly. Treat the exclusions as reliable and the rest as the shape of the thing.

The one thing to get right

Check Languages and Skills on every Workday application, because the vendor's own documentation says the parser will never fill them, and they are the fields a recruiter searches. Everything else on that form is correctable later in a conversation. Those two determine whether the conversation happens.

If you are filling in the same form for the twentieth time this week, HeroApply completes them from your profile — including the fields Workday's parser leaves empty by design.