Dijkstra's Algorithm
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
- GeeksforGeeks
The problem
Given a weighted directed graph represented as an adjacency matrix and a source vertex, find the shortest path distances from the source to all other vertices using Dijkstra's algorithm. All edge weights are non-negative.
Example 1
- Input
- vertices = 3, edges = [[0,1,4],[0,2,1],[2,1,2]], source = 0
- Output
- [0,3,1]
- Why
- Shortest to vertex 0 is 0, to vertex 1 is 0->2->1 = 3, to vertex 2 is 0->2 = 1.
Example 2
- Input
- vertices = 2, edges = [[0,1,5]], source = 0
- Output
- [0,5]
- Why
- Direct edge from 0 to 1 with weight 5.
Constraints
- 1 <= vertices <= 100
- 0 <= edges.length <= vertices * (vertices - 1)
- 0 <= edge weight <= 1000
How to think about it
Updated 2026-09-09When edge weights are strictly non-negative, extending any existing path can never decrease its cost. The unsettled vertex with the smallest tentative distance is therefore guaranteed to have reached its optimal shortest path already, allowing us to lock in its value permanently and relax its outgoing neighbors.
Approaches, worst first
Linear scan selection array
time O(V^2) · space O(V)
Maintain a distance array initialized to infinity and a visited boolean array. In each iteration, scan all unvisited vertices to find the one with minimal distance, mark it visited, and relax its outgoing edges.
Min-heap priority queueWrite this one
time O((V + E) log V) · space O(V + E)
Push `(0, source)` into a min-heap. Pop the minimum distance pair `(dist, u)`. If `dist > distTo[u]`, discard it as stale; otherwise iterate over all outgoing edges `(u, v, weight)` and push improved distances to the heap.
Where people lose marks · 3
- Failing to skip stale entries popped from the priority queue leads to redundant edge relaxations and degrades runtime.
- Dijkstra produces incorrect shortest paths when negative edge weights are present; it relies strictly on monotonicity of path length.
- Unreachable vertices will maintain infinity distance values; ensure the representation handles infinity without integer overflow during addition.
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.
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 Graph problems
Problem set and role mapping as of .