Study
System design, one building block at a time. I read a topic with my coach, then the deck below it tests me on it — including the exact questions I got wrong the first time. Learning in public while I prep for senior engineering interviews.
Algorithms
A live radar of my LeetCode strength across 14 topics — recency-decayed, difficulty-weighted — plus per-problem recall decks built from my own mistakes.
Term drills
Nouns on demand — the vocabulary interviewers listen for. Gear 1: multiple choice. Gear 2: name it, no options.
- System design
Lag, guarantees, breakers, tiers — 35 terms
multiple choice name it - DS & Algos
Patterns, invariants, structures — 23 terms
multiple choice - Which strategy?
Read a problem, pick the pattern — the first two minutes of every coding interview, drilled. 38 problems, wrong options drawn from my own recorded misfires.
multiple choice solved + queued
JavaScript
map, filter, reduce, find, sort. The one-liners a live coding round expects you to type without thinking, solved in a sandbox and checked against hidden cases.
System design
- Networking
DNS, TCP/UDP, HTTP, WebSockets, CDN
10 cards - Load balancing
L4 vs L7, strategies, health checks, statelessness
10 cards - Caching
Cache-aside, invalidation, stampedes, eviction
11 cards - Databases
SQL vs NoSQL, ACID, indexing
10 cards - Scaling
Vertical vs horizontal, replicas, sharding
10 cards - Storage
Object storage, tiering, the upload pattern
9 cards - Messaging
Queues, pub/sub, Kafka, idempotency
10 cards - Distributed systems
CAP, quorums, split brain
11 cards - API design
REST vs GraphQL vs gRPC, pagination, rate limits
10 cards