Job Search Strategy
Why applying to more jobs is making it worse
There is no correct number, because application volume is not the thing deciding whether your phone rings. What decides it is how close you sit to the role and whether a single human being at that company has any reason to know your name.
Listen to this one
Full episode transcript
Pip: Sunday night, fourteen applications submitted, zero callbacks — so obviously the answer is twenty next week.
Mara: That’s the loop Angela Malagon is writing about this week: why volume job searching backfires, and what a search that actually converts looks like instead.
Pip: Let’s start with why sending more applications might be the thing actively working against you.
Why more applications is making it worse
Mara: The core claim here is that application volume is not the variable controlling whether your phone rings — proximity to the role and a human connection are.
Pip: The post opens with a scene that will be familiar to a lot of people right now, then cuts to what actually happened to those fourteen applications after you hit submit.
Mara: Here’s the line that frames the whole piece: a job posting is not an inbox someone reads top to bottom. It is a requisition, and a requisition is a pipeline with several separate lanes feeding it.
Pip: And the applicant pool is the last lane. Referrals arrive with a person’s name attached. Sourced candidates arrive with recruiter notes. Silver medalists arrive with debrief scores. Your file arrives as a file.
Mara: Right — and volume makes that worse, not better. The post is direct about this: when the same name appears on four unrelated openings at one company in a single week, it doesn’t read as enthusiasm. It reads as someone who hasn’t decided what they do.
Pip: Which makes the resume harder to argue for in a debrief, because the recruiter can’t tell the hiring manager what you are. That’s the practical cost — not a vague penalty, an actual moment in a room where your file gets harder to champion.
Mara: There’s also a time argument. Volume degrades everything it touches. At twenty applications a week nothing gets tailored, the standard slips, and by Thursday the two activities that actually move the needle — targeting and contact — are the ones that got cut.
Pip: The post reframes the whole measurement. Applications sent is an activity count. The only number worth tracking is screens booked. Four applications and one screen beats fourteen applications and zero screens.
Mara: The fix is a target list of twenty to thirty companies, a top-half-of-applicants test before you apply, a cap of five to eight applications a week done properly, and one human contact attached to every single application — not the recruiter, the peer who does the job.
Pip: Five to eight. Done properly. That’s the whole corrective, and it’s genuinely less work than what most people are already doing.
Mara: The post also maps the funnel by stage: no screens is a targeting problem, screens that don’t progress are a positioning problem, panels without offers are an execution problem. Treating all three with more applications is exactly why searches stall for months.
Pip: Same silence, three different causes — that’s the part worth sitting with before next Sunday night rolls around.
Mara: The through-line is proximity over volume — being close to the role and having a name attached matters more than the count.
Pip: Next time: what a recruiter actually reads in the first six seconds. Which, based on this, might be the more important half.
Angela Malagon — Career Strategist. 15+ years recruiting talent for companies such as Cisco, Google, and Wells Fargo, then job searched against the same systems.
It is 10:40 on a Sunday night. You have submitted fourteen applications since Friday, logged every one in the tracker, and the only thing in your inbox is a note confirming that your application has been received and will be reviewed by the team. Three weeks of this. So the obvious conclusion is that fourteen was not enough, and next week you will do twenty.
I understand the logic. It is the only lever you can see from where you are sitting. It is also the wrong one, and I can tell you exactly why, because I spent 15+ years recruiting talent for companies such as Cisco, Google, and Wells Fargo, and I know what happened to those fourteen applications after you hit submit.
How many jobs should you apply to a day?
There is not a number, and anyone who gives you one is selling you a habit rather than a strategy. Five applications a week with a person attached to each will beat twenty sent cold, and twenty sent cold will beat forty. The reason has nothing to do with how hard you are working. It has to do with which lane your file lands in.
What a recruiter is actually looking at
A job posting is not an inbox that someone reads top to bottom. It is a requisition, and a requisition is a pipeline with several separate lanes feeding it.
There are people I went out and found myself. There are referrals from the hiring manager and the team. There are the runners-up from the last time we ran a similar search, sitting in the system with notes attached saying strong, hire later. Sometimes there is an agency submission. And then there is the applicant pool, which is you.
The other lanes arrive with context attached, and yours arrives with none. A referral comes with a person’s name on it. A sourced candidate comes with my own notes explaining why I chased them. A silver medalist comes with a debrief from a panel that already liked them. Your application comes as a file, competing against every other file, judged on paper alone in a very short window.
If you have been picturing a machine rejecting you overnight, that is not what is happening either. The ATS is a database, not a bouncer — which is exactly why never being returned in a search is the more common outcome than being turned down.
Here is the part that is harder to hear. Recruiters notice volume applicants, and it is not a flattering read. When the same name lands on four unrelated openings at one company inside a week, on the finance role and the operations role and the two program manager roles, that does not look like enthusiasm. It looks like someone who has not decided what they do, which makes the resume harder to argue for in a debrief, because I cannot tell a hiring manager what you are.
None of that means applying is pointless. People get hired out of the applicant pool constantly. It means the applications that convert are the ones that either sit very close to the role or have something human attached to them, and volume by itself produces neither.
Why more applications makes your week worse
You have a fixed number of hours and a fixed amount of nerve. Volume spends both on the lowest converting activity available.
It also degrades everything it touches. At twenty applications a week nothing gets tailored, so the same generic resume goes to roles that want different things. The standard slips, and you start applying to postings where you meet maybe a third of the requirements, because the tracker rewards the row, not the fit. By Thursday you are exhausted, and the two activities that actually move the number, targeting and contact, are the ones that got cut.
And you are measuring the wrong thing. Applications sent is an activity count, and it feels productive, which is exactly the problem. The only number worth tracking is screens booked. Fourteen applications and zero screens is not progress. Four applications and one screen is.
What a week should actually look like
Do this instead, starting tomorrow. It takes less time than what you are doing now.
- Build a target list, not a search feed. Twenty to thirty companies you would actually take a call from, chosen for industry, size, and location. You are no longer searching for jobs. You are watching thirty companies for openings, which is a much smaller and much more winnable job.
- Run the top half test before you apply. Read the must-haves, ignore the wish list, and ask whether you would land in the strongest half of the people who will apply. If the answer is no, that application is not a shot on goal, it is noise, and it is noise with your name on it at a company you care about.
- Attach a person to every single application. One message, same day, to someone who does the job you applied for or manages people who do. Not the recruiter, who is buried. Not the CEO. The peer.
- Cap the volume so steps two and three are possible. For most people that is five to eight applications a week, done properly. If you cannot write a specific reason you want a particular role, you do not have time to apply to it.
- Read your funnel every two weeks. Not your feelings, your stages. This is the part almost nobody does, and it is the only way to know what to change.
On step three, this is the whole message. Short, specific, and it does not ask for a job.
Hi [Name], I applied for the [role title] on your team this morning. I spent the last six years doing [the specific thing the posting is about] at [company type], most recently [one concrete result].
I am not asking you to refer me. I would just like to know what the team is actually trying to fix with this hire, so I can tell you honestly whether I am the right person for it. Happy to keep it to fifteen minutes.
Most of those go unanswered. That is fine. The ones that land put a human name next to your file before anyone opens it, and that is the entire difference between the lanes.
On step five, here is how to read the funnel. Applications going out but no screens coming back is a targeting and resume problem, so you are either aiming at roles you cannot win on paper or your top third is not doing its job. Screens happening but nothing progressing to a panel is a positioning problem, meaning you are answering the questions without landing on what you are — that call is testing four specific things. Panels happening but no offers is an interview execution problem, which is a different fix entirely. Same silence, three different causes, and treating all three with more applications is why searches stall for months.
The line to hold
Your search does not have a volume problem. It has a proximity problem. Every application you send with nothing attached to it is a lottery ticket, and you are buying them in bulk because buying them feels like working. Fourteen tickets and one ticket have roughly the same odds when the winning numbers are being drawn in a different lane.
The same mechanic shows up one step earlier, in what happens in the seconds after your resume is opened. I broke that down in what a recruiter actually reads in the first six seconds. And if you want the Job Search Tracker I use to run a funnel properly, it is free in the Job Search Library, along with the rest of the checklists.
If you cannot tell which stage is broken
That is what the Job Search Strategy Session is for. It is $400, ninety minutes, and we go through what you have actually been sending, where people are dropping out of your funnel, and which of the three causes above is the one costing you interviews. You leave with a target list, a corrected pitch, and a thirty day plan with a specific weekly number in it, not a general one.
You keep every note, script, and plan from the session. When you fill in the contact form you get a reply from me within 48 hours, not a bot and not a template, and if I think the session is the wrong thing for your situation I will tell you that instead of booking you.
Hiring truth, in your inbox
The stuff nobody puts in a rejection email. No spam, no pep talks. Subscribe here.