Practice the parts of an interview that are hard to fake.
Trace the code
Read a snippet and predict what really happens: object lifetimes, memory ordering, syscalls, cache behavior. Every answer comes with a full explanation.
Write real solutions
Implement locks, queues, and data structures in C++ or Rust, then run them against hidden tests in a sandbox.
Know where you stand
Accuracy by topic, a review queue of the questions you missed, and a streak to keep you coming back.
Topics
Pick one to focus on, or mix them all.
- C++Language semantics, memory model, RAII, move semantics, STL, and modern C++ gotchas.117
- Operating SystemsProcesses, virtual memory, scheduling, syscalls, and I/O.53
- ConcurrencyMemory ordering, data races, lock-free structures, and cache effects.51
- NetworkingTCP/IP fundamentals, socket semantics, and latency-sensitive I/O patterns.45
- Computer ArchitecturePipelining, branch prediction, cache hierarchies, and memory consistency at the hardware level.47
- Design PatternsClassic GoF patterns, modern C++ idioms, and the tradeoffs behind each one.44
- CompilersParsing, optimization passes, code generation, and how the compiler transforms your code.44
- GPU / CUDAWarp scheduling, memory coalescing, occupancy, and parallel kernel design.46
- Data Structures & AlgorithmsAdvanced data structures, algorithmic complexity, and problem-solving under constraints.46
- RustOwnership, borrowing, lifetimes, and the same systems-level gotchas as C++ resolved a different way.53
Your next interview won't be multiple choice.
Knowing why every wrong answer is wrong is how you get ready for it. Start with one question.
Start practicing