Skip to content

Beta.applyNchill is in active testing — expect rough edges, and check what it sends before you rely on it.

six stages · browser extension · in your Chrome

Apply

Fills and submits the real form, in your own browser and your own session, with a hand-written driver per board.

How this stage flows

Your browser extension polls your queue signed in as you and opens each posting in a background tab. The job is routed to the driver for its board — Workday, Oracle HCM, Greenhouse, or a generic navigator for everything else. Anything it cannot answer honestly it asks you about; what is submitted is written to the ledger.

polled by the extension, signed in as you

routed to the driver for that board

anything it cannot answer honestly

submitted, then written down

The only stage that runs outside the server, and deliberately so: an application should arrive from you.

Everything upstream of this happens on a server. The last step does not. A form is submitted by your own browser in your own session, because that is the only way the application is genuinely yours — and because a server pretending to be your browser is the exact thing these boards are built to detect.

Why every board has its own driver

A generic form filler gets to about the third field on any real ATS. Workday relabels its own steps, so sections are routed off its progress rail instead of the headings. Oracle keeps education and experience as a card ledger that has to match your profile exactly, or it re-fills entries you already finished. Greenhouse ignores typed text in the city box entirely. None of that is discoverable from the outside; all of it is a driver.

It stops rather than guesses

A question it cannot answer from your profile is not filled with something plausible. The knight appears on the tab with exactly the fields it is stuck on, waits for you, and carries on. An application submitted with an invented answer is worse than one that was never sent.

One browser at a time. Two browsers signed into the same account, both claiming from the same queue, is the one failure that looks like jobs vanishing rather than like an error.

Found this useful? Add applyNchill as a preferred source on Google