verdict
Candidate did not advance on LRU Cache. Core get/put behavior and a capacity guard appeared only late , while the optimal hash-map + DLL approach was never independently completed . Some list mechanics were verbalized , but the implementation stayed incorrect: moveToHead repair unfinished and put/eviction/map sync wrong at the end . After the runner failed, no dry-run replaced execution ; get recency stayed verbal only . Timer expired over budget with integrity review for unrelated pastes and admitted design blockage—do not advance.
rubric breakdown
Score 1: optimal hash-map+DLL not independently demonstrated; stuck on non-O(1) eviction ideas; interviewer help still not internalized.
Score 1: run infra failed; no substitute dry-run of sample or edges; verification ineffective.
2 of 5 written follow-ups correct
LRU Cache
gaps remainmediumhash-maplinked-listdesign35m 09s
solve time
proctoring & anomalies
Candidate identity and raw integrity evidence are omitted from this public excerpt.
strengths
+ Eventually stated core get/put API behavior and an invalid-capacity guard
+ Verbalized some linked-list unlink/tail mechanics mid-session
+ Produced partial follow-up discussion of recency updates on get
growth areas
− approach — Independently derive and state hash map keyed to DLL nodes with O(1) move-to-head and tail eviction before coding; do not stall on timestamp/sorted-map scans.
− code_quality — Finish put (insert/update + capacity eviction), correct bidirectional pointer wiring, keep helpers inside the class, and keep map and list synchronized on every mutation.
− testing — When the runner fails, immediately dry-run capacity-2 sample plus empty, update-existing, capacity-1, and single-node cases on the board.
− problem_understanding — Up-front systematic clarification of capacity edges, update-vs-insert, and eviction order rather than late partial restatements.
− integrity/process — Stay on the assigned design; avoid pasting unrelated binary-search prose when stuck.