The Application Portal Reference, One Row per ATS You Clear

You are about to open yet another company's application portal, and before you type a word you want to know what this system will do to your resume and the shortest safe path through its form. This is a lookup, not an argument: find the row for the ATS in front of you, learn what it parses, where it loses data, and how to get through without a dropped job or a validation wall. It is for anyone applying at volume, hitting five or ten portals a week, who is tired of losing an afternoon to a form that eats their work history.

Every other applying guide covers screener questions, file formats, and tracking. None maps the portals themselves, which is where the time actually goes. This reference names each system's parser reliability, its documented data-loss behavior, and the reproducible workaround, organized so you can jump to one row mid-application and leave.

Which ATS is this, from the URL alone

The apply URL's host names the ATS in about thirty seconds, before you commit to anything. Look at where the Apply button points, because the vendor slug sits in that destination URL.

A Workday host looks like acme.wd5.myworkdayjobs.com/en-US/SiteName; a Lever one looks like jobs.lever.co/leverdemo. The pattern holds often enough that one scraper's automatic detection worked for 11 of 14 companies from the domain alone, and a separate test matched the ATS for 11 of 14 career pages.

The catch is the company-branded careers domain. A posting on careers.example.com may embed Greenhouse or Workday behind a custom wrapper, and the host tells you nothing. When the URL is branded, do not assume a custom system. Load the page and view its source for vendor markers; the embedded iframe or script tag usually names the real ATS. Treating a branded domain as bespoke is the first failure mode on this list, and it costs you the chance to prep for the right flow.

Do I need an account, and does it travel

Three of the common portals force you to create a per-employer account whose profile never crosses to another company, and three usually let you apply on a single public page with no registration. This is the first thing to settle, because it decides whether you are filling a form or stuck at a login loop.

Workday runs a separate instance per employer with its own candidate database, so every company you apply to needs a new account and a new application even when they all run Workday. Some employers let you save a profile, but that data stays inside their tenant. Taleo is the same per-employer model, with a sharper edge: re-registering with the same email produces duplicate-account errors that split your application history across two logins. SuccessFactors gates external candidates behind account creation from a blank profile, while internal applicants see their details pre-populated from their People Profile and apply in one or two clicks.

Greenhouse, Lever, and Ashby are typically public single pages. On Ashby an account is usually not required at all, so you can apply without registering. BambooHR collects an application without forcing a cross-employer account.

The practical consequence is that account-based systems tax repeat applicants most. A job seeker hitting five Workday companies builds five profiles from scratch, and if any of them run Taleo, a careless re-signup splits the history. Use a password manager and one consistent email across every portal so the "Forgot username" recovery path always works.

What the parser does to your file, platform by platform

The parser's job and its reliability differ enough that the same resume can sail through one portal and sink in the next. What matters is whether the recruiter reads your uploaded file or screens the parsed fields.

On Workday the structured fields, not the attachment, are the application. Parsing populates fields as a starting point, and Workday's documentation says results vary with resume format and word order, which is why it forces you to confirm. Greenhouse is lighter: in most flows you upload, confirm a small number of auto-filled fields such as name, email, phone, and LinkedIn, then submit, after which the recruiter reads your uploaded PDF directly. Taleo puts the upload first and fills later pages from what it parsed, and its parsing is widely considered weaker than modern systems. Ashby parses to populate the candidate record, but its primary AI surface is criterion-based, returning a Meets or Does Not Meet verdict with cited source text.

This split creates a trap. Greenhouse rewards visual formatting because a human reads the file, while Workday and Taleo punish it because a parser screens the fields. The same two-column resume that reads well to a Greenhouse recruiter interleaves into garbage on Taleo.

Time burn and where the minutes go

Budget for the portal, not the posting. The time sink is almost never the writing; it is manual work-history re-entry and per-role dropdowns when the parser fails.

Workday is a multi-step wizard of roughly six to eight sections, and a single application takes about 30 minutes when the parser fails and you re-enter everything by hand. Taleo asks you to upload your resume and then re-enter every field manually anyway, averaging about 45 minutes. Greenhouse is short because the confirmation set is small and the recruiter reads the file. The difference between a clean flow and a failed one is entirely the parser, which is why format discipline pays off most on Workday and Taleo.

The resume file that parses across all of them

One file format clears every portal on this page: single-column, reverse-chronological or hybrid, with standard headings, a system font, and text-selectable output. In one tester's runs across Workday, Greenhouse, Lever, Taleo, and iCIMS, that format parsed at 95 to 99 percent, while two-column and functional resumes scored far lower, with Taleo and iCIMS two-column rates reported under 50 percent.

The concrete spec: single-column .docx or a text-based PDF, 11 to 12pt in Arial, Calibri, or Times New Roman, 0.75 to 1 inch margins, and standard headers. Use the headings the parser expects, because a resume labeled "Professional Story" offered zero employers to select, and after renaming the section "Experience" with plain-text headings, autofill populated three prior employers. Jobscan's widely cited guidance is that many ATSs struggle to read tables and columns accurately, so single-column is the safer default. Keep DOCX on hand: if a legacy system rejects your PDF upload, DOCX often goes through.

[Full Name]
[City, State] | [email] | [phone] | [LinkedIn URL]

Summary
[Two or three plain sentences, no columns, no tables.]

Skills
[Comma-separated list on one or more lines.]

Experience
[Company] - [Title] - [City, State]
[Start Mon YYYY] to [End Mon YYYY]
- [Bullet, one line, no icons.]

Education
[Degree], [Institution], [YYYY]

Keep a plain-text copy of the same content open while you apply. On Taleo and iCIMS, where parsers scramble fields, pasting from plain text into each box is faster and more reliable than wrestling a mangled auto-fill. Refolk can write that single-column, standard-header base from your own history and tailor it to each posting, which removes the manual reformatting this section asks for.

The procedure: clear the form by the shortest safe path

The method is the same seven moves every time, adjusted at one decision point per platform. Identify the system, settle the account, then commit to parse or manual before you upload.

Sources disagree on step order between parse-first and manual-first. Workday and Ashby docs present autofill as the default, while practitioner guides recommend manual entry when the layout parses badly. The honest reading: let the parser try when your file is clean single-column, and switch to Apply Manually the moment the review page shows scrambled or missing employers. Apply Manually on Workday is a documented first-class option, not a fallback.

On Workday the attachment is not the application, the fields are, which is why confirmation is never optional.

How this goes wrong, and how to check

Most lost afternoons trace to one of eight failures, and each has a reproducible check. This is the section to read before you submit, not after.

Two of these deserve extra weight. First, upload success is not parse success. Greenhouse shows a success message on parse and an "only attached" state when parse fails, so the toast you see may sit over nothing. Always open the next page and confirm your most recent role is present. Second, the Workday review reorder: the review page displays your data in a different order than you entered it, and parser-mangled fields often only become visible there. Read it line by line, because a date that landed on the wrong employer is invisible until you check.

There is also a quieter, machine-level failure. React-based forms, which includes Greenhouse and Ashby, silently wipe programmatically set values, which is why autofill extensions report "rejected" fields. If you use any autofill tool, verify after it fills, because a candidate who pastes, tabs away, and submits can send blank fields without noticing.

Where the friction concentrates, by recruiter supply

You meet Workday's high-friction flow far more often than any other portal, so the time you invest in mastering it pays back the most. In Refolk's index of professional profiles, 644 US-based recruiting and talent-acquisition professionals list Workday as a skill, against 185 who list Greenhouse, roughly 3.5x fewer.

The geographic skew is sharp too: only 22 UK-based recruiters list Workday, roughly 29x fewer than the US figure, which tells you the high-friction, account-based flow is far more of a US-market tax. In the same index, top US employers of Workday-skilled recruiters include Boeing and C&S Wholesale Grocers, while Greenhouse recruiters cluster at Meta, Snowflake, and TikTok. That maps to experience: large, established employers lean Workday or Taleo, where Taleo is reportedly used by over half of Fortune 500 companies, while newer and tech-forward employers lean Greenhouse, Lever, and Ashby.

If you want to understand a specific company's flow before you apply, ask the people who run it.

Keep this current and finish clean

The mechanics here are stable, but any platform can change its parser or its screen layout between the time you read this and the time you apply, so verify rather than trust from memory. The reliable re-check is the review page on an account-based system: upload once, look at how the fields landed, and you will know in under a minute whether this instance parses your file or not. If the latest role is wrong or missing, switch to manual before you invest the thirty minutes.

Run this checklist before you call any application done.

Two habits carry across every portal and save the most time over a batch. Keep a plain-text copy of your resume open to paste from when a parser scrambles fields, and keep a short document of your standard screener answers, work authorization, salary expectation, and how-did-you-hear, so a Taleo timeout never costs you more than a re-login. Tailoring each posting's resume to its exact requirements is the one piece worth automating, and Refolk drafts and scores that fit per posting so you spend your afternoon clearing forms, not rewriting the same file five ways.