Pipeline
Fewer Applications With Evidence Beat a Hundred Without
Budget hours, not a count of applications. Split them into two layers: a small number of roles you would genuinely take, spending real time on selection and specific evidence, and a wide, cheap layer sent as-is with no rewriting. Measure interviews per hour spent searching rather than per application sent, because a count of submissions says nothing about the attention any one of them got, and applications have been growing faster than the openings behind them.
The takeTwenty or thirty a week sounds like discipline, but it's really a platform's engagement target dressed up as a strategy, and it survives because a search returns so little feedback that nobody can easily prove it wrong. The honest answer was never a count. It's whether an hour of your search time went toward something you could defend in a follow-up conversation, or toward a number that only ever looked like progress.
Where Olive fits
Open a role and see what the work shows
Olive sits on the employer's side of the funnel as six evidenced findings written about one candidate at a time, and every report it releases is shown to the candidate it describes, free.
Rank your shortlistWhy is the answer usually a number, and why is that wrong?
Because a number is easy to sell. Job boards and auto-apply tools answer with a target, apply to twenty or thirty a week is the common version, and that target happens to match what keeps a user active on the platform selling it. Career-advice sites hedge to "quality and quantity both," which sounds balanced and tells you nothing about where to actually put an hour.
What neither answer says out loud is what happened to the denominator. Reviewer hours at any given employer stay roughly fixed; they don't scale up because applicant volume did. A Robert Half survey of more than 2,000 US hiring managers found 67 percent saying that reviewing AI-generated applications has slowed their hiring process, and 84 percent reporting heavier workloads 1. When submitting costs seconds and reading still costs minutes, more applications per opening does not mean more attention per applicant. It means less, spread thinner across a pile that keeps growing, which is an arms race being sold back to you as a strategy, and one where the platform selling the number never has to pay the cost of you following it.
What the volume actually did to your odds
Nobody has measured that directly, which is worth saying before anyone quotes a number at you. What has been measured is the crowding. On Workday's own recruiting platform, candidates submitted 356 million applications in 2024, up 26 percent, while the jobs its customers created rose 7 percent 2; in the Institute of Student Employers' survey of UK employers, graduate vacancies drew an average of 140 applications each for two years running, the highest in three decades of ISE tracking 3.
Submitting more into a pile that's growing faster than the openings behind it does not raise your odds proportionally, because everyone else's volume is rising at the same time. The one large randomized result in this area points at the application rather than the count: on an online labour market, 480,948 new jobseekers were randomly assigned, half of them to algorithmic writing assistance on their profile text, and the treated group was hired 8 percent more often 4. What that trial changed was the writing, not how much anyone sent, and it found no evidence that employers were less satisfied with the people hired that way. Two limits travel with it: the tool tested was a grammar and clarity checker rather than anything that wrote new claims from scratch, and a freelance marketplace is not a corporate hiring pipeline, so take the direction of the effect rather than the number.
Budget hours, and split them into two layers
The unit to plan in is an hour of your attention, divided into two layers. One layer is a small number of roles you would genuinely take, spending roughly an hour each: real selection of the posting, specific evidence pulled from your own work, and a named person addressed where one exists. The other is a wide, cheap layer sent as-is, with no rewriting, for roles worth a shot but not worth an hour.
A few ways to keep the split honest:
- Time the first layer, don't count it. If an hour, real hour, produces two tailored applications or five, either is fine; the constraint is attention, not a quota.
- Let the cheap layer stay cheap. The moment you start editing a "just send it" application, it has quietly moved into the wrong bucket and is now costing time it wasn't budgeted for.
- Track interviews per hour spent, not per application sent. The second number is what volume-first advice optimizes, and it improves just by clicking faster, which is why it can look like progress when nothing has actually changed.
What goes into that hour is a separate question worth its own answer: do you really have to tailor your resume for every single application covers where the hour is best spent once you've decided to spend it. The pull toward the volume end is strong and widely acted on. In a Greenhouse survey of 2,900 job seekers across four countries, nearly half said they were submitting more applications than a year earlier, and 41 percent admitted to inserting hidden text meant to game AI filters 5, a tactic no source here shows improving an outcome and a clear risk of ending one. None of that is time spent on the person who will actually read the application, and unlike an hour of real selection it carries a cost if it's ever noticed.
Watch the denominator, not the count
The denominator is reviewer attention, and nothing you send changes how much of it exists. So if you are applying faster than you can say, out loud, why you applied to that specific role, the extra applications are quietly costing you the screens you do get. Every hour spent on a scattershot application is an hour not spent making a selective one land.
Employers are living the same arithmetic from the other side; why applications per opening tripled this year, and how many of them are real is what the hiring side is being told about the exact volume you're adding to. Reading it is a useful check on the instinct that more is obviously better, since the people receiving the pile don't think so either. It also names the one exception worth knowing: identity fraud concentrated in remote-only and contract roles, a real but narrow slice of the volume, settled at offer rather than at the resume stage, and not a reason to read every crowded pile as suspicious.
Trade the borrowed number for your own: whatever a week's real, actual hours split cleanly into, a handful you can defend in a follow-up conversation, and a wider layer that costs you nothing but the time it takes to send it.
Common questions
Is there any research-backed number of applications per week?
No credible study sets a target application count, because the useful variable is attention per application, not the count itself. The specific numbers in circulation, twenty, thirty, fifty, are unverified: none of them traces back to a published study.
Does applying to more jobs at least improve my odds a little?
Only if the additional applications carry real selection and evidence, which most high-volume approaches by definition don't have time for. No study has tested application volume against outcomes directly. The closest large randomized evidence improved the writing in jobseekers' own profiles rather than the number they sent, and hires rose 8 percent.
How do I know if I'm spending too much time tailoring one application?
If an hour has stretched into two or three for one role with no unusual complexity, you've likely moved a cheap-layer application into the selective bucket without deciding to. Time-box it deliberately rather than letting it drift.
Should the cheap layer include roles I'm not that interested in?
It can, as long as you're honest that it's unedited and low-cost on your end. The problem isn't applying broadly; it's spending real hours dressing up an application for a role you weren't going to invest in anyway.
What should I actually measure to know if my search is working?
Interviews per hour spent searching, not applications sent. It's a slower number to gather, but it's the one that reflects where your time is actually converting, rather than a raw count that mostly tracks how fast you can click submit.
References
- 1. Robert Half survey: 67% of HR leaders report AI-generated applications are slowing hiring press.roberthalf.com Shows reviewer time and workload rising with application volume, supporting the point that more submissions do not buy more attention per applicant.
- 2. How HR Leaders Can Thrive in a Complicated Job Market workday.com Sizes how much faster applications grew than job openings, supporting why raw volume does not raise odds proportionally.
- 3. 5 trends you need to know from ISE's Recruitment Survey 2025 ise.org.uk Gives a dated figure for how many applications a graduate vacancy now draws, sizing the crowding volume advice runs into.
- 4. Algorithmic Writing Assistance on Jobseekers' Resumes Increases Hires (NBER Working Paper 30886) nber.org Randomized evidence that improving the writing in a jobseeker's own application text raised how often they were hired, on an online labour market.
- 5. An AI Trust Crisis: 70% of Hiring Managers Trust AI to Make Faster and Better Hiring Decisions, Only 8% of Job Seekers Call it Fair greenhouse.com Shows both rising application volume and self-reported use of hidden filter-gaming text, supporting that volume-chasing is a widespread but unproven tactic.
5 sources, numbered by first appearance. How Olive sources claims
General guidance for hiring teams. What works at one company and one volume may not transfer to yours.
Olive assesses how a person works with AI. It does not detect AI-written documents, and it never produces a score, a ranking, or a match percentage for a person. Candidates read the same report the employer reads.