Full Schedule
Working hours 9–6. Saturday & Sunday class 11–1. Free time maximised.
Day 1 — Wednesday
6 PM – 11 PM
Contains Dup, Valid Anagram, Two Sum, Group Anagrams, Top K
Product Except Self, Valid Sudoku, Encode/Decode, Longest Consecutive
Valid Palindrome, 3Sum, Container With Most Water, Trapping Rain Water
Best Stock, Longest Substr, Char Replacement, Permutation in String
Write pattern summaries. What did you struggle with? What was easy?
Day 2 — Thursday
6 PM – 11 PM
Binary Search, Search 2D Matrix, Koko Bananas, Find Min/Search Rotated
Valid Parentheses, Min Stack, RPE, Daily Temperatures, Largest Rectangle
Reverse LL, Merge Sorted, Cycle Detection, Remove Nth Node
Copy Random, LRU Cache, Merge K Lists, Add Two Numbers
Re-solve one problem you found hard without looking at solution
Day 3 — Friday
6 PM – 11 PM
Invert, Max Depth, Diameter, Balance, Same, Subtree, LCA BST
Level Order, Right Side, Validate BST, Kth Smallest
Max Path Sum, Serialize/Deserialize, Build from Preorder+Inorder
K Closest Points, Find Median Data Stream, Merge K Sorted Lists
Focus: explain each solution to yourself out loud (rubber duck)
Day 4 — Saturday
1 PM – 11 PM (class 11–1)
Climbing Stairs, House Robber I & II, Palindromic Substr, Coin Change
Decode Ways, LIS (O(n log n)), Word Break, Partition Equal Subset
Unique Paths, LCS, Edit Distance, Coin Change II
Number of Islands, Course Schedule I & II, Pacific Atlantic, Rotting Oranges
Max Subarray, Jump Game I & II, Merge Intervals, Meeting Rooms II
URL Shortener design (full) + Twitter Feed design (full)
Subsets, Combination Sum, Permutations — understand the template
Day 5 — Sunday
1 PM – 11 PM (class 11–1)
All 4 algorithms, Redis implementation, distributed rate limiting
Redis deep dive, eviction policies, multi-channel notification system
Parking Lot, SOLID principles, design patterns (Factory, Observer, Strategy)
Re-solve 3–4 problems you struggled with this week without hints
Set 45-min timer. Pick random medium problem. Narrate your thinking.
Design Twitter. Use the 5-step framework (STAR-D). Time: 45 min.
Prepare 3 STAR stories: technical challenge, conflict, production incident
Complexity table, patterns cheatsheet, system design key numbers
// Interview Day Protocol
Ask about input size, constraints, edge cases before writing any code.
Narrate your thought process. Interviewers are evaluating how you think, not just the final answer.
Always state the brute force O(n²) approach, then optimize. Shows structured thinking.
Trace through 1–2 examples manually before saying 'done'. Catch off-by-one errors.
Empty input, single element, all negatives, duplicates — mention them explicitly.
Always clarify requirements first. Scale, consistency vs availability, read vs write ratio.