ATS · 7 min read

Workday vs Greenhouse vs Lever vs Ashby: what each ATS means for you as a candidate

Advice about applicant tracking systems usually treats them as a single entity — “the ATS” — which is why so much of it is unhelpful. The systems behave quite differently from a candidate's side, and the differences are practical rather than theoretical: how long the form takes, whether you need an account, whether your uploaded resume is parsed accurately, and whether the autofill you're relying on works at all. Recognising which one you're in changes how you should approach it.

You can usually identify the system from the URL before you start. An application hosted at a boards.greenhouse.io address, or embedded in a company page but posting to Greenhouse, is Greenhouse. Lever applications sit on jobs.lever.co. Ashby uses jobs.ashbyhq.com. Workday is unmistakable — a long myworkdayjobs.com URL with the company name in it. Taleo, still common at large and older enterprises, appears as taleo.net. Knowing this in advance tells you roughly how much of your evening the application is about to consume.

Workday is the one that deserves the most preparation, because it is by far the most demanding of your time. It typically requires creating an account before you can apply, and — critically — that account is per-employer rather than universal, so applying to five Workday companies means five separate accounts with five separate passwords. It parses your uploaded resume into a full employment history form and then asks you to check and correct it, which sounds convenient and in practice means retyping a substantial amount of it, because the parsing frequently mangles dates, splits single roles into two, or drops employers entirely.

The practical approach to Workday is to accept the time cost and protect against the failure modes. Budget twenty to thirty minutes for a first application at a given employer, considerably less for subsequent ones once the account exists. After the resume upload, read every auto-filled field rather than skimming — the dates especially, since a mangled date range can silently misrepresent your years of experience, and years of experience is one of the fields recruiters actually filter on. Save your progress if the option exists, because sessions do time out and losing the form is a common and enraging experience.

Greenhouse sits at the opposite end and is the system most candidates prefer. It generally does not require an account, the form is short, and it accepts a resume upload with a small number of additional questions. Parsing is reasonable, and because there is usually no auto-filled employment history to correct, the resume you upload is the resume that gets read. Application time is often under five minutes. When people say a clean single-column PDF simply works, Greenhouse is largely what they're describing.

Lever is similar in spirit — no account required in most configurations, a short form, straightforward upload. Its one distinguishing feature from a candidate's perspective is the frequency of custom questions that companies add, some of which are substantive free-text prompts rather than checkboxes. Those questions are worth taking seriously; a thoughtful two-sentence answer in a field most applicants leave empty or fill with a single word is a genuinely cheap differentiator.

Ashby is newer and more common at technology companies that have hired recently. From the outside it resembles Greenhouse and Lever: short form, no account, quick submission. It tends to have cleaner handling of things like location and work authorisation questions, and its forms are among the more pleasant to complete. There is little candidate-side strategy required beyond the general principles.

Taleo is the oldest system you're likely to meet, and it is the least forgiving. Expect an account, a long multi-step form, session timeouts, and parsing that struggles with anything other than very plain formatting. If you are applying through Taleo, this is the moment to use your most conservative resume version — single column, standard headings, no graphics, simple dates. Creative formatting fails here more visibly than anywhere else.

SmartRecruiters, iCIMS, BambooHR and Workable fill out much of the remainder. They vary, but as a rough guide the newer and more design-forward the interface looks, the shorter the form is likely to be, and the more it resembles an enterprise system from a decade ago, the more retyping you should expect.

A pattern that holds across all of them: the structured fields matter more than the attached resume. This is the single most useful thing to understand about applicant tracking systems generally. What you type into the form becomes searchable, filterable data in a database that recruiters query. Your resume is an attachment that a human may or may not open. When a form asks how many years of experience you have with a specific technology, that answer is what gets filtered on — not the equivalent claim buried in your resume's third bullet. Fill every optional field that lets you demonstrate a genuine match, and never leave a free-text interest box empty.

Another pattern: knockout questions are real, and they are the closest thing to genuine automatic rejection in these systems. Work authorisation, willingness to relocate, minimum experience, required licences — these are configured as filters and they do remove applications from view. This is worth distinguishing from the widely circulated claim that these systems automatically reject most resumes on formatting or keyword grounds, which the available evidence does not support. Hard eligibility filters exist; a machine judging your resume's design and discarding it largely does not.

On autofill tools, including ours: they work reliably on the company's own career-page forms — Greenhouse, Lever, Ashby, Workday and similar — because these are ordinary web forms and filling one is no different from typing into it yourself. There is a technical wrinkle worth knowing, because it explains why some autofill tools appear to work and then silently fail. Most of these application forms are built with React, and a value written directly into a field is discarded by the framework on the next re-render. A correctly built autofill sets the value the way a browser does, so the framework registers the change; a poorly built one appears to fill the form, and then the submitted data is empty. If you use any autofill tool, check the fields visually before submitting.

Dropdown fields are the other common autofill failure, and worth checking by eye. Setting a select field to a value that doesn't exactly match one of its options does nothing at all — silently. So a work-authorisation dropdown can look untouched after autofill even when everything around it filled correctly. Give every dropdown a glance before you submit.

What autofill should never do is submit for you, and this distinction is where the real risk sits. Tools that automate the job boards themselves — driving LinkedIn or Indeed on your behalf and firing off applications — are a different category entirely. Both platforms prohibit automated applying, enforcement is account suspension, and losing your professional network account in the middle of a search is a genuinely serious setback. Filling in a company's own form and clicking submit yourself breaks no platform rules and carries no such risk.

A few practical habits that pay off across every system. Keep a plain-text version of your employment history — employer, title, exact start and end dates, location — somewhere you can copy from, because you will retype it more often than you expect. Use the same email address consistently, since duplicate applications under different addresses create confusion that occasionally costs interviews. Apply on the company's own careers page rather than through an aggregator where you have the choice, as it avoids duplicate-record problems and is the most reliable source of the current posting. And when a form offers a free-text field asking why you're interested, use it — it is frequently the only thing a busy recruiter reads besides your title.

One thing worth understanding is that your application persists. These systems are databases, and your record stays in the employer's instance long after the role is filled — which cuts both ways. It works in your favour when a recruiter searches the existing pool for a new opening and finds you, which is a genuinely common route to an interview and costs you nothing. It works against you when an old application with outdated information surfaces first. If you apply somewhere repeatedly over the years, it is worth updating your profile where the system lets you, so the version a recruiter finds is the current one rather than the graduate you were.

Reapplying is a common question with a straightforward answer: it is fine, and it is usually better to submit a fresh application than to reply to an old rejection. Most systems allow it, and for a different role there is no awkwardness at all. For the same role re-posted some months later, applying again is reasonable if something has genuinely changed — new experience, a certification, a different location situation. What does not help is submitting the identical application to the same posting multiple times, which creates duplicate records, looks careless in a system where the recruiter can see every one of your submissions, and is one of the few candidate behaviours that actively counts against you.

None of this changes the fundamentals of a good application. But knowing which system you're about to enter tells you how much time to set aside, which fields will need checking, and where your resume is likely to be misread — and that knowledge converts the most tedious part of a job search from a source of unpredictable frustration into something you can plan around.

Frequently asked questions

Which ATS takes the longest to apply through?

Workday, comfortably. It usually requires a per-employer account, parses your resume into a full employment-history form you then have to correct, and frequently mangles dates. Budget twenty to thirty minutes for your first application at a given company.

Why does my resume get parsed wrong in some systems and not others?

Parsers vary in quality and tolerance. Greenhouse, Lever and Ashby generally handle a clean single-column PDF well. Workday and Taleo struggle more, particularly with dates, columns and anything inside a table or graphic — use your plainest resume version there.

Do these systems automatically reject resumes?

Hard knockout questions — work authorisation, minimum experience, required licences — are real filters that remove applications. But the widely repeated claim that these systems auto-reject most resumes on formatting or keyword grounds isn't supported by the available evidence.

Is it safe to use an autofill tool on job applications?

On a company's own career-page form, yes — it's an ordinary web form and no platform rule applies. Check the fields visually before submitting, especially dropdowns, which silently stay unset if the value doesn't exactly match an option. Avoid anything that automates LinkedIn or Indeed itself.

Related guides

Try JobStraight free →