What is false sharing and how do you avoid it?

A strong answer

A strong candidate frames What is false sharing and how do you avoid it? around the exact memory layout, compiler semantics, and hardware execution model covered in Cache-Conscious Data Structures: Alignment, False Sharing, and Structure of Arrays. Explain cache-line contention when threads modify different variables on the same line, and padding/alignment fixes.

Object-oriented design and traditional C programming encourage grouping related attributes together into a single composite type:

This code looks clean, but look at the hardware utilization:

• Each struct Particle is 64 bytes.
• The update loop accesses only x, y, z (12 bytes) and vx, vy, vz (12 bytes)—a total of 24 bytes.
• The remaining 40 bytes (mass, id, tag) are completely untouched.

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: Align structs to 64-byte cache line boundaries using alignas and posix_memalign.
• Mastery of core invariant: Eliminate multi-threaded false sharing and MESI bus invalidations using explicit padding.
• Mastery of core invariant: Transform Array of Structures (AoS) to Structure of Arrays (SoA) to maximize cache line utilization.
• 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 -O0 debug build.
• Ignoring return codes, partial reads/writes, alignment padding, or cleanup paths when an allocation or syscall fails midway through a function.