Why does printf output sometimes appear before a write() syscall?

A strong answer

A strong candidate frames Why does printf output sometimes appear before a write() syscall? around the exact memory layout, compiler semantics, and hardware execution model covered in Standard I/O Buffering vs System Calls. Explain user-space stdio buffering versus unbuffered write(), and when stdout switches from line-buffered to fully buffered.

A common source of confusion in systems programming is the unexpected interaction between standard C library I/O (<stdio.h>) and low-level POSIX system calls (<unistd.h>).

In an interactive terminal, "Compute Engine Initialized" prints once. But redirect stdout to a log file (./app > out.log), and inspecting out.log shows:

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: Differentiate unbuffered, line-buffered, and fully buffered streams in <stdio.h>.
• Mastery of core invariant: Diagnose duplicated output bugs caused by calling fork() with dirty user-space buffers.
• Mastery of core invariant: Configure stream buffering policies programmatically using setvbuf.
• 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.