Recursion trips up more Python developers in technical interviews than almost any other concept. Not because recursion itself is complicated, but because most people try to hold the entire call stack in their head at once.

You do not need to hold it all in your head. You need a trace table.

A trace table is a grid where each row represents one step of execution. You track every variable, every function call, and every return value in sequence. When you are done, you have a complete picture of what the code actually does rather than what you think it does.

This article walks through exactly how to build one for a recursive Python function, step by step.

The Problem

Take this function:

def mystery(n):
    if n <= 1:
        return n
    return mystery(n - 1) + mystery(n - 2)

print(mystery(4))

What does it print?

If you immediately recognized this as Fibonacci, good. If you did not, do not worry. The trace table method works whether you recognize the pattern or not.

Step 1: Identify Your Columns

Before you write a single row, decide what to track. For any recursive function you need at minimum:

• The function call with its argument
• The condition being checked
• What gets returned

For mystery(n) your columns are: Call, n, Condition (n <= 1?), and Returns.

Step 2: Start at the Top Level Call

Write the first row for mystery(4).

The function does not return a number yet. It returns two more calls. Write both of those as new rows.

Step 3: Follow the Left Branch First

Always resolve the left side of a recursive expression before the right side. Python evaluates left to right.

Now we can backtrack and substitute the values we found:

• Now mystery(2) can resolve: 1 + 0 = 1
• Now mystery(3) needs mystery(1) which is already 1, so mystery(3) = 1 + 1 = 2
• Now mystery(4) needs mystery(2) which is 1, so mystery(4) = 2 + 1 = 3

The function prints 3.

Why This Works Better Than Visualizing

When you try to visualize recursion mentally you are running a simulation in working memory. Working memory holds roughly 4 to 7 items at once. A recursive call with depth 4 generates 9 function calls. You will lose track.

A trace table offloads that cognitive work onto paper. Your brain stops trying to remember and starts reasoning about relationships instead. That is a much more reliable process under interview pressure.

The Three Rules of Recursive Trace Tables

• Rule 1: Never skip the base case. Write it explicitly even when it feels obvious. Interviewers embed bugs in base cases specifically because candidates skip them.
• Rule 2: Resolve one branch completely before starting the other. Do not jump between left and right branches. Finish the left subtree, note the return value, then start the right.
• Rule 3: Write return values back into the parent row. When mystery(2) resolves to 1, go back to the mystery(3) row and fill in that 1. This prevents you from losing track of partial results.

Practice This Yourself

Reading about trace tables and doing them are two different skills. The only way to build the muscle is repetition.

If you want to practice dry-running Python code with immediate feedback and step-by-step explanations, I built a free tool specifically for this called PyCodeIt. It generates a unique AI-powered Python tracing problem every time you click, covers Easy through Hard difficulty, and shows you a complete trace explanation after you submit your answer.

No account needed to start. Try it out at pycodeit.com.

What to Practice Next

Once you are comfortable with simple recursion, move to these topics in order:

1. Recursive functions with mutable default arguments (a classic interview trap)
2. Nested list flattening with recursion
3. Tree traversal written as recursive Python functions
4. Memoized recursion where you must trace the cache state alongside the call stack

Each of these has a trace table pattern. Once you learn the pattern for one, you can apply it to any variation an interviewer throws at you.

Trace tables are not a crutch. They are the method that professional developers use when reasoning about code they did not write. Interviewers use dry-run questions precisely because they reveal whether you understand execution or have just memorized patterns.

Build the habit now and it becomes automatic under pressure.

Written by the developer behind PyCodeIt. A free Python coding challenge platform with AI-generated dry-run problems and interview prep.