RECOVERY

Month 1 Checkpoint: What Working Looks Like

Thirty days in, the numbers tell the truth. Here's how to read your own funnel — and the honest diagnosis of what's actually broken if the pipeline is dry.

Month 1 Checkpoint

Thirty days in, you have real data. Not feelings — data. This is the week you stop narrating what you think is happening and start reading the actual funnel numbers, because they will tell you exactly what’s broken and what isn’t.

The four metrics to track

Open the spreadsheet from week three and count:

  1. Quality applications sent — tailored, referred where possible
  2. Recruiter screens — any first call, phone or video, from a human at the company
  3. Technical screens — any coding, system design, or case round
  4. Onsite loops — full-loop interviews scheduled or completed

That’s it. Four numbers. Write them down.

What healthy looks like at month one

For a mid-to-senior SWE in a normal market:

  • 20–30 quality applications
  • 5–10 recruiter screens (roughly 20–30% of applications)
  • 2–4 technical screens (roughly 40–50% of recruiter screens)
  • 1–2 onsites in progress or scheduled

Your absolute numbers depend on level, market, and target tier — a staff+ search moves slower than a mid-level one. But the conversion ratios between stages are the tell.

The honest diagnosis

Find the stage where the drop-off is abnormal. That’s your bottleneck. Only one fix at a time.

Bottleneck: applications → recruiter screens

If you sent 20 applications and got 1 screen, it’s the resume, the targeting, or both. Likely fix: the resume isn’t reading at the seniority you’re targeting, or the top third doesn’t match the roles you’re applying to. Fix the resume before sending another twenty.

Bottleneck: recruiter screens → technical screens

If you’re getting intro calls but they don’t move forward, it’s either compensation misalignment (recruiter floated a number, you said a higher one, they dropped you quietly) or a behavioral red flag (layoff narrative, reason for leaving, or something specific the recruiter picked up on). This one is harder to see from the inside; a mock behavioral loop with honest feedback exposes it fast.

Bottleneck: technical screens → onsites

If you’re failing first technicals, that’s prep. Three weeks off is real rust — expected. Fix with 2 mock interviews a week for the next 4 weeks, matched to your target companies’ formats.

Bottleneck: onsites → offers

At month one this is rarely the issue yet. If it is, that’s a month-two problem and usually indicates specific weak areas (system design for senior roles, or behavioral for any level at Amazon).

What not to do at month one

Don’t panic because you don’t have an offer yet. The median time-to-reemployment for SWEs in 2026 is roughly 4–5 months. If your funnel is healthy at month one, you’re on track. If it isn’t, you now know exactly where the fix goes — and month two is where you double down on the channel that’s pulling.

Frequently asked questions

What's a healthy month-one funnel for a senior SWE?
Rough benchmarks: 20–30 quality applications out, 5–10 recruiter screens, 2–4 technical phone screens, 1–2 onsites scheduled or completed. If you're below those numbers, the funnel has a leak — and the leak's position tells you the fix.
No recruiter screens yet — is that a resume problem or a market problem?
Probably resume. The market is usually more forgiving than engineers assume. If you've sent 15+ quality applications (not cold-spam) and have zero screens, the resume is not reading as senior enough, or it's not making it past ATS, or the targeting is wrong. Run it through a review.
Screens are happening but nothing converts to onsite — what's wrong?
That's an interview-prep bottleneck, not a positioning problem. The resume got you in the door; the first 45-minute call sent you home. Rust, communication, or a specific weak area (usually system design for senior roles, DSA for junior). Fix it with focused mock practice.