A strong answer
A strong candidate frames When does a full specialization win over the primary template? around the exact memory layout, compiler semantics, and hardware execution model covered in Specialization: Customizing for One Type. Contrast the generic print fallback with custom bodies for string literals and owned strings, including the string header fix.
Your 0_Language/template/template_specilization.cpp defines a generic print plus two custom versions, but it omits the header that declares the string type. The fixed runnable form adds that include so both specializations compile:
Generic handling stays for numbers and books; string forms gain labeled, content-aware output without touching call sites.
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 full specialization for const char* and std::string print.
- Mastery of core invariant: Explain why C strings need content comparison, not address order.
- Mastery of core invariant: Predict overload choice between generic and specialized print.
- 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.