Turbo-charge your search
Everything below is built from pieces documented elsewhere — LinkedIn integration, the apply queue, and AI answers. This page is the workflow that gets the most out of combining them: spend your attention scanning listings, not filling forms.
The idea
Browsing LinkedIn's results, you can tell in a couple of seconds whether a job is worth applying to. Filling the application takes minutes. The turbo-charge workflow separates those two: queue everything worth applying to as fast as you can scan, then let the queue work through the pile while you keep browsing — or close the tab entirely.
Set up once
- Turn on auto-apply. Settings → Apply to queued jobs automatically. Without this, jobs sit in the queue as Queued until you press Run now yourself.
- Turn on AI answers, if you haven't already (Settings → AI answers, or during onboarding). The queue still runs without it, but every required question nothing could answer becomes a Needs answers stop — with AI answers on, most of those get resolved automatically instead, so the queue clears with far less babysitting. See exactly what that sends.
- Fill out custom Q&A for anything you already know will come up — a common screening question in your field, a specific number you'll type the same way every time. Every one you add ahead of time is one less stop later. See Custom questions.
None of this is required — the queue works fine with all three off, it's just more hands-on.
Queue in bulk
Work a results page top to bottom and press ≡ on everything worth applying to. Nothing blocks while you do this:
- The card gets a blue Queued chip immediately and the job lands in your log — no page navigation, no waiting for a tab to open.
- You can queue a dozen jobs in the time it'd take to open and review one application.
- Repeat across pages, across searches, across saved-search alerts — every ≡ press adds one more job to the same queue.
Once you've moved past the first jobs you'll notice colour-coding doing some of the triage for you — grey for already-applied-or-hidden, yellow for opened, blue for queued — so a second pass down the same list only needs a glance. See Colour coding.
Let it run
With auto-apply on, queue.js works through what you've queued one job at a time in the background — opening the posting, finding the form, filling it the same way the on-page badge would, and submitting. You don't need to keep the tab open or watch it happen; check back later.
Three things can happen to each job, and all three are useful signal, not just success/failure:
| Outcome | What it means | What to do |
|---|---|---|
| Auto-submitted | Done — no action needed | Nothing. It's in your log with a real application behind it. |
| Needs answers | A required question nothing could answer, including the AI | Open the Answer N pill in the log, answer once — it's remembered for every job after |
| Failed submit | A CAPTCHA, sign-in wall, or validation error stopped it | The tab was left open where it stopped — finish that one by hand |
Needs answers entries are the highest-leverage ones to clear: each answer you give becomes custom Q&A, so the next queued job with a similar question — same company or a completely different one — clears on its own instead of stopping again. A queue you work through steadily needs fewer manual answers over time. See Answer-and-remember and How jobwhat learns.
Check the pile, don't watch it
Open the job log filtered to the queue (Settings → Apply queue card → See the queue, or filter the log by kind) to see everything Queued, Auto-submitted, Needs answers or Failed submit in one place — no need to revisit LinkedIn to check status. Run now and Clear queue are on the same card if you want to force a pass or start over.
The Metrics tab turns a session of this into a number: forms autofilled, how many the queue auto-submitted outright, and the accuracy of what got filled — a rough sense of how much of a hundred-application week jobwhat actually carried for you.
Limits worth knowing
- Easy Apply (LinkedIn's own in-app flow) and Workday postings aren't supported by the queue — Workday's account-creation wizard needs your eyes on it, and Easy Apply isn't a page jobwhat can autofill. Queue what you can; apply to those two the normal way.
- The queue runs one job at a time, not in parallel, so a pile of fifty won't all finish in the next minute — it works through them steadily in the background as you keep browsing.
- A Failed submit doesn't retry itself. It's parked exactly where it stopped so you can pick it up, not silently dropped.