# Occurrence Typing True Branch: Explained
Occurrence Typing True Branch shows up often in coding rounds. Here is how I talk through it when the interviewer is watching.
## Key idea
Refine a variable's type based on the tests that succeeded, so inside `if (x != null)` the type of x no longer includes null.
## 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
A flow-sensitive extension of simple types; each test produces a refined environment for the true and false branches.
## Common mistake
Refining only the tested variable and not a path like x.f, which leaves field-sensitive tests useless.
## 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 here.