How is my interview problem progress saved?

All problem checkmarks and pattern completion statistics are saved strictly in your browser local storage. No account creation or server sync is required, ensuring total privacy.

How many problems should I solve per pattern?

We recommend solving 3 to 5 problems per algorithmic pattern: 1 easy problem to grasp the template, 2 medium problems to encounter edge cases and state variants, and 1 hard problem if targeting tier-1 tech firms.

What should I do after completing all patterns?

Transition into company-specific cram sheets (like Meta, Google, Amazon) and timed 45-minute mock whiteboard sessions without auto-complete to simulate real interview conditions.

Coding Interview Progress Tracker — Free DSA Checklist

How to Structure Your Coding Interview Preparation Routine

Blindly grinding hundreds of disconnected LeetCode problems without a tracking structure leads to quick burnout and low retention. Studies in cognitive science demonstrate that pattern-based spaced repetition delivers 3x higher recall speed during high-stress technical interviews than random problem grinding.

Stage 1: Foundational Pattern Recognition (Days 1–14)

Focus on mastering core templates: Two Pointers, Sliding Window, Fast & Slow Pointers, and Binary Search. Solve 3 representative problems per pattern to internalize index boundaries and invariants before attempting harder topics.

Stage 2: Non-Linear Structures & Graphs (Days 15–28)

Progress into BFS/DFS tree traversals, topological sorting, connected components, and heap/priority queue algorithms. Emphasize state deduplication using visited sets and coordinate hashing.

Stage 3: Dynamic Programming & Intervals (Days 29–42)

Tackle 1D/2D dynamic programming by starting from the recursive memoization tree, then inverting to iterative tabulation with space optimization. Practice merging and inserting overlapping intervals.

Stage 4: Timed Mock Whiteboard Simulations (Days 43–60)

Turn off syntax highlighting and code completion. Solve problems against a strict 35-minute timer while speaking your problem-solving steps out loud. Test edge cases (empty inputs, negatives, integer bounds) before running code.

The 3-Day Spaced Repetition Rule

When you struggle with a problem and need to consult the solution or editorial, do not mark it complete. Instead, log the problem in your review queue and attempt to solve it from scratch without looking at hints 72 hours later. If you can implement the optimal solution and state its complexity cleanly, your brain has successfully encoded the underlying algorithmic invariant.

My Progress

Progress by Pattern