Coming Soon.
The conceptual deck is live. This one takes longer to build right — every problem needs a completion target, progressive hints, a clean solution, and a guide that actually explains the thinking. That takes time to write once and write well.
Every problem ships with an expected completion window — 20 min, 30 min, 45 min. So you know if you're pacing right before you even start. Not a countdown, just a reference point.
Complete question with context, constraints, input/output examples, and edge cases called out explicitly. Written the way interviewers actually phrase them — not watered-down.
Hints are hidden by default and appear one at a time on click. Start with a directional nudge, then a structural one, then near-full guidance — so you only take what you actually need.
The solution is hidden until you ask for it. When you reveal it, you get the code and a step-by-step breakdown — every decision explained, not just the answer dumped.
Problem
Implement a search input that fires an API call only after the user has stopped typing for 300ms. The component should show a loading indicator while waiting and cancel any in-flight request if the query changes.
Hints
Solution + Guide
↑ this is what every problem will look like when it ships.
// In the meantime
The conceptual deck is fully live.