Minimum Path Sum
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
Given an m x n grid filled with non-negative numbers, find a path from the top-left to the bottom-right that minimizes the sum of all numbers along its path. You can only move down or right.
Example 1
- Input
- grid = [[1,3,1],[1,5,1],[4,2,1]]
- Output
- 7
- Why
- Path 1→3→1→1→1 gives the minimum sum of 7.
Example 2
- Input
- grid = [[1,2,3],[4,5,6]]
- Output
- 12
- Why
- Path 1→2→3→6 gives sum 12.
Example 3
- Input
- grid = [[1]]
- Output
- 1
- Why
- Single cell grid, the path sum is just that cell.
Constraints
- m == grid.length
- n == grid[i].length
- 1 <= m, n <= 200
- 0 <= grid[i][j] <= 100
How to think about it
Updated 2026-09-09Every cell (r, c) can only be entered from the cell directly above or the cell directly to the left. The cheapest cost to enter (r, c) is grid[r][c] plus the minimum of those two predecessors. No backtracking is needed because path steps are strictly monotonic.
Approaches, worst first
Recursive path search
time O(2^(m+n)) · space O(m + n)
From (0, 0), branch right and down, accumulating cell values to find the minimum leaf. Exponentially explores overlapping paths.
2D dynamic programming grid
time O(m * n) · space O(m * n)
Create an m x n matrix dp where dp[i][j] = grid[i][j] + min(dp[i-1][j], dp[i][j-1]). Initialize top-left cell and fill borders as running prefix sums.
1D rolling rowWrite this one
time O(m * n) · space O(n)
Use a single row array of size n. Initialize with row 0's prefix sums. For subsequent rows, update dp[0] += grid[i][0] and dp[j] = grid[i][j] + min(dp[j], dp[j-1]).
Where people lose marks · 3
- Uninitialized border transitions: cell (0, j) can only come from (0, j-1) and cell (i, 0) can only come from (i-1, 0). Blindly taking min with uninitialized cells injects false zeroes.
- Single cell grid (1x1): ensure loop boundaries do not skip the initial grid[0][0] value.
- Overwriting the input grid directly when pure functional immutability is required by the caller.
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 .