The apply queue
The Autofill button never submits a form for you. The apply queue is the one part of jobwhat that does — and only for jobs you deliberately add to it.
Queueing a job
Press ≡ on a LinkedIn job card (see LinkedIn integration) and the job lands in your log as Queued. From there, queue.js in the background service worker works through the queue one job at a time:
- Opens the LinkedIn posting in a background tab and reads the company's Apply link.
- Follows it. Boards that keep the form one click away (Ashby
/application, Lever/apply) are taken there directly. - Polls every frame for a content script that has found an application form, then asks it to
autoApply— the same fill logic as the on-page badge, followed by a click on the Submit button. - Watches the tab for up to 40 seconds.
Outcomes
| Result | What happened | What you see |
|---|---|---|
| Auto-submitted | A confirmation page appeared | Tab closed, entry marked Auto-submitted in the job log |
| Failed submit | CAPTCHA, sign-in wall, validation errors, or no confirmation appeared | Entry marked Failed submit, reason in its notes, tab left open where it stopped so you can finish by hand |
| Needs answers | A required question nothing could answer came up | Entry marked Needs answers (amber), questions in the notes, tab left open showing the badge — see Answer-and-remember |
Easy Apply (LinkedIn-internal) and Workday (account creation plus a multi-step wizard) are declared unsupported for the queue up front — Workday's wizard needs your eyes on it. Everything else the queue does, the badge can also do manually if you'd rather watch.
Pre-flight: knowing before you queue
Before a job even starts running, jobwhat does a pre-flight check: it looks up whether this exact posting (by LinkedIn job id) has known questions from the form-sharing network, resolves each one locally against your rules and custom Q&A, and — if AI answers are on — sends any leftovers to the AI in one batch. Whatever required question is still open becomes a Needs answers entry right away, before the queue ever opens a tab.
In the job log, this shows as a pill reading Answer N. Clicking it opens a small dialog — a select built from the form's own options, or a text box — and Save and queue stores each answer as custom Q&A and sets the job back to Queued, ready to run cleanly next time.
Turning it on
Settings → Apply to queued jobs automatically controls whether the queue runs on its own; the queue card on the same tab shows what's waiting, with Run now and Clear queue. Queued jobs and their outcomes live in your job log alongside everything else — filter by kind to see just the queue.