SDE II - 90 Day DSA Roadmap

Use 90-day pacing in the Plan Builder

1. 1
   Days 1–7

   Baseline and language#

   Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Goals

   • Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Focus

   concept

   Day 1: Refresh Python interview contractsDay 2: Complexity: name the work you are counting
2. 2
   Days 8–28

   Foundations and core repair#

   Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Goals

   • Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Focus

   conceptarrays-hashingtwo-pointersbinary-searchsliding-windowlinked-list

   Day 8: Recursion: make each call's contract explicitDay 9: Correctness: explain why the algorithm must workDay 10: Representation: decide what every value meansDay 11: Arrays & HashingDay 12: Two PointersDay 13: Binary SearchDay 15: Sliding WindowDay 16: Linked List
3. 3
   Days 29–49

   Structures and patterns#

   Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Goals

   • Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Focus

   treesheap-priority-queuebacktrackingintervalsgreedygraphsone-d-dpadvanced-graphstwo-d-dp

   Day 29: TreesDay 30: Heap / Priority QueueDay 31: BacktrackingDay 32: IntervalsDay 33: GreedyDay 34: GraphsDay 36: 1-D Dynamic ProgrammingDay 37: Advanced GraphsDay 38: 2-D Dynamic Programming
4. 4
   Days 50–64

   Variants and selected extensions#

   Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Goals

   • Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Focus

   practiceconcept

   Day 50: Fixed-window signal peaksDay 51: Earliest peak interval overlapDay 52: Earliest finishes in a dependency planDay 53: Nearest declared grid exitDay 54: Component count after each connectionDay 55: Minimum spanning forestDay 57: Integer arithmetic and coordinate reasoning
5. 5
   Days 65–76

   Mixed and confirmed-format practice#

   Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Goals

   • Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Focus

   review

   Day 65: Clarify a changed contract before coding
6. 6
   Days 77–85

   Mocks and targeted recovery#

   Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Goals

   • Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Focus

   mockreview

   Day 78: SDE II - Bounded Stream MergeDay 79: Turn one failure into a regression test
7. 7
   Days 86–90

   Consolidation and buffer#

   Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Goals

   • Solve unseen variants, articulate a credible alternative, and strengthen error handling and tests rather than inflating solved count.

   Focus

   review

   Day 86: Review and transfer from the mistake logDay 87: Rehearse the final checklist without cramming