Sending applications into silence is the most demoralizing part of a job search. It's easy to blame yourself, your resume or "the market". Usually the real reasons are more specific, and most of them can be fixed. We looked at 180,000 live postings from company career pages to put numbers on the common ones.
1. You're applying to roles that need more experience
Among postings that state years, a third accept 0 to 2. For product manager roles it's 9%, and for growth marketing 8%. If you're early in your career and applying broadly, most of your applications go to roles that will screen you out on years before anyone reads your resume.
Fix: read the years line before applying. Apply only where you're within about a year, and spend the time you save on better applications. Our breakdown of what "3+ years" really means has the full numbers.
2. The posting is old
About 38% of the roles in our feed were posted in the last 7 days, and 80% in the last 30. The rest are older, and around 10% have been up more than 60 days. Older postings are more likely to be filled, frozen or kept open as a pipeline. The first few days matter: many teams review the first wave of applicants and start interviewing.
Fix: check the posted date and prioritize roles from the last week. Set up a daily routine of checking new roles rather than a weekly batch.
3. You're competing in the biggest pile
A famous company's open role on a big job board can get thousands of applicants. The same skills at a smaller company, posted on its own careers page, might get a few dozen. Your resume is the same; your odds aren't.
Fix: look beyond the household names. Search company career pages directly, and include mid sized companies in your target list.
4. Your resume doesn't match the posting's words
Many companies use applicant tracking systems that let recruiters filter by keywords and knockout questions. If the posting says "SQL" and "A/B testing" and your resume says "data analysis" and "experimentation", a recruiter scanning quickly may not connect them.
Fix: use the posting's exact words for skills you genuinely have. Put the most important ones in your top third. Don't stuff keywords you can't back up in an interview.
5. The knockout questions screened you out
"Are you authorized to work without sponsorship now or in the future?" "Do you have 3 years of experience in X?" These questions often auto reject before any human review. Answering honestly is right, but it means some roles were never open to you.
Fix: read the requirements before applying. If you need sponsorship, target employers with a history of sponsoring your role. Our guide to sponsorship for new grads covers how to find them.
6. Your resume shows tasks, not results
"Responsible for weekly reporting" says what you were assigned. "Automated weekly reporting, saving the team 6 hours a week" says what you achieved. Recruiters skim in seconds and remember results.
Fix: rewrite your top bullets as outcome, action, number. If you can't measure something, describe the change it caused.
7. Nothing shows you can actually do the work
When hundreds of resumes look alike, proof stands out: a short case study, a solved problem, a project with real users, a public analysis. It gives a recruiter a reason to pick you from the pile, and it gives the hiring manager something to talk about.
Fix: add one piece of proof per target role and link it at the top of your resume. On Crossway, your Arena solves and projects are part of your profile, and companies can see exactly how you solved each problem.
Other causes worth checking
- Ghost jobs: listings kept up with no real plan to hire soon. See how to spot them.
- Internal candidates: some roles are posted publicly while an internal person is the favorite.
- Location rules: "remote" sometimes means remote within certain states or countries.
- Formatting: two column templates and text in images can confuse older tracking systems. A simple single column PDF is safest.
A better weekly routine
- Each morning, check roles posted in the last 24 to 48 hours.
- Shortlist only roles where you meet or nearly meet the years and core skills.
- Tailor the top third of your resume and link one piece of proof.
- Find one person on the team and send a short, specific note.
- Track every application, and review weekly which kinds of roles reply.
The aim is to change your reply rate, not your volume. Ten well aimed applications a week usually beat a hundred blind ones.
Track your applications like an experiment
You can't fix what you don't measure. Keep a simple tracker with these columns: company, role, posted date, date applied, years asked versus your years, referral (yes or no), proof linked (yes or no), and outcome. After 20 or 30 applications, patterns appear: maybe referrals get replies five times as often, or roles posted within three days reply far more. Then do more of what works.
| Signal | What to look for after 30 applications |
|---|---|
| Years fit | Reply rate on roles where you meet the years line versus roles where you don't |
| Freshness | Replies on roles applied to within 3 days versus older |
| Referral | Replies with a referral versus without |
| Proof | Replies when you linked a case study or project |
A 30 minute resume rewrite
- Write a one line summary naming the role you want and your strongest proof.
- Rewrite your top three bullets as result, action, number.
- Move the skills the posting names into your top third, if you truly have them.
- Cut anything that doesn't support the role you're applying for.
- Export a single column PDF and check that the text copies cleanly.
A short outreach note that works
Hi Priya, I just applied for the Data Analyst role on your team. I noticed your pricing page changed last month, so I put together a one page look at how I'd measure the impact, linked here. If it's useful, I'd love 15 minutes to hear what the team is focused on.
Specific, short and useful to them. Most people send nothing, or send a generic request for a referral.
Keep going without burning out
Silence feels personal, but it usually reflects odds and timing. Set a weekly target you control, like ten well aimed applications and five outreach notes, and judge yourself on that, not on replies. Take one day a week fully off. The search is a long game, and steady beats frantic.
Where applications usually stop, and what fixes each stage
| Stage | What usually stops you | Fix |
|---|---|---|
| Before any human sees it | Knockout questions, years mismatch, location rules | Apply only where you meet the basics |
| Recruiter skim | Unclear target role, task based bullets, missing keywords | Summary line, results first, the posting's language |
| Hiring manager review | Nothing that shows you can do this specific work | Link one piece of proof per role |
| After a first call | Vague answers, no questions, slow follow up | Prepare stories, ask about their problems, reply within a day |
Most people only work on the resume, the second stage. The biggest gains are often in the first stage (applying where you fit) and the third (proof).
Where replies actually come from
- Referrals are the highest yield channel at most companies. A short note to someone on the team, with something useful attached, often turns into one.
- Applying directly on company career pages gets your application into the same system recruiters use, often faster than a job board copy.
- Recruiters reaching out to you, which happens more when your profile clearly states your target role and shows proof.
- Communities and events in your field, where hiring managers meet people before roles are even posted.
When to change your approach
If you've sent 30 well aimed applications and gotten no replies, change something specific instead of sending 30 more: narrow your target role, add proof, rewrite your top third, or shift toward roles with better odds for your level. If you're getting first calls but no second rounds, the problem is interview prep, not applications.
Questions
Why do I get no response to job applications?
Most often: applying to roles that need more experience, applying to old postings, competing in the largest applicant pools, missing keywords, knockout questions, task based resumes and no proof of work.
How old is too old for a job posting?
Postings older than about 30 days are more likely to be filled or frozen. Prioritize roles from the last 7 days.
Do applicant tracking systems reject resumes automatically?
Knockout questions often do. Keyword matching usually helps recruiters filter rather than auto reject, so matching the posting's words still matters.
How many applications should I send per week?
Around 10 to 20 well aimed applications usually do better than 100 untargeted ones.
How do I make my application stand out?
Lead with results, use the posting's language for skills you have, and link one piece of proof like a case study or solved problem.