What does each stage of a C++ build produce?

A strong answer

A strong candidate frames What does each stage of a C++ build produce? around the exact memory layout, compiler semantics, and hardware execution model covered in From Source Text to a Running Program. Trace preprocessing, compiling, and linking, and map each common build error to the stage that reports it.

A processor cannot run that file. It understands only machine code: numeric instructions for one family of chips, such as x86-64 or ARM64. None of those instructions says "print", and none of them knows what std::cout is. Somewhere between your keystrokes and the letters on screen, the text has to become instructions, and the code that actually writes to the screen, which you never wrote, has to join your program.

Python solves this by shipping an interpreter that reads your text while the program runs. C++ takes the other road: translate everything ahead of time into a file the machine can run directly. That is a large part of why C++ programs start quickly and run fast. The price is that the translation is yours to understand, because most early errors and surprises come from it.

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: Describe what the preprocessor, compiler and linker each take in and produce.
• Mastery of core invariant: Explain why a declaration lets the compiler accept a call to code it has not seen.
• Mastery of core invariant: Classify an error message as a preprocessor, compiler or linker error.
• 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.