TRT
Sign in
easyFoundationsconcept

Why does order matter in an if/else if/else chain?

Explain that only the first true condition executes, so higher-priority conditions must come first.

TRT practice prompt — not a verified question from a named employer.

The Runtime Theory Team2 min read
Learn it firstMaking Decisions: if, else if, and elseLearn how to branch program flow with if, else if, and else, use comparison and logical operators, and trace conditional execution step by step.

A strong answer

A strong candidate frames Why does order matter in an if/else if/else chain? around the exact memory layout, compiler semantics, and hardware execution model covered in Making Decisions: if, else if, and else. Explain that only the first true condition executes, so higher-priority conditions must come first.

Every program you have written so far executes in a straight line from top to bottom: line 1 runs, then line 2, then line 3, until main returns 0. That works for a simple calculator formula, but real programs must react differently depending on the data they receive.

Without a way to choose between paths, your program would print all four grades every time it ran. Choosing which statements to execute and which to skip based on a runtime value is called branching or conditional control flow, and the fundamental tool for it in C is the if statement.

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: Write if, else if, and else statements to branch program flow.
  • Mastery of core invariant: Use comparison operators (==, !=, <, >, <=, >=) in conditions.
  • Mastery of core invariant: Combine conditions with logical operators (&&, ||, !).
  • 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.

This answer walks

Practice follow-ups

  1. 01What happens if you use separate if statements instead of else if?
  2. 02Can you nest if statements inside other if statements?

More interviews in this topic

easy · languageWalk through the internal structure of a Go channel (`hchan`), explain the exact table of channel state behaviors (nil vs open vs closed for send, receive.easy · languageHow does Go's compiler decide whether a variable is allocated on the stack or the heap (Escape Analysis), why is returning a value `User` often faster than.easy · languageExplain how Go's Concurrent Tri-Color Mark-and-Sweep GC works—why doesn't Go use a compacting/generational GC like the JVM, how does the Hybrid Write Barrier.

Not started

Sign in to save your learning progress.

Sign in to save