Senior / SDE III - 30 Day DSA Roadmap

Use 30-day pacing in the Plan Builder

1. 1
   Days 1–3

   Baseline and language#

   Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Goals

   • Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Focus

   concept

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

   Foundations and core repair#

   Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Goals

   • Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.
   • linked-list was omitted because 30 minutes did not fit an available 60-minute study day in Foundations and core repair.

   Focus

   conceptarrays-hashingtwo-pointersbinary-search

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

   Structures and patterns#

   Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Goals

   • Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Focus
4. 4
   Days 18–22

   Variants and selected extensions#

   Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Goals

   • Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Focus

   practice

   Day 18: Earliest finishes in a dependency planDay 19: Nearest declared grid exit
5. 5
   Days 23–25

   Mixed and confirmed-format practice#

   Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Goals

   • Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Focus

   review

   Day 23: Clarify a changed contract before coding
6. 6
   Days 26–28

   Mocks and targeted recovery#

   Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Goals

   • Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Focus

   mockreview

   Day 26: Senior - Ambiguous Reachability ContractDay 27: Turn one failure into a regression test
7. 7
   Days 29–30

   Consolidation and buffer#

   Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Goals

   • Clarify an ambiguous contract, implement a bounded core refresh, and write meaningful tests while preserving scheduled system-design, low-level-design, and leadership preparation.

   Focus

   review

   Day 29: Review and transfer from the mistake logDay 30: Rehearse the final checklist without cramming