A strong answer
A strong candidate frames What happens between typing gcc hello.c -o hello and seeing your program run? around the exact memory layout, compiler semantics, and hardware execution model covered in Installing a Compiler and Your First C Program. Explain the four stages of the C compilation pipeline — preprocessing, compilation, assembly, and linking — and what artifact each produces.
This is the first surprise for anyone learning C: a C source file is just text. It does not run by itself. Unlike some languages where you can press a "run" button inside an editor, C source code must first be translated by a compiler into machine code — instructions your CPU understands — and saved as an executable file. Only then can you run it.
The most common beginner question is: which program does the translating, and which command do I type? This lesson answers that, step by step, assuming you have never compiled anything before.
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: Install a C compiler (GCC or Clang) and verify it works from the terminal.
- Mastery of core invariant: Write a minimal C program with a main function and a printf statement.
- Mastery of core invariant: Compile a C source file with gcc or clang and run the resulting executable.
- 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.