Assign Cookies
An easy Greedy problem included in Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Greedy
- Sheets
- 1
- Core for
- 3 roles
- Platform
- LeetCode
The problem
You are given an array of cookies where each element represents the size of a cookie, and a greed factor array where each element represents the minimum cookie size a child is content with. Assign one cookie to each child to satisfy as many children as possible. Return the maximum number of content children.
Example 1
- Input
- g = [1,2,3], s = [1,1]
- Output
- 1
- Why
- Only one child (greed 1) can be satisfied with a cookie of size 1.
Example 2
- Input
- g = [1,2], s = [1,2,3]
- Output
- 2
- Why
- Both children can be satisfied with cookies of size 1 and 2.
Constraints
- 1 <= g.length, s.length <= 3 * 10^4
- 1 <= g[i], s[j] <= 2^31 - 1
How to think about it
Updated 2026-09-09Giving a huge cookie to an readily satisfied child wastes potential capacity that could have satisfied a greedier one. Pair the smallest adequate cookie with the least greedy child to conserve larger cookies for higher greed demands.
Approaches, worst first
Brute force search
time O(n * m) · space O(m)
For each child, scan the cookie array to find the smallest unused cookie that satisfies them, marking cookies as used. Repeated linear scans over unused items degrade performance.
Sort both arrays and two pointersWrite this one
time O(n log n + m log m) · space O(1)
Sort greed factors g and cookie sizes s ascending. Advance a cookie pointer on every step. Whenever the current cookie satisfies the current child, advance the child pointer. The final child pointer position represents the maximum satisfied children.
Where people lose marks · 2
- Advancing the child pointer when the cookie is too small; the child must remain waiting for a larger cookie while the cookie pointer advances.
- Assuming the number of cookies equals the number of children; either array can exhaust first, so the loop condition must check both bounds.
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 .