House Robber II
A medium Dynamic Programming problem included in Love Babbar 450, Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Dynamic Programming
- Sheets
- 2
- Core for
- 9 roles
- Platform
- LeetCode
The problem
You are a professional robber planning to rob houses along a circular street. Each house has a non-negative amount of money. The first and last houses are adjacent, so you cannot rob both. Find the maximum amount you can steal without alerting the police.
Example 1
- Input
- nums = [2,3,2]
- Output
- 3
- Why
- You cannot rob house 1 and house 3 together since they are adjacent. Rob house 2 for a total of 3.
Example 2
- Input
- nums = [1,2,3,1]
- Output
- 4
- Why
- Rob house 1 (1) and house 3 (3) for a total of 4, skipping the circular constraint.
Example 3
- Input
- nums = [1,2,3]
- Output
- 3
- Why
- Either rob house 2 (2) or house 3 (3). Best is 3.
Constraints
- 1 <= nums.length <= 100
- 0 <= nums[i] <= 1000
How to think about it
Updated 2026-09-09The circular connection only creates a conflict between the very first and very last house. You can never rob both in the same run. This splits the circular problem cleanly into two linear sub-problems: solve once excluding the last house, and once excluding the first house, then take the maximum.
Approaches, worst first
Recursive search with circular tracking
time O(2^n) · space O(n)
Branch recursively through the houses while passing a flag that records whether the first house was robbed to prevent robbing the last house. Recomputes overlapping states.
Two linear runsWrite this one
time O(n) · space O(1)
Reuse the linear House Robber routine twice: first on slice nums[0..n-2], and second on slice nums[1..n-1]. Each run runs in linear time using constant space, and the answer is the larger of the two results.
Where people lose marks · 3
- A single-element array has no distinct start and end. Slicing nums[0..n-2] produces an empty slice if n == 1. The edge case n == 1 must immediately return nums[0].
- Assuming that omitting the first house implies the last house MUST be robbed. The second linear pass allows the last house to be considered; it does not force it.
- Creating deep subarray copies when slicing. Passing index ranges to a helper function avoids allocating extra memory.
The theory behind it
Dynamic Programming — the ground this problem stands on. All Dynamic Programming problems
What Dynamic Programming is
Dynamic programming is a method for solving a complex problem by breaking it into overlapping subproblems, solving each subproblem only once, and remembering the answers in a lookup table. Instead of recalculating identical questions over and over, future steps look up previous answers directly. By assembling these saved pieces from the bottom up or storing them during recursion, a task that would take billions of steps finishes in a fraction of a second.
When to reach for it
Reach for dynamic programming when questions ask for the maximum profit, minimum cost, total number of distinct ways to achieve a goal, or whether a target can be formed. Signals include overlapping choices where making a choice now affects what choices remain later, but greedy picking fails to find the true global optimum. If drawing a recursive decision tree reveals the same subproblem states repeating across branches, dynamic programming is needed.
How the pattern works
Identify the state variables that uniquely describe a subproblem, such as an array index and remaining capacity. Write the base cases first, representing states whose answers are known without calculation. Next, write the recurrence relation that expresses the current state using previously solved states, taking the minimum, maximum, or sum among your options. Build the solution either top-down by caching recursive returns in a memo table, or bottom-up by filling an array in topological dependency order. When each state depends only on the previous row, compress storage down to a single array.
What each operation costs
| Operation | Time |
|---|---|
| fill dynamic programming table of n states | O(n) |
| solve two-dimensional grid of m by n states | O(m * n) |
| space-optimized state transition keeping one row | O(n) |
What usually goes wrong with Dynamic Programming
- Filling a bottom-up table in an order where the current cell needs values that have not been computed yet, reading uninitialized zeros.
- Failing to initialize base cases properly, such as filling a minimization table with zeros instead of infinity, which traps the answer at zero.
- Overwriting values in a 1D space-optimized knapsack array by scanning in the wrong direction, allowing the same item to be chosen multiple times.
Which roles need this problem
Dynamic Programming is a core topic for these 9 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 5 more roles, including Game Developer, Cryptography Engineer, Performance Engineer.
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 Dynamic Programming problems
Problem set and role mapping as of .