# Rotting Oranges: Explained

Rotting Oranges shows up often in coding rounds. Here is how I talk through it when the interviewer is watching.

## Key idea

Multi-source BFS from every rotten orange; minutes = max depth, and any leftover fresh orange means -1.

## Steps to say out loud

1. Restate the input and the exact ask, and nail down constraints and overflow.
2. Name the pattern (graph BFS/DFS, union-find, topological sort, or tree DP) and why a simpler scan fails.
3. Code it, then trace a short example plus one empty or already-solved edge case.

## Complexity

O(mn).

## Common mistake

Counting the number of BFS layers incorrectly when the queue still holds the previous minute.

## Practice tip

Time yourself: two minutes to explain, ten to code, three to test edges. Disclosure: I work on Linkjob AI. I also keep a practice cheat sheet at Linkjob.ai.