Staff - 60 Day DSA Roadmap

Use 60-day pacing in the Plan Builder

1. 1
   Days 1–5

   Baseline and language#

   Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Goals

   • Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Focus

   concept

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

   Foundations and core repair#

   Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Goals

   • Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Focus

   conceptarrays-hashingtwo-pointersbinary-search

   Day 6: Recursion: make each call's contract explicitDay 8: Correctness: explain why the algorithm must workDay 9: Representation: decide what every value meansDay 10: Arrays & HashingDay 11: Two PointersDay 12: Binary Search
3. 3
   Days 19–33

   Structures and patterns#

   Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Goals

   • Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Focus

   linked-listtreesbacktrackinggraphs

   Day 19: Linked ListDay 20: TreesDay 22: BacktrackingDay 23: Graphs
4. 4
   Days 34–43

   Variants and selected extensions#

   Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Goals

   • Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Focus

   practiceconcept

   Day 34: Component count after each connectionDay 36: Minimum spanning forestDay 37: Minimum dictionary tokenizationDay 38: Merge timestamped streamsDay 39: Integer arithmetic and coordinate reasoning
5. 5
   Days 44–51

   Mixed and confirmed-format practice#

   Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Goals

   • Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Focus

   review

   Day 44: Clarify a changed contract before coding
6. 6
   Days 52–57

   Mocks and targeted recovery#

   Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Goals

   • Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Focus

   mockreview

   Day 52: Staff - Diagnostic Traversal and Dependency ReviewDay 53: Turn one failure into a regression test
7. 7
   Days 58–60

   Consolidation and buffer#

   Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Goals

   • Complete format-specific tasks, review a bounded implementation, and explain integration trade-offs while keeping algorithm scope diagnostic-driven.

   Focus

   review

   Day 58: Review and transfer from the mistake logDay 59: Rehearse the final checklist without cramming