Last Stone Weight
An easy Heap problem included in Love Babbar 450. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Heap
- Sheets
- 1
- Core for
- 9 roles
- Platform
- LeetCode
The problem
We have a collection of stones, each with a positive integer weight. In each turn, pick up the two heaviest stones and smash them together. If they have equal weight, both are destroyed; if they differ, the lighter stone is destroyed and the heavier stone gets reduced by the lighter stone's weight. Repeat until at most one stone remains. Return the weight of the last remaining stone, or 0 if none remain.
Example 1
- Input
- stones = [2,7,4,1,8,1]
- Output
- 1
- Why
- Smash 8 and 7 to get 1, remaining [2,4,1,1,1]. Smash 4 and 2 to get 2, remaining [1,1,1,2]. Sort descending: [2,1,1,1]. Smash 2 and 1 to get 1, remaining [1,1]. Smash 1 and 1 to get 0, remaining [1]. Last stone weight is 1.
Example 2
- Input
- stones = [1]
- Output
- 1
- Why
- Only one stone exists, so its weight is returned directly.
Example 3
- Input
- stones = [10,10]
- Output
- 0
- Why
- Both stones are equal weight, so both are destroyed, leaving nothing.
Constraints
- 1 <= stones.length <= 30
- 1 <= stones[i] <= 1000
How to think about it
Updated 2026-09-09Smashing two stones reduces the total count by either one or two every single round. You always need the absolute two heaviest available, and when they collide, the remainder re-enters the pool at an unpredictable rank. That dynamic top-two lookup is the textbook signature of a priority queue.
Approaches, worst first
Repeated full sort
time O(n^2 log n) · space O(n)
Sort the array descending, pop the two largest, push their positive difference back, and sort the entire array again. Simple to write, but wastes work repeatedly ordering undisturbed elements.
Max-heap simulationWrite this one
time O(n log n) · space O(n)
Heapify all stones into a max-heap. Pop two elements; if unequal, push the difference back. Each clash costs logarithmic time and shrinks the collection, leaving at most one element when the loop exits.
Where people lose marks · 3
- Returning an unhandled empty state. When the final two stones have equal weights, both vanish and the heap is completely empty, which must evaluate to 0 instead of popping undefined.
- Pushing a difference of zero back into the heap. Equal stones destroy each other entirely; inserting 0 pollutes the heap and inflates loop iterations.
- Assuming at least two stones exist initially. If stones has length 1, no smash ever occurs and that single stone must be returned immediately.
The theory behind it
Heap — the ground this problem stands on. All Heap problems
What Heap is
A heap is a specialized tree that keeps only the single most extreme item at the very top. In a min-heap, every parent node is smaller than its children, so the smallest element in the entire collection sits immediately at the root. Unlike a binary search tree, a heap does not keep all items in full sorted order. It maintains only a partial order, making it fast at giving you the single smallest or largest item without spending time sorting everything else.
When to reach for it
Reach for a heap when a problem asks for the top k largest elements, the kth smallest value, or a running median from a stream of numbers. Signals include phrases like continuously finding the cheapest item, merging k sorted linked lists, or scheduling tasks with priorities. Whenever you need repeated access to the minimum or maximum value while items are added and removed dynamically, a priority heap is the tool.
How the pattern works
To find the k largest elements, keep a min-heap of fixed size k. Push incoming numbers into the heap; whenever the heap size grows past k, pop the top item, which is the smallest among them. After processing all elements, only the k largest remain. For a running median, balance two heaps: a max-heap holding the smaller half of numbers and a min-heap holding the larger half. In code, heaps are stored compactly as flat arrays where a node at index i has children at indices 2i plus 1 and 2i plus 2.
What each operation costs
| Operation | Time |
|---|---|
| read the minimum or maximum element | O(1) |
| insert a new element and sift into position | O(log n) |
| remove the top element and sift down | O(log n) |
| build a heap from an array of n items | O(n) |
What usually goes wrong with Heap
- Using a max-heap instead of a min-heap when keeping the k largest elements, causing the largest values to be evicted while small items stay behind.
- Assuming that extracting elements by iterating over the backing array yields sorted order, without popping items from the heap one by one.
- Forgetting that standard language libraries provide a min-heap by default, leading to wrong answers when a max-heap was required.
Which roles need this problem
Heap 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 11 more roles, including SDE / Backend Engineer, Data Engineer, ML 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 Heap problems
Problem set and role mapping as of .