Workday, Greenhouse, iCIMS: How Autofill Handles Different Career Portals

Apply to five jobs in a US or Canadian job search and you'll likely land on five different-looking forms — one is a Workday multi-page wizard with an account you have to create first, another is a single-scroll Greenhouse page, a third is a stripped-down Lever form with three fields and a resume upload. They're built by different companies on different codebases, and none of them share a form schema. Here's what actually differs between them, and how a browser autofill tool deals with a job posting it's never specifically been coded for.

Why these platforms don't look alike

Workday, Greenhouse, Lever, and iCIMS are separate commercial products, each sold to employers as an end-to-end hiring system, not just an application form. Workday's form is often the deepest — multi-step, sometimes requiring an account, frequently asking EEO self-identification questions as separate steps. Greenhouse tends toward a single long page. Lever is usually the shortest. iCIMS sits somewhere in between and varies more by how the specific employer configured it. None of that variation is arbitrary — it reflects different product philosophies at each company — but it does mean a tool built to fill "the Workday form" would break the moment it hit a Greenhouse page, and vice versa.

The two ways to build around that

There are two real approaches to autofilling forms across platforms like this, and they trade off differently:

• Hand-coded, per-site selectors. You write logic specific to LinkedIn's Easy Apply modal, or Naukri's application flow — reading the exact DOM structure of that one site and mapping it field by field. This is precise where it applies, but it only covers the sites someone explicitly wrote code for.
• A generic engine that reads whatever DOM is actually there. Instead of assuming a known layout, the engine looks at each form field's label, placeholder text, and surrounding context on the page it's currently on, and matches it against your profile data regardless of which ATS rendered it. This is what makes it possible to fill a Workday page, a Greenhouse page, and an iCIMS page without three separate integrations — the same matching logic runs against whatever fields the current page happens to have.

ApplyCandid uses hand-coded flows for LinkedIn and Naukri specifically, because their in-page application modals are common enough and structured enough to be worth that precision. For everything else — any direct-URL job posting on Workday, Greenhouse, Lever, iCIMS, or a similar platform — it runs the generic engine instead, so a new employer's careers page doesn't need a new integration before it can be filled.

What the generic engine actually fills, and what it doesn't

Deterministic fields — name, email, phone, address, work authorization — get matched and filled directly from your saved profile on any of these platforms, with no AI call involved. Open-ended fields, like a "why are you a good fit" box some Greenhouse and iCIMS forms include, get drafted from your resume and the job description through the AI server you've connected. Both categories stop at the review step: nothing on a third-party ATS gets auto-submitted, regardless of whether Auto-Submit is turned on for LinkedIn or Naukri. That's a deliberate boundary — every employer's Workday or Greenhouse instance is configured slightly differently, and a form that looks fully filled can still have a step you need to catch by eye, like a multi-select EEO question or a required file upload the engine can't see.

What actually trips up a generic fill

The most common friction points are the same regardless of which platform is rendering them: multi-step wizards where a "Next" button gates the next set of fields, account-creation gates before the actual application starts (common on Workday), and file-upload steps for a cover letter or portfolio that need a document you have ready rather than text the engine can type. None of these are platform bugs — they're just steps that need a document or a click rather than a field to fill, so the run pauses there for you rather than guessing.