The friction is not one thing. It is six stacked things.
Candidates do not hate Workday because it is slow in one way. They hate it because several separate costs compound on a single application. Naming each one makes the workarounds obvious, and stops you from blaming yourself for a process that is genuinely poorly configured.
A new account for every employer.
Workday is sold per employer, and each employer runs an isolated tenant. Creating an account at company A does not carry over to company B. Ten Workday applications means ten separate account creations, ten password resets, and ten sets of recovery questions.
The “My Experience” re-entry trap.
You upload a resume, then re-enter every job by hand because the parser scrambles it. Two-column layouts get flattened, dates disconnect from their jobs, and skills fuse into a single run of text. The resume you provided does not save you the typing it should.
A five-to-seven-page wizard.
Applications unfold across sequential screens: My Information, My Experience, Application Questions, Voluntary Disclosures, Self Identify, and Review. You cannot skip ahead, and a mistake on page two often means backing through pages you already finished.
Custom dropdowns and typeaheads.
Workday uses its own widgets for country, state, job titles, and skills. Generic browser autofill does not recognize them, so even fields that look standard refuse the values your browser already knows.
A session that dies quietly.
About 20 minutes of inactivity ends the session with no countdown, per Workday admin documentation. Step away to look up a date and you can return to a login screen, with your in-progress answers gone.
“Save for Later” you cannot trust.
Save for Later is unreliable across tenants and can reset EEO and custom question sections on resume. It is safer to treat each application as a single sitting than to rely on resuming it later.
The frustration this produces is loud and consistent. On Reddit, one candidate wrote: “Can we all just agree that Workday is literally the worst platform to apply for jobs?… the second I click ‘Apply’ and see it redirect to a Workday portal, I literally just close the tab.” Another replied more bluntly: “I’d rather stay unemployed.” On Blind, the feeling is the same in capitals: “I HATE WORKDAY… EVERYTHING ABOUT IT IS AWFUL.” The per-account problem is captured well by Nelson Figueroa on his blog: “Why do I have to create a separate account for each company that uses Workday?” And Hayden Linder, writing on LinkedIn, names the real cost: “When I see one of those two domains, I close the tab immediately. In the time I would have spent creating an account and filling in my employment history, I can apply to 3 other jobs hosted on Greenhouse or Lever.”
These are forum posts, not survey data. But they describe the same six frictions from different people, unprompted, over years. The pattern is real even if the quotes are anecdotal.
What our testing found, and what it does not prove.
We ran a small private test to put numbers on the complaints: 6 people, 40 applications across Workday, Ashby, and generic web forms. We counted fields per application and how many were left for the candidate to fill manually.
| Platform | Avg fields per application | What we measured |
|---|---|---|
| Workday | 73 (range 57–89) | 86.3% of fields left for manual entry |
| Generic web forms | 29 | Not broken down in detail |
| Ashby | 10.4 | Minimal forms, little manual re-entry |
Workday averaged 73 fields per application against Ashby’s 10.4 and a generic baseline of 29. Worse, 86.3% of Workday fields were left for the user to fill manually, the highest share of any system we tested, and only 8.2% were fillable from known profile data. In plain terms: Workday asks for roughly seven times as many fields as Ashby, and almost none of them come back pre-filled.
Be honest about the limits: this was a small private test, not a controlled study. Six people and forty applications is enough to confirm the direction of the complaints above, not to publish a benchmark. Employer configuration varies wildly, so your Workday applications may have more or fewer fields than ours. Treat the numbers as a description of the problem, not a prediction of your exact experience.
It is this way because Workday is HR software, not a careers page.
The fairest reading is that Workday was not built as a candidate-facing platform. It is an enterprise human capital management suite, sold to employers who need payroll, benefits, and workforce data in one system. Recruiting is one module inside that. According to Workday’s annual report (Form 10-K), the platform serves more than 65% of the Fortune 500, over 11,500 organizations, and 75 million users, the overwhelming majority of whom are employees, not applicants. The application experience is a side door into a system designed for a different audience.
Per-tenant data isolation is an architectural property of how Workday is sold. Each employer’s data lives in its own tenant. That is why an account at one company never carries to another. It is not an employer being awkward; it is how the product is structured.
Where the account screen sits is a choice. Workday’s own best-practice documentation says account creation should come at the end of the process, not the beginning. Many employers simply do not configure it that way, which is why you hit the login wall before you have done anything else.
This matters because it tells you where leverage is. You cannot change the architecture, so per-tenant accounts are a fixed tax you plan around. But the account-at-the-start problem, the wizard length, and the parser failures are configuration and engineering choices that employers and Workday could improve, and that good tooling can work around.
What actually helps, with no tool required.
These workarounds cost nothing and most of the benefit comes from the first three. They do not make Workday pleasant, but they turn a ninety-minute ordeal into something closer to a focused thirty minutes.
- Save each tenant in a password manager. Store the Workday URL and credentials for every employer separately, labeled by company. The account-creation tax is unavoidable, but re-logging-in never has to cost you a password reset again.
- Keep a master-answers document.Pre-write the recurring factual answers in one text file: work authorization, salary expectation, notice period, willing-to-relocate, and a one-line “why this role” you adapt each time. Paste, don’t retype.
- Use a single-column resume with standard headings.Two-column resumes get scrambled by Workday’s parser, dates detach from jobs, and skills fuse together. A single column with “Experience”, “Education”, and “Skills” headings parses far more reliably.
- Try “last application” within the same tenant. If you have applied to the same employer before, some tenants let you start from your last application. This is the one place the per-tenant model helps you: re-entry is lower inside a company than across them.
- Finish in one sitting. Do not trust Save for Later. With a roughly 20-minute session timeout and unreliable saves, the safe move is to open your master answers, block out the time, and submit before you walk away.
- Learn which sections are optional. Skills, certifications, and languages are frequently skippable on Workday. Scan the page for the optional flag before you spend ten minutes re-typing your skills from memory.
- Batch Workday applications together. The first application to an employer costs the most because of account setup and resume re-entry. Applying to three roles at the same employer in one session amortizes that setup cost.
- Use a typed-skills list you can paste. Keep your skills as a plain, comma-separated list in your master document so the skills re-entry step is one paste, not twenty keystrokes.
Autofill extensions do exist for Workday. Tools like Restday, JobFill, and VeloApply can populate some fields, and they genuinely save time on the repetitive contact and work-history sections. But none of them are perfect: they still require you to review every field, they struggle with the custom dropdowns, and a confident-looking wrong value is worse than an empty one. Treat any autofill as a head start, not a replacement for reading the form.
How other application systems compare.
The contrast with Ashby and Greenhouse is not cosmetic. They are purpose-built applicant tracking systems, designed around the candidate experience, not enterprise HCM suites with a recruiting module bolted on. In our data, Ashby averaged 10.4 fields per application with minimal forms and no account required. Greenhouse, which we did not field-count, is typically resume-first with no account and a short form. The difference is visible the moment you click Apply.
| Property | Workday | Ashby | Greenhouse |
|---|---|---|---|
| Account required | Yes, per employer tenant | Typically no | Typically no |
| Avg fields (our test) | 73 (57–89) | 10.4 | Not measured |
| Form structure | 5–7 page wizard | Single short form | Short, resume-first |
| Resume handling | Parser scrambles common layouts | Resume-first, light re-entry | Resume-first, light re-entry |
| Built as | Enterprise HCM suite | Purpose-built ATS | Purpose-built ATS |
This is why a candidate’s instinct to close the Workday tab is rational, not lazy. The same fifteen minutes yields roughly one Workday application or three Greenhouse or Lever ones. If you are job-hunting under time pressure, prioritizing non-Workday roles is a legitimate strategy, not a sign you are avoiding hard work.
If you are building or choosing an autofill tool.
Workday is the hardest common target for autofill, so it is a useful stress test for any tool. The features that matter here are the ones that handle Workday’s specific widgets and fail honestly when they cannot.
Visible review states that separate filled, needs-review, and left-for-you fields; per-tenant credential handling that treats each employer as a distinct login; a resume-parser-aware matcher that maps your history to Workday’s My Experience rows; and a hard rule against auto-submitting, so you always press the final button yourself.
Silent guesses that fill a plausible-looking but wrong value; any tool that submits on your behalf; tools that store or read passwords, CAPTCHA, payment data, or national IDs; and any claim to have “solved” Workday without showing how it handles the custom dropdowns and parser failures.
Jobsistant’s Workday support is in development and has not shipped. The principles above, reviewed autofill with visible uncertainty and no auto-submit, describe what we are building toward, on Workday and every other platform. Nothing here is a claim that the product handles Workday today.
The whole workflow in five moves.
One password-manager entry per employer
One master-answers text file
A single-column, standard-heading resume
Finish each application in one sitting
Review every autofilled field before submit