constexpr — Pay at Compile Time, Not Runtime
Signal: Whether the candidate uses the compile-time evaluator to push work off the hot path.
Modern C++ patterns with HFT-grade explanations.
Signal: Whether the candidate uses the compile-time evaluator to push work off the hot path.
Signal: The 'do you think about latency' question. Tests breadth and ability to reason about microarchitectural effects.
Signal: Tests whether the candidate understands rvalue references and how to avoid unnecessary copies. Critical for hot-path code.
Signal: Whether the candidate uses the right tool. Reaching for raw pointers when references suffice signals C-with-classes thinking.
Signal: Whether the candidate knows allocations cost orders of magnitude more than ALU ops, and how to write code without them.
Signal: Knowing when and how to hint the optimizer. Mostly cosmetic but reveals familiarity with branch predictor behavior.
Signal: Whether the candidate writes self-documenting struct initializations. Mostly cosmetic but reveals fluency with C++20.
Signal: Whether the candidate knows why two atomics in the same struct can destroy performance even when they're never touched together.
Signal: Whether the candidate writes generic code and uses concepts to constrain it. Error messages drop from 50 lines of template spew to 1 line.
Signal: Tests whether the candidate defaults to unique_ptr (correct) or shared_ptr (overused).
Signal: Tests whether the candidate knows how to control compile times and ABI stability in large codebases.
Signal: Whether the candidate knows about TLS overhead and when to use it instead of locking.
Signal: Whether the candidate optimizes for the access pattern of their hot loop, not for OOP cleanliness.
Signal: Whether the candidate has actually built or read an order book. Reveals data structure judgment under realistic constraints.
Signal: The deepest C++ topic an interviewer can probe. Separates senior from staff.
Signal: Whether the candidate knows compile-time polymorphism exists, and when each tool is right.
Signal: The single most important concept in C++. Reveals whether the candidate writes exception-safe code by default.
Signal: The canonical 'design a lock-free data structure' interview problem. Tests memory ordering, false sharing, and ABA.