Why Does a "Great" Resume Still Get Nothing?
The short answer
Jobbris is an AI resume-tailoring tool that turns your documented experience into a truthful, job-specific resume in about two minutes. A great resume gets nothing because reading well only clears the floor. In the biggest hiring experiment, competent applications heard back about a quarter of the time, and the practical base rate is two to three in a hundred.
Why does a "great" resume still get nothing?
Because reading well only clears the floor. In the largest controlled experiment in hiring, more than 83,000 competent applications got employer contact about a quarter of the time, and that figure is close to a ceiling, not an average. The practical base rate is two to three in a hundred, so silence is the default.
The 83,000 number comes from a field experiment by Kline, Rose and Walters, whose NBER paper sent more than 83,000 fictitious but competent applications to 108 of the largest US employers. A statistics reading of that study puts employer contact at about 24% within 30 days. Because every resume in the study was competent and role-appropriate by construction, that quarter is closer to a ceiling than an average, and the fieldwork ran from late 2019 into 2021, so it is a ceiling from a tighter market.
The practical base across channels is lower. LoopCV's 2026 response-rate guide, vendor data rather than an academic study, puts the industry-wide baseline at two to three per hundred, with Easy Apply at one to two, a direct company site at three to five, and a referral at thirty to fifty. Those numbers are directional, but they give you a shape: what you get depends heavily on which door you knocked on, and most people knock on the cheapest one.
How many replies should 100 applications actually get?
Two or three, if they all went through a portal. Around ten to twenty if a recruiter submitted you, and thirty to fifty if they came through referrals. A hundred Easy Apply clicks can honestly return one or two replies and tell you almost nothing about your resume. The channel moves that number far more than the document does.
This is why the r/jobs poster who was on their 98th application in five months, and had started checking whether email was actually working, was asking the right question in the wrong place. Silence at 98 portal applications sits inside the expected range. An r/bayarea thread that collected 487 comments from laid-off tech workers was, in effect, a peer sample of the same rate: one commenter wrote, "I get less than 1% response to applications. is it just me?" It was not just them.
Run the test before you rewrite anything. Track your next hundred applications, split them by channel, and count the replies. If portal applications return two or three and everything else stays silent, the document is not the variable. If a referral goes quiet too, then you have a real signal worth chasing.
Why is the pile you are measured against bigger than your effort?
Because a fifth of the people you are compared with are software. Greenhouse's 2025 Workforce and Hiring Report found 22% of actively searching candidates use bots to apply automatically, rising to 31% among Gen Z. LinkedIn was reporting about 11,000 applications per minute across the platform in 2025, up 45% year on year.
"I applied to 100 jobs" is still a large number as effort. It is no longer a large number as competition. When a machine can fire off applications you never sent, the pile your one application lands in stops reflecting human hours, which is the point of the bot numbers in Greenhouse's 2025 report. That is why both halves of the seeker sentence are true at once. "I sent a hundred" and "I heard nothing" can coexist without either one being wrong.
Why do I keep losing to a candidate who looks perfect on paper?
Because qualified is the floor, not the tiebreaker. Once a role has hundreds of applicants who can all do the job, selection happens on variables the document cannot control: an internal candidate already slotted, a gap that reads as a firing, or a credential the team quietly requires.
The clearest illustration is the top comment, at 200 likes, on an r/Accounting thread from October 2026. The poster had a year and a half at a Big Four firm and no interviews. The comment did not nitpick the resume. It said, "Ignore the people who are nitpicking your resume. It is largely fine," then named the two things actually deciding: an unemployment gap since June that read as a firing, and a CPA credential not yet passed. The document was not the problem, and telling that poster to rewrite it would have wasted their week.
There is a comparative layer sitting on top of that. One commenter who had been "final rounded 5 times" described losing to "the perfect on paper candidate or someone they had slotted and are just meeting numbers as well." Nothing in that sentence is about a resume, which is exactly why the resume keeps getting rewritten. It is the only part of the search that answers to effort.
What should you do instead of rewriting your resume a ninth time?
Change the channel and sharpen the fit. Move effort from portal volume toward referrals and targeted applications, and make each resume answer the specific posting before you send it. Rewriting the same document for the tenth time does not move a base rate that was never about the document.
If your resume is fine, the remaining lever is fit to the specific role. That is the part you can actually improve, and it is what Jobbris is built for: send a job link and get a truthful, job-specific resume in about two minutes, then spend your hour where there is a signal. The arithmetic supports the shift. If referrals convert at thirty to fifty per hundred and Easy Apply at one to two, then ten warm introductions beat a hundred cold clicks, and the resume you send to each one is the thing that actually gets read.
Frequently asked questions
Why does my resume get no reply when a recruiter told me it was fine?
Because fine and selected are different tests. A recruiter saying your resume is fine means it clears the floor, not that it wins the pile. The r/recruitinghell poster whose old job was helping people with their resumes found nothing to fix, even after a career coach: the same case from the person least able to believe it.
Does my resume read as relevant or generic?
That is the one place the document still decides. A fine resume can read as generic if it does not answer the specific posting, and that is a fit problem rather than a quality problem. Generic is the failure mode a targeted rewrite can fix. Invisibility at a base rate of two to three per hundred cannot.
Tanul Tewari
Founder, Jobbris
Building Jobbris to fix the part of the job search nobody talks about: the hours of tailoring and the silence that follows.