Balanced Binary Tree
An easy Binary Trees problem included in Apna College, Love Babbar 450, Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Binary Trees
- Sheets
- 3
- Core for
- 4 roles
- Platform
- LeetCode
The problem
Given the root of a binary tree, determine if it is height-balanced. A height-balanced binary tree is defined as a binary tree in which the left and right subtrees of every node differ in height by no more than 1.
Example 1
- Input
- [3,9,20,null,null,15,7]
- Output
- true
- Why
- The left subtree has depth 1, the right subtree has depth 2. Difference is 1, so it is balanced.
Example 2
- Input
- [1,2,2,3,3,null,null,4,4]
- Output
- false
- Why
- The left subtree has depth 3 while the right subtree has depth 1, exceeding the allowed difference of 1.
Example 3
- Input
- []
- Output
- true
- Why
- An empty tree is trivially balanced.
Constraints
- The number of nodes is in the range [0, 5000].
- -104 <= Node.val <= 104
How to think about it
Updated 2026-09-09Checking balance top-down forces repeated depth scans on every subtree. Instead, piggyback the balance check onto height calculation bottom-up: if any subtree is unbalanced, propagate a sentinel value (-1) straight to the root to short-circuit all remaining work.
Approaches, worst first
Top-down recursive depth check
time O(n^2) · space O(h)
At each node, call `depth(node.left)` and `depth(node.right)`, check that `abs(left - right) <= 1`, and recurse on children. Recomputes depths of lower nodes repeatedly, degrading performance on skewed trees.
Bottom-up DFS with sentinelWrite this one
time O(n) · space O(h)
Compute height recursively. If a child returns -1 or subtree heights differ by more than 1, return -1 immediately. Otherwise return `1 + max(left, right)`. The tree is balanced if and only if the root call does not evaluate to -1.
Where people lose marks · 3
- A tree where every individual node's left and right depths differ by at most 1 is balanced, but only checking height at the root fails when deeper subtrees are lopsided.
- Confusing 0 depth with the -1 failure sentinel; an empty subtree has height 0, which is perfectly valid and balanced.
- Failing to propagate -1 immediately upon detecting an imbalance wastes time computing heights for sibling subtrees.
The theory behind it
Binary Trees — the ground this problem stands on. All Binary Trees problems
What Binary Trees is
A binary tree is a branching data structure that starts at a single top node called the root, like an upside-down family tree. Every node holds a piece of data and can branch out to at most two children below it, known as the left child and the right child. Because there is no ordering rule about which values go left or right, finding a specific item can require checking every single node in the entire tree.
When to reach for it
Reach for binary trees when problems present hierarchical data with left and right child pointers. Questions asking for tree height, maximum depth, path sums from root to leaf, diameter, lowest common ancestor, or checking whether two trees are mirror reflections of each other all signal binary tree traversals. Any problem asking to inspect or reconstruct a tree layer by layer or path by path belongs here.
How the pattern works
Think recursively by focusing on what a single node must do. If the current node is null, return the base answer immediately. Otherwise, ask the left child for its result, ask the right child for its result, and combine both answers with the current node value before returning up to the parent. For horizontal scans, use a queue to read nodes layer by layer, measuring the queue length at the start of each layer to group nodes by depth.
What each operation costs
| Operation | Time |
|---|---|
| traverse all nodes using recursion or queue | O(n) |
| search for an arbitrary value in an unordered tree | O(n) |
| call stack memory on balanced tree | O(log n) |
| call stack memory on skewed tree | O(n) |
What usually goes wrong with Binary Trees
- Dereferencing left or right child pointers without checking if the current node is null, throwing null pointer errors on empty trees or leaf nodes.
- Defining a leaf node incorrectly by stopping when either child is null instead of checking that both left and right children are simultaneously null.
- Computing tree diameter by taking left height plus right height inside a recursive helper without updating a global maximum across every visited node.
Which roles need this problem
Binary Trees is a core topic for these 4 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 5 more roles, including Full-Stack Developer, Android Developer, iOS Developer.
Track this in your role's order
Pick your target role and all 370 problems — including this one — resequence to what that interview actually asks. Free.
Start freeMore Binary Trees problems
- Diameter of Binary TreeEasy
- Binary Tree Maximum Path SumHard
- Construct Binary Tree from Preorder and InorderMedium
- Construct Binary Tree from Inorder and PostorderMedium
- Serialize and Deserialize Binary TreeHard
- Lowest Common Ancestor of Binary TreeMedium
- Vertical Order Traversal of Binary TreeHard
- Top View of Binary TreeMedium
Problem set and role mapping as of .