How many applications should I send per week?

5–10 is plenty if they're high quality. 50+ usually means you're copy-pasting and your response rate will be under 1%. The goal isn't volume — it's signal. A senior engineer with a strong network and a clean resume converts at 20–30% on warm intros and 3–5% on cold. Do the math on what you need.

Should I tailor the resume for every application?

No. Maintain one strong master resume and one cover-letter template. Swap in 2–3 sentences of company-specific context per application. More than that is diminishing returns — you'll burn out by week four.

What about applying through the job board vs a referral?

Always take the referral if you can get one. Internal referrals get pulled out of the ATS queue and reviewed by a human within days, not weeks. Cold applications go into a pile sorted by keyword match. Different pipelines, different odds — often 10x different.

RECOVERY

Week 3 After a Tech Layoff: Start Applying (But Differently)

Week three is the first week of applying. But 70% referrals, 30% direct — and five targeted companies beat fifty shallow ones every single time.

Updated Apr 19, 2026

Week 3 After a Tech Layoff

Week three is the first week you apply to anything. The temptation will be to make up for lost time by firing off fifty applications in a single afternoon. Don’t. The engineers who land fast are the ones who spent two weeks on infrastructure and now aim narrow.

The 70/30 rule

Out of every ten hours you spend on the search this week, seven go to referrals and intros, three go to direct applications. Not the other way around. Referrals convert at roughly an order of magnitude higher rate — a recruiter who gets your resume from an internal Slack gets interested in a way an ATS keyword match never generates.

In practice this looks like:

Every application is preceded by a 10-minute search for anyone you know (or anyone your network knows) at that company. LinkedIn’s 2nd-degree view is free and accurate. A warm intro beats the application form.
Cold applications are a backup, not the plan. You still send them — but only for companies you’re genuinely excited about and where you have no connection path.

Target 5–7 companies deeply, not 50 shallowly

Write down 5–7 companies that meet three criteria: hiring for your role, domain you care about, and at least one person in your network (1st or 2nd degree). Research each one for an hour — their engineering blog, their Glassdoor interviews, their recent funding or product launches. By the time you walk into a phone screen, you should sound like you already work there.

This approach generates more offers than the spray-and-pray approach even though it looks slower from the outside. Ten targeted conversations where you clearly did the homework beats 100 cold apps where the recruiter can tell you didn’t.

The mock-interview calibration

Three weeks off is enough rust that your first technical screen will go worse than it should. Before the first real interview, run at least two mock loops — one DSA, one system design. The goal isn’t to practice problems; it’s to reacquaint yourself with the feeling of thinking out loud under time pressure.

A mock interview is cheap. A failed onsite at your dream company is expensive. Do the cheap version first.

Track the funnel

Open a spreadsheet. Five columns: company, channel (referral / direct / recruiter outreach), status, date last touched, next action. Update it weekly. By the end of month one you’ll be able to look at it and tell where the bottleneck is — applying, getting screens, passing screens, or getting offers. Each of those failure modes has a different fix.

What the week ends with

By Friday of week three: 5 targeted applications out (3 via referral, 2 direct), two mock interviews completed, calendar with at least one recruiter call scheduled. That’s a strong week.

If after 10 targeted applications you’re getting zero recruiter calls, the bottleneck isn’t effort — it’s positioning. Revisit the resume. If you’re getting calls but failing the screens, it’s prep. Either way, month one is where you check the numbers honestly and pick the fix.

Frequently asked questions

How many applications should I send per week?: 5–10 is plenty if they're high quality. 50+ usually means you're copy-pasting and your response rate will be under 1%. The goal isn't volume — it's signal. A senior engineer with a strong network and a clean resume converts at 20–30% on warm intros and 3–5% on cold. Do the math on what you need.
Should I tailor the resume for every application?: No. Maintain one strong master resume and one cover-letter template. Swap in 2–3 sentences of company-specific context per application. More than that is diminishing returns — you'll burn out by week four.
What about applying through the job board vs a referral?: Always take the referral if you can get one. Internal referrals get pulled out of the ATS queue and reviewed by a human within days, not weeks. Cold applications go into a pile sorted by keyword match. Different pipelines, different odds — often 10x different.