Interview Sprint 8 Weeks
An 8-week frontend interview plan — JS, React, DSA, machine coding, system design, and mocks with weekly checkpoints.
- roadmaps
- interview-sprint
Eight weeks is enough to raise signal if you practice under time and review mocks. It is not enough to learn frontend from zero — use Frontend roadmap first if foundations are weak.
Who this plan assumes
- You can build React UIs day-to-day
- You want FE roles that may include DSA + UI coding + design
- ~10–14 focused hours/week
Adjust intensity; keep the order.
Weekly rhythm (template)
| Day focus | Activity |
|---|---|
| Mon–Tue | Concepts + notes you can teach |
| Wed–Thu | Timed coding / machine coding |
| Fri | System design outline or deep dive |
| Sat | Full mock (or 2 short) |
| Sun | Review rubric + light rest |
Self-review: Mock interview self review. Structure: How to structure answers.
Week 1 — Language & browser baseline
Goals: Event loop, closures, fetch/abort, load pipeline.
- JavaScript interview
- Event loop · Closures · Promises
- AbortController · Fetch
- How browsers load a page · Critical rendering path
- Browser interview questions
Checkpoint: Explain event loop with a mixed output prompt; debounce from memory — Debounce.
Week 2 — JS coding patterns + light DSA
- JS coding interview patterns
- Complexity analysis
- DSA: Two sum · Valid parentheses · Group anagrams · Longest substring
- Emitter / Promise.all / flatten drills
Checkpoint: 2 timed easy-medium problems with narration.
Week 3 — React depth
- React interview questions
- Reconciliation · Rules of Hooks
- useEffect · Keys
- useMemo/useCallback · React performance checklist
Checkpoint: Implement useDebouncedValue; explain stale closures.
Week 4 — Machine coding
- Machine coding framework
- Builds: Todo · Modal · Autocomplete · Infinite scroll
- A11y talking points
- Whiteboarding UI
Checkpoint: One 45-minute component from scratch with a11y pass.
Week 5 — DSA expansion (company-dependent)
Prioritize patterns over volume:
- Arrays/hash, windows, stacks
- Trees basics: Invert tree · Level order
- Graphs lite: Number of islands
- LRU cache
Checkpoint: 8–10 problems total this week timed; log misses.
Skip or shrink if target companies are UI-only — verify with recruiter.
Week 6 — System design (FE)
- System design FE framework
- Practice outlines: News feed · Autocomplete design · Image gallery · YouTube
- Performance talking points
- Security talking points
- Tradeoff language
Checkpoint: Two 45-minute designs with phases + non-functionals.
Week 7 — Full mocks + stories
- 3–4 mocks mixed types
- Behavioral stories — bank 8
- Explaining projects
- Senior signals if leveling up
- Common mistakes
- Debugging live · Network tab
Checkpoint: Rubric average ≥20/30 on two consecutive mocks.
Week 8 — Polish & logistics
- Light review notes; no new rabbit holes
- Company-specific: Experiences hub etc.
- Take-home strategy if relevant
- Offer negotiation basics
- Sleep, setup, environment checks
Checkpoint: One final mock early week; taper intensity.
Daily micro-drills (15–20 min)
- One verbal topic out loud
- One small util or flash pattern
- One mistake from last mock fixed
Tracking board
| Week | Mock score | Weakest skill | Drill |
|---|---|---|---|
| 1 | |||
| … | |||
| 8 |
Related on this site
- Interview hub
- DSA hub
- Machine coding hub
- System design hub
- JavaScript mastery path
- React career path
Further reading
Consistency beats heroic weekends. Protect mock review time — that is where the sprint compounds.