4 min read
How many jobs should you apply to? Fewer than the internet says
The applications-per-day question has the wrong unit. Why volume targets backfire, what actually limits a job search, and where the freed-up hours should go.
Search this question and you'll find confident numbers: ten a day, fifty a week, a hundred a month. The numbers disagree with each other, which is the first clue that they're made up. The second clue is the unit. Applications per day treats a job search like piecework, where output scales with repetitions — and everything downstream of the submit button says it doesn't.
What a volume target optimises
Set a daily quota and you will hit it, because the quota is the only thing being measured. What bends to make that possible is everything the quota doesn't see. Reading the posting properly goes first. Tailoring goes second — a quota rewards the untailored application, which takes a tenth of the time and produces a tenth of the signal. Judgement about fit goes last: by application eight of ten, the marginal posting isn't one you chose, it's one that was still open in the tab.
The applications this process emits are the ones recruiters describe reading constantly: technically responsive to the posting, obviously written for no posting in particular. They don't fail because a filter catches them. They fail because a person reads two lines and moves on — and each one taught you nothing, because nothing about "generic application, no reply" distinguishes the role, the CV, or the market as the cause.
There's a second-order cost, too. Every application is a thread that can come back: a screening call, an assessment, a recruiter with questions about a role you can't remember applying to. Volume without judgement doesn't just lower reply quality — it books your own calendar with the replies you least wanted.
The real constraint is attention, not throughput
A job search has one genuinely scarce input: focused attention. The evening you have after work holds maybe two properly done applications — read the posting twice, decide what to emphasise, tailor, write something specific, check it. That's not an argument for a quota of two. It's the observation that attention spent on a badly matched role is attention removed from a well matched one, which reframes the entire question. The number that matters isn't how many you apply to. It's how good the worst role you applied to was.
That number is set upstream of the application, at the filtering step — the unglamorous work of reading many postings and discarding most. Done honestly it consumes more time than applying does, which is exactly why quota-driven searches skip it. Skipping it doesn't remove the filtering; it moves the filtering to the employer's side, where it runs at two lines per rejection and returns no information to you.
Where automation actually belongs in this
The tempting automation is the submit button — it's the most repetitive step, so it looks most automatable. But automating submission scales the part that was never the constraint, and floods the market with exactly the applications that don't work.
The automation that changes the economics sits earlier and later. Earlier: discovery and filtering — scanning the boards, discarding the dead and the mismatched, scoring what's left against your actual history so the evening starts at the shortlist instead of the haystack. This is where Quarrion puts the machine reading: it reads the four hundred so your attention starts at the twenty. Later: the clerical wrapper around each application you chose — the form-filling, the tracking, the follow-up drafts — with an approval gate, so nothing leaves without a person having decided it should. The judgement stays where the accountability is.
Notice what this does to the original question. With filtering handled, the sensible application count stops being a discipline target and becomes an output: it's however many roles genuinely cleared the bar this week. Some weeks that's three. In a hiring surge in your specialism it might be fifteen. Both are correct answers, because the bar, not the count, is what's being held constant.
A better weekly shape
If a number helps as scaffolding, aim it at inputs you control: every open role in your target space seen and triaged this week — by software if possible, by a fixed skim hour if not; every role that cleared your bar applied to properly, with materials arranged for that reader; every live thread followed up on schedule. Then let the application count fall where it falls, and judge the week by pipeline movement — screens booked, interviews progressing — rather than by submissions.
"How many should I apply to?" is usually anxiety wearing arithmetic's clothes — the search feels stalled, and a bigger number feels like doing something. The honest answer is that the number was never the lever. The bar is the lever. Set it with your own judgement, hold it when the week feels slow, and spend the anxiety on the follow-ups instead; they're cheaper than applications and recover stalled threads more often.