Complete-DSA-Preparation: A Curated Problem Index for Interview Practice

The Gap Complete-DSA-Preparation Tries to Fill

Interview preparation has a discovery problem. LeetCode and GeeksforGeeks each host hundreds of problems, and neither site imposes a study order by default. A candidate who opens either site without a plan tends to solve whatever looks familiar, which leaves gaps in topics like Tries or Backtracking until an interviewer asks about them.

This repository addresses that with a table of contents that runs from Time Complexity and Mathematics through Arrays, Searching, Sorting, Matrix, Hashing, String, Linked List, Stack, Queue, Tree, Binary Search Tree, Heap, Graph, Greedy, Backtracking, Dynamic Programming and Trie. Each section is a table with columns for the problem number, title, code, document, video, difficulty and tags. The audience is narrow and clear: a student preparing for placement interviews, most likely in India, where the README's UPI donation block and the FAANG-related topics point. The README also states that LeetCode and GeeksforGeeks together provide "a rich library of more than 500+ real coding interview questions," which is the pool this index draws from.

It is not a course with lessons. It is the syllabus page of a course, with the lessons living on other people's sites.

How the Topic Tables Are Structured

The mechanism is a Markdown table per topic. The Mathematics table, for example, lists rows such as "Factorial Of Number" linking to a GeeksforGeeks practice URL, "Prime Number" linking to another practice URL, and "Absolute value" linking instead to a GeeksforGeeks theory article. Difficulty appears as a colored square emoji in the source: green for Easy, orange for Medium, and the repository defines red for the harder tier. A Tag column carries short labels like Math, Modulo, Factorial and Prime.

The columns are unevenly filled. In the Mathematics rows shown in the README, the Code column is empty for every entry, and the Video column is empty as well. Some rows have a Theory link; others have only a practice link; a few have neither and rely on the title alone. That asymmetry is the honest state of a self-paced course that is assembled over time rather than generated. The README's opening line asks readers to star the repository "so you can keep up to date on any daily progress," which frames the tables as a work in progress rather than a finished reference.

The data flow is entirely manual: a learner reads the table, clicks out to LeetCode or GeeksforGeeks, solves the problem in their own editor, and returns to the next row. Nothing in the repository executes.

Getting the Repository and Reading a Table

There is no package to install. The repository's top-level entries are LICENSE, README.md, _config.yml, assets/ and img/, so the deliverable is documentation plus images and a Jekyll configuration file. The practical first step is cloning it so the Markdown renders locally and you can search it.

git clone https://github.com/helloworldbyprince/Complete-DSA-Preparation.git
cd Complete-DSA-Preparation

After the clone, the repository root contains the files listed above. Open README.md in any Markdown viewer or on GitHub to see the tables rendered with their colored difficulty squares.

From there the workflow is manual: follow the practice or theory link in a row, write your solution in a separate file, and test it in your own environment. The repository does not provide a runner, a test harness or a build step, and the README does not document rollback because there is nothing to roll back.

Where the Index Falls Short

The empty Code column is the first limitation a reader hits. A table row that says "Trailing zeroes in factorial" and links to a practice problem gives you a target, not a solution. If you are stuck, the repository does not help you get unstuck; you go back to GeeksforGeeks or search elsewhere. The Video column has the same problem, and the README's own reliance on emoji squares for difficulty means the tables carry no estimated time per problem, no prerequisite chain within a topic, and no indication of which rows are essential versus optional.

There is also a mismatch between the repository's stated purpose and its file inventory. The primary language reported for the repository is SCSS, which reflects the site styling in assets/ rather than algorithm implementations. A learner who clones this expecting C++ or Java solution files will find none at the top level. That is not a defect in the index itself, but it is the most likely source of disappointment.

Finally, the index is opinionated about sources without saying so. It points at LeetCode and GeeksforGeeks, and a candidate preparing for a company that favors a different problem set, or for a domain like systems design, will find the tables stop short of that ground.

Complete-DSA-Preparation Compared with NeetCode and Striver Sheets

The closest alternatives are curated problem lists such as NeetCode's roadmap and the Striver A2Z sheet. The difference is in what each one treats as the product. NeetCode's roadmap pairs each problem with a video explanation and, for many, a written solution, so the list and the teaching material live in one place. Striver's sheet is similarly integrated with a video series and a fixed ordering.

Complete-DSA-Preparation takes a lighter approach: it indexes problems and links out for theory, leaving the explanation and the code to the destination sites. That makes it cheaper to extend, which fits the README's "daily progress" framing, but it also means the value depends entirely on link quality and on the learner's ability to teach themselves from a GeeksforGeeks article. If you learn best from a single integrated source, the other two are a better fit. If you want a free, topic-ordered checklist that does not lock you into one instructor's video schedule, this index is usable as-is.

Licence, Maintenance and Upgrade Cost

The repository is MIT licensed, and the README shows the standard GitHub license badge pointing at the LICENSE file. MIT is permissive: it allows reuse and modification with attribution and without warranty. That matters less here than it would for code, because the repository's content is a list of links to third-party problems. Those problems, their statements and their editorials remain the property of LeetCode and GeeksforGeeks and are governed by those sites' terms, not by this repository's MIT grant. Copying problem text into your own fork is therefore a different question from copying the table structure.

The MIT terms also carry no warranty, which is the normal posture for a study index and worth stating plainly: nothing here guarantees that a linked problem still exists at the same URL.

On maintenance, the last push to the default branch was on 2026-09-22, and the repository is not archived. Upgrade cost is effectively zero in the software sense: there is no dependency graph, no version pinning and no migration path. The cost that does exist is link rot. Because the tables point outward, the useful maintenance work is checking that each practice and theory URL still resolves, and the README does not describe a process for that.

Editorial conclusion

Adopt this if you want a free, ordered problem list for interview practice and you already know how to compile and test your own C++ or Java solutions. Do not adopt it if you need runnable code, a graded curriculum, or a package you can install. Before committing, open the README's Mathematics and Bits Manipulation tables and confirm the Code and Video columns are populated for the topics you plan to study, because many rows list only a Title and a Theory link.

Frequently asked questions

Official sources

1. helloworldbyprince/Complete-DSA-Preparation on GitHub
2. Issues
3. License: MIT
4. Project website
5. README