Minimum Number of Arrows to Burst Balloons
A medium Greedy problem included in Love Babbar 450, Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Greedy
- Sheets
- 2
- Core for
- 3 roles
- Platform
- LeetCode
The problem
There is a 2D grid of balloons. An arrow shot at coordinate x pops all balloons that have a horizontal diameter spanning x. Find the minimum number of arrows needed to pop all balloons.
Example 1
- Input
- points = [[10,16],[2,8],[1,6],[7,12]]
- Output
- 2
- Why
- Shoot at x=6 (pops [1,6] and [2,8]) and x=11 (pops [7,12] and [10,16]).
Example 2
- Input
- points = [[1,2],[3,4],[5,6],[7,8]]
- Output
- 4
- Why
- Each balloon needs its own arrow since they don't overlap.
Constraints
- 1 <= points.length <= 10^5
- points[i].length == 2
- -2^31 <= xstart < xend <= 2^31 - 1
How to think about it
Updated 2026-09-09The balloon that ends first forces your hand: you must pierce it before or at its right edge. Shooting at its exact right edge gives the arrow the greatest possible reach into balloons that start later.
Approaches, worst first
Sort by start coordinate
time O(n log n) · space O(1)
Sort by xstart and maintain the current intersection window [currStart, currEnd]. When a balloon starts past currEnd, fire an arrow and reset the window. Correct, but requires maintaining both endpoints of the intersection.
Sort by end coordinateWrite this one
time O(n log n) · space O(1)
Sort balloons by xend. Shoot the first arrow at the first balloon's end coordinate. Skip all subsequent balloons whose start coordinate is within reach of this arrow. When a balloon starts after the current arrow, shoot a new arrow at its end coordinate.
Where people lose marks · 2
- Integer subtraction `a[1] - b[1]` inside comparator functions will overflow and flip signs because coordinates can span -2^31 to 2^31 - 1; use explicit `<` and `>` comparisons.
- Treating touching points as disjoint: a balloon [1, 2] and [2, 3] both get popped by an arrow at 2, so the condition to skip is `start <= arrowPos`, not `start < arrowPos`.
The theory behind it
Greedy — the ground this problem stands on. All Greedy problems
What Greedy is
A greedy algorithm makes the best-looking choice available right now, at every step, without ever looking back or second-guessing its decision. Think of a cashier making change by handing over the largest possible coin first, repeatedly, until the total is reached. Unlike dynamic programming, which saves and compares answers to multiple overlapping paths, a greedy strategy commits to one immediate option and keeps moving forward.
When to reach for it
Reach for greedy when problems ask for minimum jumps, interval scheduling, assigning resources to maximize satisfaction, or finding fractional values. Key signals include sorted orders where greedily taking the next item never hurts future options, or gas station round trips where running balances prove reachability. If you can prove that taking the immediate best choice never leaves you worse off than any alternative, greedy gives the fastest answer.
How the pattern works
Start by sorting the input to bring the most promising candidates to the front. At each position, evaluate your local rule, take the best available piece, and update your running state. The crucial mental step is proving the greedy choice property: demonstrate that picking this immediate winner cannot block a better global solution down the road. If choosing an item now forces you to reconsider past decisions when conditions change later, greedy fails and you must switch to dynamic programming instead.
What each operation costs
| Operation | Time |
|---|---|
| sort elements to enable greedy selection | O(n log n) |
| greedy single-pass scan through sorted input | O(n) |
| greedy choice using a priority queue | O(n log n) |
What usually goes wrong with Greedy
- Applying a greedy choice without proving it yields the global optimum, such as picking the largest coin first for arbitrary denominations where dynamic programming was required.
- Forgetting to sort the input before running the greedy loop, making local decisions on unordered elements that produce invalid answers.
- Picking items based on only one attribute when the optimal decision depends on a ratio or combination of multiple attributes.
Which roles need this problem
Greedy is a core topic for these 3 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 4 more roles, including Site Reliability Engineer, Search Engineer, Quant 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 Greedy problems
Problem set and role mapping as of .