Evaluate Reverse Polish Notation
A medium Stack problem included in Love Babbar 450, Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Stack
- Sheets
- 2
- Core for
- 8 roles
- Platform
- LeetCode
The problem
Evaluate an arithmetic expression given as a list of tokens in Reverse Polish Notation. The valid operators are plus, minus, multiply, and divide. Each operand may be an integer or another expression.
Example 1
- Input
- tokens = ["2","1","+","3","*"]
- Output
- 9
- Why
- ((2 + 1) * 3) = 9. The plus operator applies to 2 and 1, yielding 3, then multiply by 3.
Example 2
- Input
- tokens = ["4","13","5","/","+"]
- Output
- 6
- Why
- 4 + (13 / 5) = 4 + 2 = 6. Integer division truncates toward zero, so 13 / 5 = 2.
Constraints
- 1 <= tokens.length <= 10^4
- Each token is either an operator (+, -, *, /) or an integer in the range [-200, 200]
- The expression is guaranteed to be valid and evaluates to an integer
How to think about it
Updated 2026-09-09Postfix notation removes the ambiguity of precedence by placing every operator strictly after its two operands. Reading left to right, every operator consumes the most recent two numbers that have not yet been consumed. That last-in, first-out relationship means a stack naturally holds dormant operands until their operator arrives.
Approaches, worst first
In-place array compaction
time O(n^2) · space O(1)
Find the first operator, apply it to the preceding two indices, replace the triplet with the calculated result, and shift the remaining elements left. Loses because shifting the array on every operator produces quadratic work.
Operand stackWrite this one
time O(n) · space O(n)
Iterate through the tokens. Push numeric tokens directly onto a stack. When encountering an operator, pop the right operand first, then the left operand, evaluate the operation, and push the result back. At the end, the stack contains exactly one final value.
Where people lose marks · 3
- Operand order matters for subtraction and division. The first element popped from the stack is the right operand, and the second is the left operand; reversing them flips the sign or quotient.
- Language-level integer division differences: in JavaScript or Python, default floor division rounds negative numbers away from zero (-3 // 2 = -2), whereas the problem requires truncation toward zero (`Math.trunc`).
- Tokens with negative integers like `-4` start with a minus sign. Checking `token.startsWith('-')` can misidentify negative numbers as subtraction operators unless string length is verified.
The theory behind it
Stack — the ground this problem stands on. All Stack problems
What Stack is
A stack is a vertical pile of cafeteria trays where items enter and depart from one single opening at the top. The most recent item set down is the first one retrieved, while items deposited earlier remain buried underneath until newer arrivals are lifted away. This strict last-in, first-out sequence guarantees that older context stays preserved until all newer nested actions run to completion.
When to reach for it
Reach for a stack whenever an algorithm encounters nested structures like matched brackets, tags, or algebraic formulas. Problems demanding undo operations, function execution histories, or evaluating postfix arithmetic require this discipline. It is also the primary structure for monotonic queries where a task asks for the nearest greater or smaller value adjacent to each position in a series.
How the pattern works
Picture peeling layers back in exact reverse order of their arrival. Push items as pending jobs or unclosed delimiters encounter the scan. When closing boundaries appear, pop the topmost entry and check for compatibility. For monotonic patterns, maintain an invariant where elements on the stack remain strictly increasing or decreasing; pop any items that violate this rule before recording candidate answers and pushing the current item.
What each operation costs
| Operation | Time |
|---|---|
| push item onto the top | O(1) |
| pop item from the top | O(1) |
| inspect the topmost element | O(1) |
What usually goes wrong with Stack
- Popping from or peeking into an empty stack without first verifying that the size is positive, causing runtime null pointer or empty collection errors.
- Forgetting to verify that the stack is completely empty at the end of bracket matching, which mistakenly accepts strings with dangling unclosed opening symbols.
- Storing values instead of indices in monotonic stacks, making it impossible to calculate distance intervals between matching elements afterwards.
Which roles need this problem
Stack is a core topic for these 8 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 9 more roles, including Frontend Engineer, Data Engineer, Game 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 Stack problems
Problem set and role mapping as of .