Everything you need to cram for a SWE interview.
18 reference notes — patterns, the Blind 75, system design, behavioral, and more. Free to read, no signup. When it's go time, a guided 24-hour sprint turns them into an hour-by-hour plan with checkpoints and a readiness score.
Coding & patterns
- DSA PatternsThe reusable templates behind 80% of LeetCode-style problems — two pointers, sliding window, BFS/DFS, and more. Memorize the skeleton, plug in the variation.
- Blind 75 SolutionsThe Blind 75 with brute-force and optimal solutions side by side — the actual answers interviewers want to hear, with the reasoning that gets you there.
- ConcurrencyThreads, processes, async, locks, and the common race patterns — and how to reason about them out loud in an interview.
System design
- High-Level System DesignCore distributed-systems building blocks plus 15 commonly-asked high-level design problems, worked end to end.
- Low-Level DesignSOLID, the key design patterns, and 15 low-level design problems with class structure and a Python skeleton for each.
- MicroservicesWhen to split a service (and when not to), the anti-patterns, service discovery, data patterns, and what to actually say in interviews.
- API DesignHow to design clean HTTP APIs and answer 'design the X API' questions — resources, versioning, pagination, and idempotency.
Foundations
- OS & NetworkingThe OS and networking fundamentals every SDE interview pokes at, plus the canonical 'what happens when you type a URL' walk-through.
- SQLThe SQL surface area asked in SDE interviews — joins, indexes, window functions — plus 15 classic problems with solutions (PostgreSQL).
- SecurityThe OWASP Top 10, authentication vs authorization, common attacks, and what to spot in a code-review round.
Infra & tooling
- Docker & KubernetesContainers, images, Compose, and Kubernetes pods/deployments/services — plus the 'when not to use Kubernetes' reasoning interviewers look for.
- AWS BasicsCommon AWS services mapped to the problem each one solves — enough to discuss intelligently in a system-design round.
- GitA working mental model, the commands you actually need, and how to recover from 'I think I broke prod with git.'
Engineering practices
- Code ReviewHow to do good code review, what to look for, and how to answer 'review this code' interview questions.
- DebuggingHow to answer 'tell me about a tough bug' and 'how would you debug X?' — a repeatable method, not war stories.
- TestingTest types, TDD, mocking, flaky tests, and the talking points that show you take quality seriously.