Explain why mutable default arguments and `[[0]*N]*M` fail in Python, why `if not bucket:` is a subtle bug compared to `if bucket is None:`, and how.

A strong answer

A strong candidate frames Explain why mutable default arguments and [[0]*N]*M fail in Python, why if not bucket: is a subtle bug compared to if bucket is None:, and how. around the exact memory layout, compiler semantics, and hardware execution model covered in [Mutability, Shallow vs Deep Copies, and the Mutable Default Argument Trap]. Trace fn.__defaults__, distinguish falsy empty lists [] from None, and explain deepcopy's memo cycle-detection dictionary.

You deploy a FastAPI endpoint with a helper def add_tag(tag: str, tags: list[str] = []) -> list[str]: tags.append(tag); return tags. In unit tests with one call it passes, but in production User B sees all the tags that User A added 5 minutes ago! And in another route, copying a configuration template with cfg = BASE_CFG.copy() and modifying cfg['db']['port'] = 5433 silently corrupts BASE_CFG['db']['port'] for the entire server!

When engineers encounter this bottleneck in production, a surface-level API description rarely explains what went wrong. In real workloads, every line of code executes against concrete hardware constraints: fixed-width memory cells, CPU cache lines, kernel descriptor tables, network socket buffers, or accelerator memory buses. Without a clear mental model of mutability, shallow/deep copying, and function __defaults__ binding, debugging degrades into guesswork—tuning timeouts, adding retries, or scaling instances blindly while the underlying architectural flaw remains 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: Trace why default parameter expressions live in fn.__defaults__ and persist across function calls.
• Mastery of core invariant: Distinguish if bucket is None: from if not bucket: when handling optional mutable arguments.
• Mastery of core invariant: Predict which nested mutations leak across shallow copies (copy()) vs deep copies (deepcopy()).
• 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.