Skip to content

14-Day Interview Practice Ramp

This is the day-by-day calendar for the two weeks before a live-coding interview. The default is editor-first practice with comments, working code, focused tests, and one correction. Timed board or observed work appears only when pressure is the skill being trained. The broader method and rubric live in sheet 10.

Keep nearby

  • The booklet (booklet.pdf): decision trees and one algorithm per page.
  • Sheets 01, 03, 05: standard library, templates, and pattern triggers.
  • Sheet 10: interview method and optional pressure protocol.
  • Sheet 07: interview-day logistics for Week 2.

The daily editor loop

  1. Pick: run just study-spaced 1 and use its printed editor command.
  2. Think: write ordinary source comments or docstrings in your own words, then save and explicitly continue.
  3. Build: implement in the isolated source and add cases in your test tab.
  4. Check: use /continue or just practice-next, then run just practice-test or just practice-repl.
  5. Reflect: trace one example and reconcile comments with the code.
  6. Close: name one win and one fix, then run just practice-finish "one specific fix". This saves the note and schedules review together.

Four-hour allocation

TimeWork
0:00-0:10Arrival ritual: breathing + worry dump + reappraisal + choose first draw
0:10-1:40One or two cold editor reps with comments, code, and focused tests
1:40-1:55Real break
1:55-2:55Trace, REPL, and test work on the single largest miss
2:55-3:40Optional observed or timed rep; otherwise another editor rep
3:40-4:00One-fix closeout and tomorrow's first draw

Example cycle (fill in your own dates)

This run: Day 1 = Sun Jul 5, 2026, interviews ≈ Jul 20. Adjust the anchor; the shape holds for any two-week window.

Week 1: build the editor reflex

DayFocusProblemsSheets openObserver
1Read sheet 10, then easy arraysarrays two_sum, arrays group_anagrams10, 03, 01none
2Arrays + stacks/queuesarrays product_except_self, stacks_queues valid_parentheses, stacks_queues daily_temperatures03, 05, 01none
3Sliding window + binary search; narrate one recovery from a blanksliding_window longest_substring_no_repeat, searching binary_search, searching search_rotated_array03, 05none
4BFS/DFS + linked listsgraphs number_of_islands, graphs course_schedule, linked_lists reverse_linked_list03, 02none
5Trees + heaps; first optional human-observed editor reptrees validate_bst, trees level_order_traversal, heaps kth_largest02, 03person
6Trees/trie + shore up your weakest rubric rowtrees trie, 2 review draws08, 02person
7Rest (or one light review rep). Rest is training.nonenonenone

Week 2: breadth plus optional pressure

DayFocusProblemsSheets openObserver
8Graphs, the heaviest topicgraphs dijkstra, graphs topological_sort, graphs bellman_ford03, 06optional person
9Dynamic programmingdp coin_change, dp edit_distance, dp knapsack, dp longest_increasing_subseq03person interrupts
10Mixed cold draws; optionally time one editor rep at 35 minutesjust study-spaced 307, 05optional person
11Backtracking + greedy + stringsbacktracking subsets, backtracking n_queens, greedy merge_intervals, strings valid_palindrome03, 05person
12Observed live-coding mock with back-to-back editor problems3 cold draws07, 10 (§7 card)person
13Taper. Review your best rep notes and run one light editor rep.1 easy draw10 (§7)none
14Rest. Read the sheet-10 §7 card and sheet 07.none10 (§7), 07none

The target is one improved signal per day, not a perfect score or a completed row count.

This page lives in git. Anyone can propose an edit. Edit this page View source

Editor-first interview practice. Content is tracked in git, and every packet page links to its source.

built from bb84dc1