Patterns and Object-Oriented Design

The intervals lesson and the practical-coding lesson cover the loudest two shapes, but they leave gaps. Candidates who sat the Netflix loop report a sliding-window counting problem the intervals family never touches. They also report an object-oriented design round where the prompt is a class to build with a few operations and nothing to recognize from LeetCode. A binary search that hunts for a minimum capacity rounds out the three, and three more reported problems on a single sequence close the lesson. The dependency-ordering sort and the graph, tree, heap and DP problems have their own lesson, Graphs, Heaps & Dynamic Programming.

The Netflix angle

Netflix runs a decentralized loop, so the exact problem is team-picked and varies a lot from one panel to the next. So prepare shapes, since a memorized problem list transfers poorly between panels. The three here are ordinary patterns wearing a streaming label. A viewing session is an array you slide a window across, and a content catalog is a bag of records you design a query for. An encoding backlog is a schedule you binary-search. Pure puzzle-grinders get caught off guard by the object-oriented round, because there is no algorithm to recall, only a class to design cleanly and defend.