Skip to main content

LeetCode Interview Questions — 200+ Problems by Pattern

Every LeetCode problem organized by the algorithm pattern it tests. Learn the pattern, solve the problems, ace the interview. 103 high-frequency problems tagged by company.

Problems by Pattern

Click any pattern to see its problems with templates and tips.

Problems by Company

Practice the exact problems each company asks. Filter by your target company.

Top High-Frequency Problems

These problems appear most frequently across FAANG interviews. Start here if you're short on time.

Problem Difficulty
Longest Substring Without Repeating Characters Medium
Minimum Window Substring Hard
Two Sum II - Input Array Is Sorted Medium
3Sum Medium
Container With Most Water Medium
Trapping Rain Water Hard
Valid Palindrome Easy
Remove Duplicates from Sorted Array Easy
Binary Search Easy
Search in Rotated Sorted Array Medium
Find Minimum in Rotated Sorted Array Medium
Subarray Sum Equals K Medium
Product of Array Except Self Medium
Two Sum Easy
Group Anagrams Medium
Top K Frequent Elements Medium
Valid Anagram Easy
Longest Consecutive Sequence Medium
Valid Parentheses Easy
Min Stack Medium
Daily Temperatures Medium
Number of Islands Medium
Rotting Oranges Medium
Binary Tree Level Order Traversal Medium
Kth Largest Element in an Array Medium
Find Median from Data Stream Hard
Merge K Sorted Lists Hard
Reverse Linked List Easy
Linked List Cycle Easy
Merge Two Sorted Lists Easy

Curated Problem Lists

Frequently Asked Questions

How many LeetCode problems should I solve for interviews?

Quality beats quantity. Solving 75-150 well-chosen problems across all core patterns is more effective than grinding 500+ random ones. Focus on mastering each pattern with 5-10 representative problems before moving on. The Blind 75 and Grind 75 lists are the most efficient starting points.

What are the most important LeetCode problems for FAANG interviews?

The highest-frequency problems across FAANG companies: Two Sum (LC 1), Valid Parentheses (LC 20), Merge Two Sorted Lists (LC 21), Binary Search (LC 704), Maximum Subarray (LC 53), Climbing Stairs (LC 70), Coin Change (LC 322), Number of Islands (LC 200), Longest Substring Without Repeating Characters (LC 3), and LRU Cache (LC 146). These cover the most common patterns.

How long does it take to prepare for LeetCode interviews?

Most engineers need 8-12 weeks of focused preparation. If you have a solid CS foundation, 6-8 weeks is achievable. The key is consistency — 2 hours daily beats 8 hours on weekends. A pattern-first approach (learn the template, then solve 3-5 problems per pattern) is the most efficient path.

Should I use Python, Java, or C++ for LeetCode interviews?

Use the language you know best — interviewers care about your problem-solving approach, not your language choice. Python is the most popular for interviews because of its concise syntax and built-in data structures. Java and C++ are strong choices for performance-critical reasoning. All three are fully supported by LeetCode.

What is the difference between Blind 75 and NeetCode 150?

Blind 75 is the original curated list of 75 essential problems organized by data structure. NeetCode 150 extends it to 150 problems by adding coverage of Tries, Advanced Graphs, 2D DP, and Bit Manipulation. All 75 Blind 75 problems are included in NeetCode 150. If you have 4-6 weeks, do Blind 75. If you have 8+ weeks, do NeetCode 150.

Which LeetCode problems does Amazon ask most frequently?

Amazon's most frequently asked problems: Two Sum, Valid Parentheses, Merge Intervals, Product of Array Except Self, Top K Frequent Elements, LRU Cache, Word Search, Number of Islands, Binary Tree Level Order Traversal, and Coin Change. Amazon emphasizes arrays, trees, and BFS/DFS patterns. They also heavily test Leadership Principles alongside coding.

Which LeetCode problems does Google ask most frequently?

Google's most frequently asked problems: Merge Intervals, Meeting Rooms II, Product of Array Except Self, Binary Tree Maximum Path Sum, Word Ladder, Alien Dictionary, Trapping Rain Water, Edit Distance, Serialize/Deserialize Binary Tree, and Course Schedule. Google leans heavily on graph problems, dynamic programming, and problems requiring careful edge case handling.

Buy me a coffee