August 21, 2026

How Many Jobs Should You Apply To? (And How to Track Them Properly)

The real trade-off between application volume and tailoring quality, how many roles a week is realistic, and how to run a job application tracker that survives past week three.

Two pieces of advice circulate constantly, and they contradict each other. One says apply to everything, because it is a numbers game. The other says apply to five carefully chosen roles, because quality beats quantity.

Both are half right, and the half that is missing is what most people get wrong.

The actual trade-off

Applications have two costs: the time to send one, and the attention to send a good one. Volume and quality trade against each other only because tailoring is slow. Change how long tailoring takes and the trade-off moves.

If a tailored application takes 45 minutes, then ten a week is a part-time job and quality collapses beyond that. If it takes five minutes, twenty-five a week is comfortable and every one of them is still specific.

This is why "is it volume or quality" is the wrong question. The right one is: what is the largest number of genuinely tailored applications you can sustain each week?

A realistic weekly target

For most people conducting an active search alongside other commitments:

  • 15 to 25 applications a week is a sustainable, effective range when tailoring is fast.
  • 5 to 8 a week is the honest ceiling if you are tailoring by hand from scratch each time.
  • Above 40 a week almost always means the applications have stopped being tailored, whatever you tell yourself.

Response rates vary enormously by field, seniority and market conditions, so treat any specific conversion figure you read with suspicion. What is consistent is the shape: a small number of well-matched, well-tailored applications outperforms a large number of generic ones, and the gap widens the more competitive the role.

Why blanket applying underperforms

Popular postings routinely attract several hundred applicants within days. In that pool, a generic resume is not competing on merit — it is competing on whether a recruiter's search happens to surface it, which it usually does not. As covered in the 75% rejection myth, applications disappear because of volume and search, not because a robot rejected them.

There is also a self-inflicted cost. Applying to forty roles you are not qualified for generates forty silences, and forty silences is how people conclude the market is impossible and stop applying. Targeting is partly a morale strategy.

Where to draw the line on fit

A reasonable filter before you spend any time tailoring:

  • Do you meet most of the required qualifications? Not all — most. Postings are wish lists, and the research on this is consistent: candidates who apply at roughly 60% of stated requirements are frequently interviewed.
  • Is there a genuine keyword overlap between your history and the posting? If nothing in your background maps to the core of the role, that is not a resume problem to be fixed by better tailoring.
  • Would you take the job? Location, compensation band, work model. Applying to roles you would decline wastes the scarcest resource in a job search, which is your own attention.

If you find yourself failing the second test repeatedly, the useful move is to change what you are applying for, not to apply harder. Running a posting through an ATS resume checker answers this in seconds — a low semantic score against your genuine history means "wrong role", not "worse resume".

Running a tracker that survives

Everyone starts with a spreadsheet. Most abandon it around week three, at exactly the point where it starts to matter — when interviews begin and you can no longer remember which of six resume versions went to which company.

What a tracker has to hold to be worth maintaining:

Which resume version you sent. The single most important field, and the one spreadsheets handle worst. When a recruiter calls about a role you applied for three weeks ago, you need the exact document in front of you before you speak.

Stage, not just status. Saved, Tailoring, Applied, Interviewing, Offer. A Kanban view makes the shape of your pipeline visible at a glance — including the uncomfortable truth when twenty cards are stuck in Applied.

The job description itself. Postings get taken down. Preparing for an interview against a job description you can no longer read is avoidable pain: save the text when you apply.

Date applied. For follow-up timing, and for noticing that a company has gone quiet for three weeks.

Contact and source. Whether it came from a referral, a recruiter, or a board changes how you follow up.

Vignova's job tracker keeps each tailored resume attached to the job it was written for, which removes the version-tracking problem entirely. A spreadsheet can work — it just requires discipline exactly when you have least of it.

A weekly rhythm that works

A structure that holds up better than applying in bursts:

  • Monday: source. Collect 15 to 25 postings that pass your fit filter. Save them, do not apply yet. Separating sourcing from applying stops you drifting into low-fit roles when the list looks thin.
  • Tuesday to Thursday: tailor and send. Work through the saved list. Tailoring in a batch is faster than one-at-a-time because you stay in the same mode.
  • Friday: follow up and review. Chase anything two weeks silent. Look at what got responses and adjust what you are targeting.

The point of the rhythm is that it makes the search finite. An open-ended "apply whenever" search expands to fill every evening and burns people out within a month.

When to follow up

Roughly 10 to 14 days after applying, once, briefly, to a named person if you can find one. A second follow-up rarely helps and occasionally hurts.

After an interview, a short thank-you within 24 hours, then follow the timeline they gave you. If they said two weeks, chase on day 15 — not day 8.

Frequently asked questions

Is it worth applying to a role posted three weeks ago? Often yes for less competitive roles, rarely for high-volume ones where a shortlist already exists. Prioritise postings under a week old.

Should I apply to several roles at the same company? Two, if they are genuinely different and you are genuinely qualified for both. Five reads as spraying.

Does applying early matter? For high-volume roles it matters a lot, because shortlists form fast. This is the strongest argument for a sourcing routine that catches postings within a few days.

How do I stay organised across multiple resume versions? Attach the resume to the job record rather than storing resumes in a folder. The relationship between document and application is the thing you actually need to preserve — see how to tailor per role without losing track.

The short version

Do not choose between volume and quality — reduce the cost of quality until you can afford volume. Fifteen to twenty-five genuinely tailored applications a week, filtered for real fit, tracked with the resume attached to the role, beats both the five-application purist and the hundred-application sprayer.

Vignova saves jobs, tailors a resume for each one, and tracks the whole pipeline in one place — free tier, no credit card.