RECOVERY
What to Do When You're Not Getting Responses
Hundreds of applications, zero replies. It's not the volume — it's a diagnosable problem. Here's the triage tree SWEs should run before sending one more.
What to Do When You’re Not Getting Responses
You’ve sent 80 applications. You’ve got zero replies. The narrative you’re telling yourself is that the market is broken or you are. Neither is usually the full story — but both matter less than the diagnostic tree that finds the actual leak.
Before sending one more: run the triage
Five possible causes. Check in order.
1. ATS parsing failure
Copy the full text of your PDF into a plain text editor. If it comes out as a jumbled mess, so does the view the recruiter’s ATS shows. Common failure modes:
- Two-column layouts (ATS merges the columns in the wrong order)
- Text in images or icons (invisible to parsers)
- Creative fonts that don’t extract cleanly
- Headers with non-standard wording (“My Journey” instead of “Experience”)
Fix: single-column, Helvetica/Arial/Calibri, standard section names, no images. A “plain” resume ranks higher than a designed one at the parsing stage.
2. Seniority / level mismatch
Read the job descriptions you’re applying to. What does “senior” mean there? If the posting asks for “8+ years” and you have 4, the ATS will likely auto-reject no matter how strong the resume is. Same for staff/principal roles with coded requirements (“drive technical strategy across multiple teams”). Apply where your level actually matches; that increases response rate on its own.
3. LinkedIn signal weakness
For 2026, LinkedIn is often the de-facto resume. Recruiters cross-check every applicant. If your LinkedIn doesn’t back up your resume — outdated title, missing current experience, no activity in 6 months — applications get filtered out for looking stale. Audit: is the headline searchable? Is the current role up to date? Is the skills section current?
4. Targeting mismatch
Are you applying for roles that fit your actual tech stack, or for ones that contain keywords from your last job title? Ex-backend engineers applying to generalist “software engineer” roles get lost; ex-backend engineers applying to “senior backend engineer, payments” or “backend engineer, Go, distributed systems” get read. Specific is better than general.
5. A silent former-manager signal
Rare, and usually overestimated, but possible. If you had a tense exit with a former manager who’s now influential in your target domain, a reference service can tell you in 48 hours what they’re saying about you. Usually the answer is “nothing” — but when it isn’t, you need to know.
The 5-application test
Before you panic-apply to 50 more jobs, send 5 carefully targeted ones that fix everything identified above. Track responses for 2 weeks. If those 5 get 1–2 screens, the tactic works — now scale. If those 5 get zero, it’s deeper than the resume and you need the structured diagnosis from month 3’s checklist.
The volume trap
Applications above ~10 per day almost always mean declining per-application quality. You’re probably spamming the same resume into different ATSes, and every one of them hits the same fate. One hour of careful targeting on two applications produces more screens than two hours of bulk submission across ten.
If the emotional side of the no-response stretch is wearing you down, read the mental health guide. If it’s the financial side, run the runway numbers to know how much time the triage actually has.
Frequently asked questions
- How do I know if my resume is ATS-broken?
- Copy-paste the full PDF into a plain text editor. If formatting explodes, columns merge, or symbols appear in the wrong places, ATS parsers are probably seeing the same mess. Single column, standard section headings (Experience, Education, Skills), no tables, no images, no creative fonts.
- Could a former manager be silently blackballing me?
- Possible but rare, and usually overestimated. References are legally narrow (companies confirm dates and title, that's usually it). If you suspect this, use a reference service to call as a pretend recruiter — cheap, and it tells you exactly what's being said. Most of the time the answer is 'nothing unusual.'
- I'm applying to senior roles as a 10-YOE engineer and getting no responses. What gives?
- Check the level match carefully. Many companies have compressed their senior band — 'senior' at Google is different than 'senior' at a Series B startup. If you're applying across tiers without adjusting the pitch, one version of the resume will be over-targeting and the other will be under-targeting.