DSA Sheet
A DSA sheet is a curated list of problems organized by topic and difficulty that serves as a structured curriculum for interview preparation. The most wide...
What a DSA Sheet Is and How to Use It Strategically
A DSA sheet is a curated list of problems organized by topic and difficulty that serves as a structured curriculum for interview preparation. The most widely used examples are Striver's SDE Sheet (180 problems), the NeetCode 150, the Blind 75, and various company-specific problem sets. Each sheet reflects its creator's judgment about which problems best cover the solution patterns that appear most frequently in technical interviews, allowing you to maximize preparation efficiency by avoiding redundant coverage.
The most common mistake when using a DSA sheet is treating it as a checklist to complete as fast as possible. Rushing through a sheet — solving problems with constant hint-checking, moving on after understanding the solution without practicing the implementation — produces a false sense of readiness. A more effective approach is to work through the sheet at a pace where you can solve each problem independently within 30-40 minutes before moving on. This typically means spending 2-3 weeks per major topic section rather than completing the entire sheet in a month.
Use a DSA sheet as a spine, not a complete curriculum. The sheet identifies which problems to practice; you supplement it with additional problems in your weak areas and fewer problems in your strong areas. After completing each problem on the sheet, rate your confidence (1-3) and add low-confidence problems to a review queue. Revisit the review queue every two weeks, attempting problems again from scratch until your confidence reaches 3. This spaced repetition built on top of the sheet structure dramatically improves long-term retention compared to sequential completion without review.
Comparing Popular DSA Sheets and Choosing the Right One
The Blind 75, originally compiled by a Facebook engineer, contains 75 problems that represent the minimum set needed to cover all major interview patterns. It is best for candidates with 4-8 weeks of preparation time who need comprehensive coverage without depth. The NeetCode 150 extends the Blind 75 with additional problems that provide better coverage of sliding window, two pointers, and advanced graph topics. The NeetCode website provides video explanations for each problem, making it beginner-friendly.
Striver's SDE Sheet (450-problem variant) or TCS/core interview sheets are more appropriate for candidates targeting Indian product companies or looking for comprehensive coverage of topics like segment trees, tries, and bit manipulation that are less common in Western FAANG interviews. The depth and breadth of Striver's sheet makes it a better 6-month plan than the 4-week Blind 75, but the two serve different goals.
Company-specific sheets (e.g., "Google top 100 problems on LeetCode") curated by the community provide useful signal about what a specific company emphasizes but should be treated with skepticism — problem sets change over time and the actual interview experience may differ from the curated list. A practical approach is to use a general sheet (Blind 75 or NeetCode 150) as your primary resource and then spend the final two weeks before a specific company interview supplementing with that company's frequently asked problems. Tracking your completion percentage and confidence ratings for each topic in a simple spreadsheet takes less than 5 minutes per session and provides objective visibility into your readiness.
Tracking Progress and Adapting the Sheet to Your Weaknesses
Progress tracking transforms a DSA sheet from a static list into a dynamic study plan. The minimum tracking you should do is logging whether you solved each problem independently (no hints), with hints, or could not solve it. Over time, this data reveals systematic weaknesses. If you needed hints on 8 of the 10 sliding window problems, that is a clear signal to spend another week on that topic before progressing.
Beyond binary solved/not-solved tracking, record the time taken and the type of bug encountered (wrong algorithm choice, correct algorithm with wrong implementation, off-by-one error, integer overflow, etc.). Categorizing bugs reveals whether your weakness is conceptual (need to review algorithm theory) or implementational (need more coding practice). These are different problems requiring different remedies — no amount of additional problem-solving fixes a conceptual gap, and no amount of reading fixes an implementation fluency gap.
Adapt the sheet dynamically based on your progress data. If you are consistently solving arrays and strings problems in under 20 minutes, de-prioritize that section and reallocate time to trees or DP. If you are 2 weeks from your interview date and have only covered 60% of the sheet, identify the highest-probability topics (graphs, DP, arrays) and prioritize completing those sections over finishing the lower-probability topics (tries, advanced graph algorithms). A concrete tip: in the final week before interviews, stop solving new problems and focus exclusively on reviewing problems you previously solved with hints, re-attempting them from scratch to verify that your understanding has solidified into reliable recall.