# Purity Analysis Side Effects: Practice Notes

Purity Analysis Side Effects shows up often in coding rounds. Here is how I talk through it when the interviewer is watching.

## Key idea

Classify functions as pure, read-only or effectful so a compiler can CSE, hoist or parallelize their calls.

## Steps to say out loud

1. Restate the input and the exact ask, and nail down constraints and overflow.
2. Name the pattern (binary search on the answer, monotonic stack or deque, interval / interval-DP, string hashing, graph traversal, or shortest paths) and why a nested scan or naive search fails.
3. Code it, then trace a short example plus one empty or already-solved edge case.

## Complexity

Typically a bottom-up summary of stores, syscalls and writes through escaped pointers.

## Common mistake

Treating a function that mutates a freshly allocated object and returns it as impure, which is too conservative for constructor-style code.

## Practice tip

Time yourself: two minutes to explain, ten to code, three to test edges. Disclosure: I work on Linkjob AI. I also keep a practice cheat sheet at multilingual AI interview assistant.