Course Schedule II
A medium Graph problem included in Love Babbar 450, Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Graph
- Sheets
- 2
- Core for
- 11 roles
- Platform
- LeetCode
The problem
There are a total of numCourses courses labeled from 0 to numCourses-1. Given a list of prerequisite pairs, return the ordering of courses you should take to finish all courses. If impossible, return an empty array.
Example 1
- Input
- numCourses = 2, prerequisites = [[1,0]]
- Output
- [0,1]
- Why
- Course 0 has no prerequisites, so take it first, then course 1.
Example 2
- Input
- numCourses = 4, prerequisites = [[1,0],[2,0],[3,1],[3,2]]
- Output
- [0,1,2,3]
- Why
- Take course 0 first, then 1 and 2 in either order, then course 3.
Constraints
- 1 <= numCourses <= 2000
- 0 <= prerequisites.length <= 5000
How to think about it
Updated 2026-09-09Topological sort linearizes dependencies: courses with no remaining requirements can be taken immediately. Recording each course as its prerequisites reach zero yields a valid progression, and if the resulting schedule falls short of numCourses, a deadlock prevented completion.
Approaches, worst first
DFS post-order with reverse output
time O(V + E) · space O(V + E)
Run cycle-detecting DFS across all nodes using visited status arrays. When all dependents of a course are resolved, push it to an ordering list and reverse the list at the end. Aborts with an empty array if any cycle is detected.
Kahn BFS peeling zero-indegreesWrite this one
time O(V + E) · space O(V + E)
Compute in-degrees for all vertices and push all nodes with in-degree 0 into a queue. Pop courses one by one directly into the output array, reducing in-degrees of neighbors. If the output array size matches numCourses return it, otherwise return empty.
Where people lose marks · 3
- Returning the partial array instead of an empty array `[]` when a cycle prevents all courses from being scheduled.
- Prerequisites array can be empty (length 0), where every course is independent and valid answers include any permutation such as `[0, 1, ..., numCourses - 1]`.
- Forgetting that multiple valid topological orderings exist; asserting equality against a single rigid test output instead of verifying prerequisite constraints breaks local tests.
The theory behind it
Graph — the ground this problem stands on. All Graph problems
What Graph is
A graph is a network of individual points, called vertices or nodes, connected by lines called edges. Think of a subway transit map, an electrical circuit, or a web of social friends. Unlike a tree, a graph has no designated top node and no parent-child hierarchy. Connections can run one-way or both ways, and paths can loop back on themselves to form closed cycles.
When to reach for it
Reach for graph algorithms when inputs describe relationships, networks, flights between cities, course prerequisites, or clone networks. Signals include finding the shortest route across unweighted connections, ordering tasks that depend on earlier tasks, counting isolated clusters, or checking whether a path contains an infinite loop. Whenever problems present pairs of related entities and ask for reachability, distances, or dependencies, graph representations apply.
How the pattern works
First convert edge lists into an adjacency list, mapping each node to an array of its neighbors. Choose your exploration strategy based on the goal: use a queue and breadth-first search to find the shortest path in unweighted networks, or use recursion and depth-first search to explore full paths and detect cycles. Because graphs can have loops, always track visited nodes in a set or boolean array. Add nodes to the visited set at the moment they enter the queue so they are never visited twice.
What each operation costs
| Operation | Time |
|---|---|
| visit all nodes and edges via search | O(v + e) |
| topological sort using in-degree counts | O(v + e) |
| shortest path using dijkstra with a min-heap | O((v + e) log v) |
What usually goes wrong with Graph
- Adding a node to the visited set when popping from the queue instead of when pushing, which lets neighboring nodes enqueue duplicate entries and wastes memory.
- Failing to check for cycles in directed graphs when finding prerequisite orders, causing topological sort routines to hang or return incomplete lists.
- Assuming an input graph is fully connected and scanning from only a single starting node, missing disconnected islands and isolated components.
Which roles need this problem
Graph is a core topic for these 11 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 6 more roles, including Performance Engineer, Search Engineer, Information Retrieval 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 Graph problems
Problem set and role mapping as of .