A strong answer
A strong candidate frames What is the TCP TIME_WAIT state and why does it exist? around the exact memory layout, compiler semantics, and hardware execution model covered in TCP State Machine and Socket Options: setsockopt, SO_REUSEADDR, and TIME_WAIT. Explain TIME_WAIT ensures delayed segments are not misinterpreted as new connections and SO_REUSEADDR allows rebinding.
You stop your server process with Ctrl+C or deploy a new binary. You launch the service two seconds later, and the program crashes immediately:
If you inspect the operating system using ss -tan or netstat -tan, you find no running process attached to port 8080. Instead, you see a socket entry lingering in the TIME_WAIT state:
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: Trace TCP state transitions across active close (FIN_WAIT, TIME_WAIT) and passive close (CLOSE_WAIT, LAST_ACK).
- Mastery of core invariant: Eliminate EADDRINUSE errors upon server restart using SO_REUSEADDR.
- Mastery of core invariant: Distribute incoming connection queues across worker threads using kernel SO_REUSEPORT load balancing.
- 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.