N Meetings in One Room
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
- GeeksforGeeks
The problem
Given n meetings with their start and end times, find the minimum number of rooms required to accommodate all meetings without overlap.
Example 1
- Input
- meetings = [[0,30],[5,10],[15,20]]
- Output
- 2
- Why
- Meetings [0,30] and [5,10] overlap, and [0,30] and [15,20] overlap. At most 2 meetings happen simultaneously.
Example 2
- Input
- meetings = [[7,10],[2,4]]
- Output
- 1
- Why
- No meetings overlap, so only one room is needed.
Constraints
- 1 <= meetings.length <= 10^5
- meetings[i].length == 2
- 0 <= start < end <= 10^9
How to think about it
Updated 2026-09-09Every meeting must be assigned a room, and a room only becomes available once its earlier meeting finishes. Sorting meetings by start time allows assigning each to the room whose meeting concludes earliest, allocating a new room only when even that room is still occupied.
Approaches, worst first
Chronological event sweep
time O(n log n) · space O(n)
Split intervals into start (+1) and end (-1) events. Sort all events chronologically, breaking ties by placing end events before start events, and track the peak active rooms.
Min-heap of end timesWrite this one
time O(n log n) · space O(n)
Sort meetings by start time. Maintain a min-heap of end times for currently occupied rooms. If the earliest ending room in the heap finishes before or when the new meeting starts, reuse it by popping and pushing the new end time; otherwise allocate an additional room.
Where people lose marks · 2
- Tie-breaking: if meeting A ends at time T and meeting B starts at time T, they can share the same room (`start >= heap.top()`), not requiring a new room.
- Sorting meetings by end time instead of start time breaks the heap simulation because rooms would be evaluated out of chronological start order.
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.
Companies that have asked it
Tags taken from the problem's own GeeksforGeeks page — not a copied list.
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 .