Saved In Your Browser • No Account

Blind 75 Tracker

75 problems, 18 topics. Mark what you solved, flag what needs another pass, and keep an honest revision queue instead of a checklist that lies to you.

Solved
0/75
Completion
0%
75 not started
Needs Revision
0
Solved with help, do again
By Difficulty
Easy 0/19
Medium 0/49
Hard 0/7

Showing 75 of 75 problems. Focus a row and press s for solved, r for revise, x to clear.

Move or clear your progress

Progress lives in this browser only. Export it to a file to carry it to another device or browser, then paste it back in there. Importing merges per problem using timestamps, so the newer record wins and nothing gets silently overwritten.

How to work through Blind 75

Blind 75 is a revision list, not a course. It works because the 75 problems map onto about fifteen patterns that interviewers reuse endlessly, so finishing it leaves you able to recognise a problem shape in the first minute rather than the fifteenth.

Go topic by topic in the order below rather than jumping around. Arrays and hashing first, then two pointers and sliding window, because almost everything later assumes you are comfortable scanning an array with two indices. Graphs and dynamic programming last, when you have the stamina for them.

Give each problem twenty five minutes. If you have not found the approach by then, read the editorial, understand it properly, then mark the problem for revision and move on. The mistake is sitting on one hard problem for two hours and calling it a productive evening.

Revise on a three day gap. A problem you understood on Monday and cannot reproduce on Thursday was never learned, and finding that out in week three is much better than finding it out in an interview.

Who this suits. Anyone with four to eight weeks before interviews who already knows the basics of arrays, recursion and hash maps.

Who it does not. Complete beginners. Blind 75 assumes you can already write a loop and a recursive function without looking things up.

Questions people ask

How long does Blind 75 take?

At two to three problems a day, 75 problems takes roughly 4 weeks including revision. Doubling the daily pace does not halve the time, because retention is the bottleneck, not throughput.

Where is my progress stored?

In your browser, using local storage. It is never uploaded, which means it works signed out and offline, and also means it does not follow you to another device unless you export and import the file.

What does the revision flag do?

Marking a problem for revision puts it in the revision queue, ordered oldest first. Use it for anything you solved by reading the editorial. Those are the problems that fail you in an interview.

Is Blind 75 enough on its own?

Complete beginners. Blind 75 assumes you can already write a loop and a recursive function without looking things up.

Are the problem links official?

Yes. Every problem links to its LeetCode page, and where a free video walkthrough exists it is linked too. This tracker adds progress tracking on top, it does not host the problems.

Credits and sources

Sheet credit: Originally compiled by Yangshun Tay. The original sheet is here. The problem listing used by this tracker comes from neetcode-gh/leetcode (MIT licensed). Problems are hosted by LeetCode, and every row links there. Listing last rebuilt 2026-09-08.