Start from a pattern, not a random title
1,672 problems · Array scanning plus hash lookup
Open topic pageString699 problems · State transition dynamic programming
Open topic pageHash Table610 problems · Array scanning plus hash lookup
Open topic pageDynamic Programming529 problems · State transition dynamic programming
Open topic pageMath528 problems · Array plus Math
Open topic pageSorting400 problems · Array scanning plus hash lookup
Open topic pageGreedy377 problems · Greedy choice plus invariant validation
Open topic pageBinary Search265 problems · Binary search over the valid answer space
Open topic pageDepth-First Search252 problems · Binary-tree traversal and state tracking
Open topic pageMatrix221 problems · Array plus Matrix
Open topic pageBit Manipulation220 problems · State transition dynamic programming
Open topic pageBreadth-First Search197 problems · Binary-tree traversal and state tracking
Open topic pageTree191 problems · Binary-tree traversal and state tracking
Open topic pagePrefix Sum186 problems · Binary search over the valid answer space
Open topic pageTwo Pointers182 problems · Two-pointer scanning with invariant tracking
Open topic pageSimulation171 problems · Array plus Simulation
Open topic pageHeap (Priority Queue)169 problems · Array scanning plus hash lookup
Open topic pageCounting149 problems · Array scanning plus hash lookup
Open topic pageGraph141 problems · Graph traversal with depth-first search
Open topic pageStack140 problems · Stack-based state management
Open topic pageSliding Window133 problems · Sliding window with running state updates
Open topic pageBinary Tree130 problems · Binary-tree traversal and state tracking
Open topic pageEnumeration118 problems · Array scanning plus hash lookup
Open topic pageDesign94 problems · Array scanning plus hash lookup
Open topic pageTopic pages give the LeetCode cluster a cleaner structure for both users and crawlers. Instead of treating every problem as an isolated leaf, GhostInterview groups related questions under one pattern page so you can move from broad intent to narrow execution without losing context. That is better for study flow, better for internal linking, and better for search engines trying to understand the shape of the library.
Why Topic Pages Matter
The fastest way to improve coding interview performance is not to random-walk through unrelated problems. It is to repeat one pattern until the explanation becomes stable. Topic pages support that by collecting the questions that share a family resemblance: array scans, binary search, graph traversal, dynamic programming, and other pattern-heavy groups that show up repeatedly in live loops.
Pattern-first prep is easier to repeat
When you stay inside one topic, you are not starting from zero every time. You are practicing the same mental move with slightly different constraints, which is what makes the explanation sharper under pressure.
Topic hubs are better discovery layers
The broad LeetCode hub is still useful when you want to search by title or difficulty. Topic pages take the next step and tell crawlers and users which groups of problems belong together.
How To Use These Pages
Pick a topic that matches your current weak spot, open its hub, and then select two or three representative problems from that page. Once the pattern feels stable, open GhostInterview and rehearse the explanation flow as if the interviewer were already pushing on trade-offs and complexity.
Start with topics that show up often
If you are unsure where to begin, start with arrays, strings, binary search, graphs, trees, and dynamic programming. Those patterns cover a large share of common interview signal.
Keep each session narrow
One topic plus two or three problems is enough for a strong prep block. The point is to build transfer, not just consume more titles.
How GhostInterview Fits
Topic pages are the static discovery layer. Individual problem pages give you the exact breakdown. GhostInterview remains the live solver layer when you want answer paths, complexity framing, and follow-up support during a real coding interview workflow.
FAQ
What are these topic pages for?
They turn broad LeetCode patterns into crawlable hubs. Use them to stay inside one pattern family, compare representative problems, and move into a solver-first workflow faster.
How should I use a LeetCode topic page?
Start with one topic, scan the representative problems, and then open individual problem pages only after you know which pattern you want to reinforce.
Do these pages replace the main LeetCode hub?
No. The main hub is the broad discovery layer. Topic pages make the cluster more focused by grouping related interview questions under one pattern.
Will topic pages keep growing as more problems are generated?
Yes. They are derived from the problem index, so new problem pages automatically strengthen the matching topic hubs.
Why does this matter for live interviews?
Interview performance improves when you repeat one reasoning pattern across several related problems instead of jumping between unrelated questions.
Need direct help when the pattern is clear but execution is not?
Use GhostInterview as the solver layer after you choose the topic and the problem. The topic page narrows the family. The product helps you execute under pressure.