Why your job applications stall at 'reviewing' (and the 30-day rule that tells you to move on)

You applied to 23 roles in March. 17 went to "under review" and stayed there. Three rejected you. Three never responded at all. Now it's May, you're applying again, and you have no idea which of those 17 are still live.

This is the silent killer of job searches: applications don't formally fail, they just stop. You keep mentally holding open a slot for them, your pipeline feels fuller than it is, and you don't apply hard enough to new roles because you're "waiting to hear back" on six that are already dead.

What 'under review' actually means

It almost always means one of three things:

1. The recruiter looked, didn't move you forward, and didn't bother to reject. Common for high-volume roles. The ATS shows "under review" forever because no one updated the status.
2. The role was filled internally and the external posting was a compliance exercise. Especially common at large companies for senior roles.
3. The role is genuinely paused (hiring freeze, headcount review, candidate slate restart). This is the only case where waiting makes sense.

You can't tell which without inside information. So the move is to treat the application as a probability that decays over time.

The 30-day rule

For 80% of roles, an application that hasn't moved past "under review" within 30 days of submission is functionally dead. Specific timelines that work as a default:

• Day 0 to 7: Live application. ~60% of successful applications get a first-round response in this window.
• Day 8 to 14: Slower process, still live. ~25% of successful applications respond here.
• Day 15 to 30: Cooling off. ~12% respond in this window. Worth one polite follow-up email at day 20.
• Day 31+: Functionally dead. ~3% of successful applications respond after day 30. Don't count this application as live in your pipeline anymore.

The numbers are looser at smaller companies (where hiring can be genuinely slow) and tighter at high-volume employers (where silent rejection is the norm). But the shape holds: every additional week the application sits, the probability halves.

The 4 stages worth tracking separately

Lumping every application into "applied" hides the real bottleneck. Split your pipeline into 4 explicit stages:

1. Applied (Day 0 to 30). Live, hopeful. Count this as ~10% probability of a real interview.
2. Screen scheduled or completed. The recruiter has talked to you. ~30% probability of moving forward.
3. Interview loop in progress. You're talking to the team. ~40% probability of an offer.
4. Offer or rejection. Terminal state. Done.

If you have 17 applications in Stage 1 and 0 in Stage 2 after 6 weeks, the bottleneck is at the resume-to-screen conversion. Either your resume isn't matching the role, your applications are landing in the wrong pile (most ATSs reject 75% before a human reads them), or the roles you're picking are wrong for you.

If you have 4 in Stage 2 and 0 in Stage 3, the bottleneck is your screen. Practice answering "tell me about yourself" out loud. Most candidates fail the screen on this single question.

The follow-up email that actually works

Send one at day 20, to the recruiter or hiring manager, two paragraphs. The pattern:

1. Reference one specific thing from the role description that you've been thinking about (proves you actually read it). Example: "I noticed the role mentions migrating from monolithic Postgres to a sharded architecture. I led exactly that migration at [Company] last year."
2. State directly: you're still interested, you have a few other processes moving, you'd like to know if there's a next step.

The second part matters. "Still interested" alone gets ignored. "Have other processes moving, would like clarity" creates urgency. About 30% of these follow-ups get a real response (either rejection or escalation). Either is better than silence.

What to track per application

The minimum you need to make decisions:

• Date applied (for the 30-day rule)
• Role title and company
• Stage (Applied / Screen / Interview / Offer or Rejection)
• Last contact date (drives the follow-up cadence)
• Salary range and target (so you can compare offers later)
• Likelihood (your gut score, 1 to 10). Adjust over time as signal arrives.

This is 5 to 6 columns. A spreadsheet works. An app works. The point is having one place to look so you stop holding pipeline state in your head.

The AI Coach part

Tracking is the easy half. The hard half: figuring out why apps are stalling and what to do next. The Job Application Tracker auto-stamps every application with its date, computes the 30-day cutoff, surfaces stalled apps in a dedicated view, and the AI Coach reads your full pipeline (stages, follow-up history, gaps) and tells you exactly which app to follow up on, which to abandon, and where your funnel is leaking.

If you're interviewing soon: pair this with the Interview Prep Coach, which reads the roles you're applying to and writes STAR answers using your actual background. Or the Salary Negotiation Coach if you're staring at an offer letter.

FAQ

What if a company explicitly says "we'll get back to you in 6 weeks"?

Believe them, but only the first time. If they go past 6 weeks with no contact, the application is dead. They didn't get back to you because the answer was no.

Should I withdraw an application I've given up on?

Only if you have an active conversation elsewhere and need to use it as leverage ("I have other processes moving"). Otherwise, no. Just mark it dead in your tracker and stop thinking about it.

How many applications should I have live at once?

Aim for 8 to 12 in Stage 1, 2 to 4 in Stage 2, 1 to 2 in Stage 3. If you have 50 in Stage 1, you're spraying. If you have 0 in Stage 2 after 6 weeks of applying, the issue is your top of funnel.