Study Plan

Grind 75

75 LeetCode problems that cover every pattern top companies test. Customize your weekly schedule, filter by difficulty, and track your progress as you go.

Hours/week
8
Weeks
8

75

Problems

32h 15m

Total time

0%

0 done

15m
20m
20m
15m
15m
15m
15m
20m
15m
20m
20m
15m
20m
20m
20m
20m
15m
30m
20m
15m
15m
20m
20m
25m
30m
30m
25m
30m
25m
20m
25m
30m
30m
30m
30m
30m
35m
30m
25m
30m
30m
25m
25m
30m
20m
20m
30m
30m
35m
30m
25m
35m
45m
40m
45m

Topics covered

Array
12
Binary Tree
9
Graph
8
String
7
Stack
6
Dynamic Programming
5
Linked List
5
Binary Search
4
Heap
4
Recursion
3
Binary Search Tree
3
Trie
2
Hash Table
1
Binary
1
Matrix
1

What is Grind 75 and why does it work?

Grind 75 is a curated list of 75 LeetCode problems designed to give you maximum interview coverage with minimum time investment. Created by Yangshun Tay, the same engineer behind the Tech Interview Handbook and the original Blind 75, this list represents years of refinement based on real interview data.

The problems are sequenced intentionally. You start with foundational patterns like two pointers, hash maps, and basic tree traversals. By the time you reach the Hard problems in weeks 7-8, you've already built the mental models needed to tackle them. This is not a random collection of problems. It is a curriculum.

Each problem targets a specific pattern that shows up repeatedly in real interviews. Two Sum teaches hash map lookups. Valid Parentheses teaches stack-based matching. Number of Islands teaches graph traversal. Once you internalize these patterns, you can recognize and solve variations you have never seen before.

How to get the most out of Grind 75

1. Set a time limit per problem. The time estimates next to each problem are realistic targets. If you cannot solve a problem within the time limit, study the solution. Understanding the pattern matters more than arriving at it yourself.

2. Explain your approach out loud. Solving a problem silently and explaining it to an interviewer are two completely different skills. Practice verbalizing your thought process: what approach you are considering, why, and what the tradeoffs are.

3. Review problems you got wrong. Come back to failed problems after 2-3 days. Spaced repetition is how patterns stick. If you solved a problem but it took too long, that counts as a problem you need to revisit.

4. Simulate real interviews. Once you have solved 20-30 problems, start doing mock interviews. An AI-powered mock interview puts you under real pressure with time constraints, follow-up questions, and a scorecard that shows exactly where you need improvement.

Grind 75 vs Blind 75 vs NeetCode 150

Blind 75 is the original curated list that started the trend. It covers the core patterns but lacks structured ordering and time estimates. Good if you want the classics, but the sequencing is suboptimal for learning.

Grind 75 (this page) is the direct successor to Blind 75, by the same author. It fixes the ordering, adds time estimates, and is customizable. You can adjust the number of weeks and hours per week to fit your schedule. Best for structured, time-boxed preparation.

NeetCode 150 expands to 150 problems for more comprehensive coverage. Good if you have 2-3 months, but can be overwhelming on a tight timeline. Many candidates find that 75 well-practiced problems beat 150 rushed ones.

Our recommendation: start with Grind 75. If you finish with time to spare and want more coverage, expand to NeetCode 150. Quality beats quantity. Check which problems your target company actually asks on our company interview questions page.

Frequently Asked Questions

What is Grind 75?add

Grind 75 is a curated list of 75 LeetCode problems selected to cover every major coding interview pattern. It was created by Yangshun Tay, an ex-Meta Staff Engineer, as an improved version of the original Blind 75 list. The problems are ordered by difficulty and topic to build your skills progressively.

How is Grind 75 different from Blind 75?add

Grind 75 is the successor to Blind 75, created by the same author. It reorders problems for better learning progression and adds time estimates so you can plan your study schedule. The problems cover more topics and edge cases than the original Blind 75.

How long does it take to complete Grind 75?add

At 8 hours per week, you can complete all 75 problems in about 8 weeks. If you can dedicate 15-20 hours per week, you could finish in 3-4 weeks. Use the controls above to customize your schedule based on your available time.

Should I do Grind 75 problems in order?add

Yes. The problems are ordered intentionally. Easier problems come first to build foundational patterns, and later problems build on those patterns. Skipping ahead to Hard problems before mastering the Easy and Medium ones often leads to frustration and slower progress.

Is Grind 75 enough to pass a FAANG interview?add

For most candidates, completing Grind 75 thoroughly provides solid coverage for coding interviews at top tech companies. The key is depth over breadth: understanding why each solution works, being able to explain your approach, and recognizing patterns in new problems.

What topics does Grind 75 cover?add

Grind 75 covers arrays, strings, linked lists, trees, graphs, dynamic programming, binary search, stacks, heaps, tries, recursion, backtracking, sliding window, two pointers, and more. Each problem is tagged with its primary topic so you can focus on weak areas.

How should I practice Grind 75 problems effectively?add

For each problem: (1) spend 15-20 minutes trying without hints, (2) if stuck, read the approach but code it yourself, (3) after solving, study the optimal solution and understand the pattern, (4) practice explaining your approach out loud. Mock interviews with an AI interviewer can simulate real interview pressure and help you practice communication alongside problem-solving.

Knowing the problems is step one

Solving them under pressure, explaining your thinking, and handling follow-ups is what gets you the offer. Practice with an AI interviewer that simulates the real thing.

Try a free mock interviewarrow_forward