How many jobs should you apply to each week?

Why the usual numbers are useless

Advice to send two hundred applications assumes each one costs you two minutes. Advice to send five assumes each one takes most of a day. Neither describes what you are doing, so neither number transfers to your situation.

The useful question is not how many, but how much return you get per hour spent. Twenty carefully targeted applications and two hundred generic ones can take the same number of hours. What differs is the response rate, and that is the only figure worth optimising.

What actually moves the response rate

Three things change outcomes more than volume does, and all three are within your control.

• Relevance. Applying to roles where you already cover most of what is asked beats applying widely to roles where you cover a third.
• Timing. Applying in the first days after a posting appears beats applying in the third week, by a wide margin.
• Specificity. A resume that uses the employer's own language for the work beats a general one, because that is what both the filter and the reader are scanning for.

The problem with mass applying

Sending a hundred identical applications feels productive and rarely is. The mechanics work against you. Generic applications are the ones most likely to be filtered out on keyword grounds, because a generic resume by definition does not use the vocabulary of any particular posting.

There is a second cost that is easy to miss. Many employers post several similar roles, and applications are visible across them. Applying to six roles at one company with the same untailored resume is a pattern a recruiter can see in one screen, and it reads as indiscriminate rather than keen.

A rate that holds up over a long search

For most people looking for a professional role, somewhere between five and fifteen well-targeted applications a week is sustainable and productive. That range assumes each application involves reading the posting properly, adjusting your summary and the order of your bullets, and keeping a record of what you sent.

Sustainability matters more than intensity, because job searches run for months rather than weeks. A pace that produces forty applications in week one and nothing in week four is worse than a steady ten, both for results and for morale.

Track the outcome rather than the effort. If you have sent forty applications and had no first-round conversations, the problem is not that you needed eighty. Something upstream is wrong: the roles are mismatched, or the resume is not carrying the language the filter is looking for, and sending more of the same will not fix either.

Where automation genuinely helps

Automation is well suited to the parts of a job search that are mechanical: finding the openings, scoring them against your experience, filling in the same name and email for the hundredth time, and keeping a record of what you sent and when.

It is poorly suited to the part that decides the outcome, which is judging whether a role is worth your time and saying something specific about why. Tools that submit applications on your behalf optimise the number rather than the response rate, and the number was never the constraint.