What Are Speed Drills?
Speed drills are short, repetitive, high-intensity DSA implementation exercises designed to:- Improve code recall speed (from concept to code).
- Build muscle memory for common algorithms and patterns.
- Reduce the cognitive load in real interviews (so you think about approach, not syntax).
- Increase your ability to write bug-free template code under pressure.
Think of them as the LeetCode equivalent of warm-up and sprint intervals in athletic training.
You’re not solving new problems here — you’re practicing templates and pattern recognition until they become second nature.
What Comes Under Speed Drills? (Types of Drills)
Speed drills focus on the core algorithmic building blocks that form 90% of coding interviews. We’ll divide them by category.1. Core Algorithmic Templates (Implement Blindly)
These are must be able to write in 2 mins items:2. Pattern-Based Recognition Drills
Once you can code the base templates fast, you move to pattern recognition speed drills — identifying the pattern from problem statements within 1–2 minutes. Common Drills:3. Structural “Mini Drills”
These are mini 10–15 min sets of 4–6 tiny tasks, done fast and repeatedly. Example structure for a “Graph drill” session:When to practice?
1. Daily Micro Speed Drill (5–15 minutes)
- Every weekday, during your DSA session, end with speed drills.
- Pick 1 topic per day (cycling weekly):
2. Weekly Deep Speed Session (Saturday, 45–60m)
- Every weekend morning (after 1–2h of regular DSA):
- Pick 2 core patterns (e.g., DP + Sliding Window).
- Write 5 problems each from memory, timed.
- Compare to target thresholds (see below).
- Track in your Speed Log Sheet (problem | pattern | time | correctness | notes).
4. Speed Targets & Measurement
Every 2 weeks, your median implementation time across 10 speed drills should hit the targets:5. How to Perform a Speed Drill (exact steps)
- Pick a template topic (e.g., BFS).
- Set timer (e.g., 3 minutes).
- Start writing from memory — no IDE autocomplete.
- Code complete function with small test harness (optional).
- Stop timer.
- Verify correctness quickly (does it compile/return expected).
- Record time + error count in log.
- Repeat 5–6 times with small variations (directed/undirected, recursive/iterative).
6. Speed Drill Kit Setup
Program
Key components:- Weekly short speed drills (daily micro-sessions)
- Weekly long speed drills (one session per week)
- Coverage mapping (which topics/pattern groups from the sheet map to which drill weeks)
- Tracking & metrics (time logs, error logs, improvement targets)
- Variation & review (once you’ve coded, revisit the hardest ones, add to SRS)
Mapping
Weekly Short & Long Sessions (12-Week Drill Schedule)
Coverage Strategy over 450 Problems
- Map the 450 problems into the topic clusters (as above). Each week you handle new problems + revisit older ones via speed drills.
- Use a problem queue: Each week, assign “new problems” from the sheet (target: ~38 problems/week). Among them, select 5–10 as speed-drill candidates (i.e., templates you’ll learn to write fast).
- Mark them in your spreadsheet with categories:
- T = Template (for speed drills)
- R = Re-solve (timed)
- D = Deep-fix (hard / failed) Make sure every template problem appears in a daily micro-drill within that week/one after.
Example Week 1 Speed Drill Plan (detailed)
Week 1 (Arrays & Math Basics) Daily micro-drill topics:- Mon: Two-pointer skeleton (e.g., “3Sum”)
- Tue: Prefix-sum skeleton (e.g., “Subarray Sum K”)
- Wed: Sliding window skeleton (e.g., “Longest Substring Without Repeating”)
- Thu: Basic sorting skeleton (e.g., “Merge two sorted arrays without extra space”)
- Fri: Math/array variant (e.g., “Kadane’s algorithm for max subarray sum”)
- Saturday long drill: pick 5 problems from sheet (Arrays medium/hard) → time each, review.
- Sunday: Weekly topic test on Arrays (timed) + speed drill review (convert templates you failed into SRS cards).