Skip to content
16-Week DSA Roadmap

Personal study roadmap · 2026–27

16 Weeks to Product-Company Interview Readiness

Beginner-level DSA, NeetCode-inspired problem practice, frontend interview fundamentals, revision and mock interviews. Built for a realistic two-hours-per-day schedule.

  • 16 weeks
  • 112 LeetCode problems
  • 2 hours / day
  • Product companies

Your progress

Focus on mastery, not just counts.

Work through 14 topic weeks, then dedicate weeks 15–16 to timed practice and revision. This plan intentionally prioritizes fundamentals over finishing every NeetCode 150 problem.

0 / 112Problems completed
0%Overall progress
0 / 14Weeks completed

Checklist progress is saved in this browser using local storage. Use “Export progress” to save a backup.

Daily rhythm

2 hours a day

  1. 20mLearn the pattern
  2. 65mSolve problems
  3. 25mReview solution
  4. 10mRevisit an old problem

Target 8 new problems per week, usually 1–2 per day, while reserving time for revision. A hard Medium may take an entire session; that's fine.

Method

How to learn from every problem

  1. Understand the constraints and formulate a brute-force idea.
  2. Try independently for 20–30 minutes before using a hint.
  3. Read the explanation if needed, close it, and reimplement without copying.
  4. Record the pattern, key insight, and time/space complexity.
  5. Revisit difficult questions after 2–3 days and again after 1–2 weeks.

Stretch questions: Word Ladder (Week 9) and Edit Distance (Week 11). Postpone these if needed. Difficulty is based on LeetCode categories and can evolve.

Your 14-week problem checklist

112 problems shown

Weeks 15–16

Revision + mock interviews

Week 15 · Mixed revision

Re-solve 12–15 problems you previously attempted. Prioritize Two Sum, 3Sum, Longest Substring, Search in Rotated Sorted Array, Daily Temperatures, Reverse Linked List, Tree Level Order, Number of Islands, Course Schedule, Coin Change, Merge Intervals and LRU Cache.

Week 16 · Interview simulation

  • 3 timed DSA mock interviews with no hints or autocomplete.
  • 2 JavaScript/React or role-specific technical sessions.
  • 1 frontend machine-coding round.
  • 1 project walkthrough + behavioral mock interview.
  • Review mistakes and return to weak patterns.

Benchmark:comfortably explain a solution and solve many unseen Medium questions within ~25–35 minutes, including complexity analysis.

Companion track

Product-company interview preparation

Suggested focus: around 65% DSA, 25% role-specific technical study and 10% projects, resume and mocks. The topics below suit frontend roles; for backend/full-stack, substitute APIs, SQL, databases and system design.

WhenAlongside DSA, study…
Weeks 1–2JavaScript fundamentals, closures, scope, hoisting, this
Weeks 3–4Promises, async/await, event loop, debouncing, throttling
Weeks 5–6React hooks, state, rendering, reconciliation
Weeks 7–8React performance, memoization, custom hooks
Weeks 9–10Machine coding: autocomplete, pagination, infinite scroll
Weeks 11–12Browser fundamentals, HTTP, caching, security and web performance
Weeks 13–14Frontend system design and project walkthroughs
Weeks 15–16Mock interviews, resume, referrals and applications

Start applying selectively around Weeks 9–10. Increase applications and mock interviews during the final month.

Readiness check

What success looks like

  • Identify likely patterns without being told the topic.
  • Solve most unfamiliar Easy problems independently.
  • Solve a substantial share of unseen Medium problems in ~35 minutes.
  • Explain time and space complexity clearly.
  • Implement DFS, BFS, binary search and basic DP patterns from memory.
  • Explain project decisions and technical trade-offs convincingly.

Shorter timeline

If you have only 3 months

Keep Weeks 1–8 unchanged. Combine Graphs, 1D DP, Greedy and Intervals in Weeks 9–10. Use Week 11 for revision and mock interviews, then Week 12 for timed interviews, frontend preparation and applications. Skip the most advanced graph, bit-manipulation and 2D DP exercises if necessary.

Principle:100–112 well-understood problems outperform 150 problems solved only once.