Everything on this site, in one place, organized by what you're trying to do. Each guide stands alone, but they're written to compound: the strategy explains why, the pattern series teaches how, the plans schedule it, and the company guides aim it. This page stays updated as new guides publish, so it's the one to bookmark.
If you're brand new, the fastest path: read the strategy manifesto, skim the pattern field guide, pick your timeline, and start Week 1. That's four links, and they're the first four below.
1. The strategy (read these first)
- Learn the Patterns, Not the Problems: the argument behind everything here: why grinding 500 problems fails, and what interviews actually measure.
- Why Is LeetCode So Hard?: the cognitive-science companion: the missing skill is recognition, and it's trainable.
2. The patterns
- LeetCode Patterns: The Complete Guide to All 42: the hub. Every pattern's tell, the cheat sheet, the three-signal diagnosis method, and the training system. If you read one technical page here, read this one.
The deep-dive series, one pattern at a time (tell, templates with code, mistakes, practice ladder):
- Sliding Window: the template that solves 20+ problems.
- Two Pointers: three templates and the discard argument interviewers grade.
- Fast & Slow Pointers: cycle detection in O(1) space.
- Merge Intervals: one overlap test, one sort, one sweep.
- Monotonic Stack: the pattern nobody taught you.
- Top 'K' Elements: the heap pattern, and why k-largest means min-heap.
More are on the way; each new deep dive is added here and to the hub the day it publishes.
3. Plan your prep
- How Long Does It Take to Prepare?: honest timelines by situation, measured in milestones rather than hours.
- How Many LeetCode Problems Should You Solve?: the count question, answered by scenario.
- The 4-Week Study Plan, Week by Week: the day-by-day version for working engineers with a month.
4. Choose your resources (the honest reviews)
- Blind 75 vs NeetCode 150 vs Grokking 75: the list decision, by timeline.
- Grokking the Coding Interview vs NeetCode: course versus platform, from the course's author, with the disclosure up front.
- Is Grokking the Coding Interview Worth It?: our own course, reviewed the way we'd want anyone to review it.
- Is NeetCode 150 Enough for FAANG?: what the best free list covers, and the three gaps between finishing it and passing.
- Is Cracking the Coding Interview Still Worth It?: the classic book, audited honestly a decade on.
- The Only 75 Problems You Need (Grokking 75): the full list, free, with its 6-week schedule.
5. Company guides
- Meta Coding Interview: The Patterns That Actually Show Up: the speed bar, the tiers, the 4-week Meta plan.
- Amazon Coding Interview: The Patterns That Actually Show Up: the OA, the Bar Raiser, and why Leadership Principles are half your score.
Google and Microsoft guides are planned; the AI-era guides below cover Google's new round today.
6. The AI-era interviews
- Meta's AI-Assisted Coding Interview: the new round's format, the rubric (prompting isn't on it), and five prep drills.
- Google's AI-Assisted Coding Interview: how Google's pilot differs, and why your prompts are graded artifacts there.
Where the courses fit
The guides above are free and complete on their own. When you want the problems curated, sequenced, and taught rather than assembled: Grokking the Coding Interview is the full 42-pattern curriculum with 300+ problems ($79, lifetime access), and Grokking 75 is the 6-week essential track for short timelines. Both are built on exactly the philosophy this library teaches.
Suggested orders, by situation:
- Interview in a month: timeline guide → 4-week plan → hub → deep dives as needed → your company's guide.
- Interview at Meta or Amazon specifically: company guide first (it tells you where to aim), then the hub and the tiers it names.
- Just starting to think about switching jobs: strategy manifesto → why-LeetCode-is-hard → timeline guide, and give yourself the runway the honest numbers ask for.
- Choosing what to buy (or not buy): the reviews section, top to bottom; they're written to be useful even if you never spend a dollar here.