A strong answer
A strong candidate frames How does a class template stamp a distinct class per argument list? around the exact memory layout, compiler semantics, and hardware execution model covered in Class Templates: A Generic Pair and Container. Describe Pair instantiation, layout per argument list, const-correct members, and header placement for member definitions.
One spelling serves coordinates, prices and catalogue entries. The lesson turns that sketch into a complete class template with correct construction and a stated instantiation model.
Three hand-written pair classes start alike. A week later one has a constant display method. Another lacks it. The third stores references with unclear lifetime. The compiler cannot warn about drift across copies. One template keeps behavior aligned because edits apply once.
In a production interview, always connect the specification rule to its concrete runtime consequence: state what lives on the stack versus the heap or static storage segment, how the compiler or operating system validates alignments, lifetimes, and error codes, and what happens under adversarial or boundary inputs (such as zero-length buffers, integer overflow, concurrent mutation, or partial I/O). Backing your explanation with a small trace of register/memory state transitions immediately separates senior systems engineers from candidates who only memorized syntax.
What the interviewer is listening for
- Mastery of core invariant: Write a class template with correct member definitions outside the class.
- Mastery of core invariant: Explain how Pair avoids code duplication across type pairs.
- Mastery of core invariant: Predict instantiation, size and copy behavior for chosen arguments.
- Hardware and ABI awareness: Explaining how sizes, alignments, calling conventions, or kernel boundaries behave on real 64-bit targets rather than relying on implementation-defined assumptions.
- Defensive engineering: Naming the exact compiler flags (
-Wall -Wextra -Werror), static analyzers, or runtime sanitizers (-fsanitize=address,undefined,thread) that verify correctness in CI.
Common mistakes
- Explaining only surface syntax without tracing the underlying memory addresses, ownership lifetime, or kernel/user-space state transitions.
- Assuming undefined behavior (such as signed overflow, uninitialized reads, strict-aliasing violations, or dangling pointers) will "just work" because it passed an unoptimized
-O0debug build. - Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.