Job searches fail two ways: too slow, and too fast. Too slow — you spend three months perfecting your resume and never apply. Too fast — you blast 200 applications in a week with a generic resume and get zero replies.
The 8-week structure below is the pace I've seen work consistently for tech and adjacent roles. It's opinionated. Adjust the calendar, but keep the sequence.
Assumptions: you're currently employed (or have runway) and can spend 10–15 hours a week on the search. If you're unemployed and full-time searching, compress the schedule by 30–40%.
Week 1: audit and target
Goal: know what you're selling and who you're selling to.
Three concrete outputs:
- A target list of 30–50 companies. Not "tech companies" — actual names, ranked into three tiers (dream, realistic, safety). Tier 1 gets your best effort; tier 3 is for calibration reps.
- A one-page "role definition" document. Title, level, 3–5 must-have JD bullets, comp band, remote/hybrid/onsite, locations. This is the filter you'll run every posting through.
- An honest gap analysis. For the top 10 postings in your target list, which 2–3 skills show up repeatedly that you don't have? Can you close the gap in 8 weeks? If no, widen the role definition or pick a different target.
No applications this week. None. The discipline to not apply in week 1 is what separates a structured search from a panic search.
Week 2: artifacts
Goal: resume, LinkedIn, cover letter template, portfolio link. All tight.
- Resume: one page, tailored to your most common target role. Every bullet quantified. Our perfect resume in 2026 and how to beat ATS systems guides are the working doc.
- LinkedIn: full rebuild using the LinkedIn optimization checklist. Headline, About, Featured, Experience, Skills.
- Cover letter skeleton: two paragraphs. First paragraph: why this company specifically. Second paragraph: why you specifically. 150 words max. You'll tailor the first paragraph each application.
- Portfolio or proof of work: link to a GitHub, a blog, a case study, a Notion. If you have nothing, build one this week — a 1-page writeup of a project you've shipped, with metrics, is enough.
End of week 2 checkpoint: someone outside your field reads your resume cold and can tell what you do and what you're good at in 30 seconds. If not, keep editing.
Week 3: calibration applications
Goal: send 15–20 applications to tier-3 (safety) companies.
Why safety first: you're going to be bad at this in the first week. You'll mis-tailor the resume. Your cover letters will be too long. You'll misread the level. Better to burn those mistakes on companies where you're less invested.
Process per application:
- Read the JD twice.
- Re-order your resume skills + top two bullets to mirror the JD's top three requirements.
- Rewrite the cover letter opening paragraph for the specific company.
- Apply through the portal.
- If a recruiter or hiring manager is findable, send one LinkedIn DM using the cold outreach templates.
Target pace: 4–5 applications a day on weekdays. Track in a spreadsheet — company, role, date applied, DM sent, status. Week 3 should produce 2–4 recruiter replies. Use them for phone screen practice.
Week 4: tier 2 and networking
Goal: 15 applications to tier-2 targets, plus 10 networking messages.
You've now got one week of data. Which resume version got responses? Which didn't? Iterate.
The networking layer this week:
- 5 informational interview requests to people at tier-1 companies (see Template 4 in the cold outreach guide).
- 5 re-engagement messages to old colleagues at target companies.
Expect 2–4 of those 10 to convert to actual conversations. That's your referral pipeline for weeks 5–6.
Interview prep starts now too. Don't wait until you have a phone screen scheduled to prep. Start grinding the relevant prep — for engineers, that's the software engineer interview questions patterns. 30 minutes a day, every day, starting week 4.
Week 5: tier 1 push
Goal: your best shots. 10–15 highly tailored applications to tier-1 companies.
Each application this week should take 45–90 minutes, not 10. You:
- Read the JD three times.
- Find the hiring manager on LinkedIn and read their last 10 posts.
- Tailor the resume at the bullet level, not the skill list level.
- Write a cover letter that quotes a specific detail about the team.
- Send a hiring-manager DM after applying (Template 2).
- Ask your network for a referral if anyone is at the company.
Volume drops to 2–3 per day. Quality is the constraint.
Also this week: phone screens from weeks 3–4 applications start landing. You'll have 4–8 of them. Prep each one specifically — 20 minutes researching the company, 10 minutes reviewing your own resume, 10 minutes on likely questions.
Week 6: first-round interviews
Goal: convert phone screens to onsites.
By week 6 you'll have a mix of phone screens and coding screens. Expected conversion from phone screen to next round: 40–60% for well-qualified candidates. Lower, calibrate. Higher, start being pickier about which conversations you invest in.
Schedule practice:
- No more than 3 interviews a day.
- At least one prep block of 60–90 minutes before each.
- A 15-minute decompression after each to write down what went well and what didn't.
Keep applying — 5–10 new applications this week, focused on anything that appeared on your radar from networking in week 4. Pipeline discipline matters. Most candidates stop applying the moment they get a few interviews; that's how 6-week searches become 14-week searches when the first pipeline dries up.
Week 7: onsite loops and deep prep
Goal: perform in onsites; open second pipeline for contingency.
Onsites are 3–5 hours and take 10+ hours of prep each. Block them. For engineering roles this means coding under time pressure, system design, and behavioral. For PM roles, case studies, product sense, and behavioral. Know the format for each company — ask the recruiter directly if you're unsure.
Keep one or two hours a day on new applications. The goal is not to relax because you have three onsites; it's to keep the pipeline warm in case none convert.
Week 8: offers, negotiation, decision
Goal: convert onsites to offers; negotiate; decide.
Expected conversion from onsite to offer: 25–40%. Two offers from five onsites is a strong outcome.
Negotiation rules:
- Never accept the first number. Always counter, even if the offer feels great.
- Counter with a range, not a number. "I was expecting something closer to $X–$Y based on my research and other processes I'm in."
- Use competing offers as leverage, but honestly. If you don't have another offer, don't invent one — recruiters talk.
- The signing bonus is negotiable. So is equity. Base is the hardest to move.
Before you negotiate, know the market number. Comp has moved a lot in 2026 — our software engineer salary guide is a good sanity check.
What to do if week 8 doesn't produce an offer
It happens. 8 weeks is a median, not a guarantee. If you're at week 8 with no offers but healthy pipeline (multiple onsites, several phone screens a week), keep going — you're close. If you're at week 8 with no interviews at all, the problem is upstream: either the resume isn't landing, the targeting is wrong, or the market for your current level is soft.
Go back to week 1. Redo the gap analysis. The candidates who search the longest are usually the ones who refuse to diagnose what's actually broken.
The bottom line
A job search is a compounding process: week 1 decisions shape week 8 outcomes. The candidates who move fastest aren't the ones working the most hours. They're the ones with a sequence that makes each week build on the last.
Print the 8 weeks. Put them on a wall. Move through them in order. Don't skip week 1.
