Interview prep timeline

Pick a target start date for applications, then work backward. Eight weeks is the default if you already write production code daily; six if you are returning to interview mode after recent practice; ten if data structures feel rusty.

Random grinding feels productive and still fails because you practiced the wrong skill or applied too late for offers to overlap. A good prep plan is calendar math plus deliberate practice, not a LeetCode streak counter.

Walking through eight weeks

Weeks 1–4: coding patterns

Focus on recognition speed, not volume. Work through a curated list (Blind 75 or NeetCode 150) by pattern: arrays/hashing, two pointers, sliding window, binary search, trees, graphs, heaps, intervals, DP. Target 1–2 quality problems per weekday and a longer weekend set.

1. Struggle 15–20 minutes before reading a solution.
2. Re-solve from scratch the next day without notes.
3. Keep a one-line "pattern trigger" note per problem ("sorted array + target sum → two pointers").
4. Time yourself once you know a pattern; aim for mediums in ~25 minutes.

If foundations are weak, spend week 1 on data structures in practice and language fluency (Python's heapq, collections.deque, typing) before grinding.

Weeks 3–6: system design (overlap with coding)

1. Refresh building blocks: load balancing, caching, sharding, queues, consistency.
2. Learn one delivery framework (requirements → API/entities → high-level design → deep dives) and reuse it every time. See the interview framework.
3. Practice 8–12 common prompts out loud: URL shortener, news feed, chat, rate limiter, ticket booking. Time-box 35–45 minutes.
4. After each attempt, fill gaps with Hello Interview / ByteByteGo writeups, then redesign once more.

Juniors interviewing for SDE1/new-grad may replace most of this block with more coding and light "API + database schema" design. Mid-levels and above should not skip design.

Behavioral throughout

Draft stories in week 1, not week 7. Build an 8–10 story bank mapped to ownership, conflict, failure, ambiguity, mentoring and impact. Practice out loud twice a week for 20 minutes. Numbers beat adjectives: "cut p99 from 800 ms to 120 ms" lands; "improved performance" does not.

Last 2–3 weeks: mocks

Mocks convert knowledge into interview performance. Details: mock interviews.

Keep a simple spreadsheet: date, problem or mock type, time, result (pass/fail/partial), one note on the failure mode. If "silent coding" appears three times, the next practice block is narration drills, not more DP videos.

When you are not actively interviewing, a light maintenance mode beats zero: one medium problem a week and one design sketch a month. When a recruiter ping arrives, you want yes within two weeks of sharpening — not eight weeks from cold.

Common mistakes

• Infinite problem count, zero mocks.
• Drafting behavioral stories the night before onsite.
• Opening ten new hard problems the night before. Sleep and logistics win.

Check yourself

You have four weeks and 80 well-reviewed mediums. What do you cut?

New problems. Spend the time on mocks and story polishing.

When do behavioral stories get drafted?

Week 1, not week 7. Practice them out loud twice a week.

Key takeaways

• Run 6–10 weeks with overlapping tracks: coding first, design overlapping, behavioral from day one, mocks last.
• Prefer curated pattern practice and spaced re-solves over infinite problem count.
• Track failure modes. Practice the failure, not a random new topic.
• Past ~100 solid mediums, mocks beat more problems.

Further learning

Next: mock interviews.

NeetCode roadmapPractice coding interviews with structured courses, AI-assisted assessments, head-to-head Versus mode, and 1,000+ problems.NeetCode