Job search diagnostic
Whether applying at volume is working for you, arithmetically
The answer above holds regardless of your situation. The questions below narrow it to the one cause your own answers point at, which is a different and more useful thing than a list of possible reasons.
Is mass applying to jobs bad?
Mass applying is not a moral question, it is an arithmetic one. Volume works when each application has a non-trivial chance of a response, because sending more of them scales a working process. It fails when the per-application rate is near zero, because multiplying a number near zero produces a number near zero while consuming all the time you would need to fix the rate. So the useful question is not whether to apply at volume but what your current response rate is, and whether the hours are better spent raising it than repeating it.
- When volume is the right strategy
- When you are getting responses at a workable rate and simply need more of them. Scaling something that works is not a mistake.
- When it is the wrong strategy
- When the response rate is near zero. More applications at the same rate cannot produce an interview, and the time spent is the same time that would have identified why.
- The trade-off that actually decides it
- Applications per hour against responses per application. If cutting volume in half would more than double the rate, targeting wins; if not, volume does.
- What this cannot tell you
- Your response rate. That number comes from your own records, and it is the one input nobody else can supply.
Source and method
RoleSprint, from the structure of the job-search process rather than from a dataset. Verified 2026-08-30. This page carries no third-party statistics, because the honest ones for this question do not exist in a citable form. What it holds is a decision tree over facts you report about your own search, and the reasoning behind each branch is stated on the page so you can disagree with it. Nothing you select is transmitted anywhere.
Narrow it down
3 questions you can answer without looking anything up. Nothing you select leaves your browser.
What this page will not claim
Stated here rather than in a footer, because the value of a diagnostic is entirely in knowing what it cannot see.
- This is arithmetic over numbers you supply, not a prediction about your search.
- It assumes your reported response rate is stable, which it may not be across different kinds of role.
- It says nothing about whether any specific application was worth sending.
Every outcome this page can reach
Published in full so the tool cannot be a black box. If none of these describes your situation, the page is the wrong one and says so rather than forcing a fit.
Volume cannot help you at this response rate
Stop adding applications for a week and find out where they are stopping. A rate of zero across twenty is a signal about the applications, not about the number of them.
Your applications cost too much for the rate they return
Cut the per-application time hard, or cut the number and spend the difference on checking fit before you commit. Doing neither is the only losing option.
Volume is working, and it is a reasonable strategy
Keep the volume and protect the rate. The failure mode from here is broadening the target set until the rate quietly drops.
The target set is too broad for the effort you are spending
Filter harder before you write anything. The check on whether a role is worth an hour takes minutes and removes most of the applications that were never going to respond.
What to do next
This page narrows one symptom. The full diagnostic looks at the whole search at once, which matters when more than one thing is wrong.