What is a zombie process and how do you prevent it?

A strong answer

A strong candidate frames What is a zombie process and how do you prevent it? around the exact memory layout, compiler semantics, and hardware execution model covered in Process Synchronization: wait, waitpid, and Zombie Reaping. Explain zombies as exited processes whose exit status has not been reaped by wait/waitpid, and how to reap them.

Spawning child processes with fork() creates concurrent execution threads. However, without process synchronization, parent and child execution flows diverge unpredictably:

Running this code demonstrates asynchronous interleaving:

1. The parent prints "Parent finished." and exits immediately.
2. The shell displays a new command prompt.
3. Two seconds later, the child wakes up and prints "Child completed work." directly into the terminal, disrupting interactive shell input.

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: Block execution or poll child process state transitions using wait and waitpid.
• Mastery of core invariant: Decode child exit statuses and terminating signals using POSIX status macros.
• Mastery of core invariant: Explain kernel process table retention, zombie states, and init/systemd reparenting.
• 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.