Find Peak Element
A medium Binary Search problem included in Love Babbar 450, Striver A2Z. Below: the roles whose interviews prioritise this topic, and how to practise it.
- Topic
- Binary Search
- Sheets
- 2
- Core for
- 7 roles
- Platform
- LeetCode
The problem
Given an integer array, find a peak element and return its index. A peak element is one that is strictly greater than its neighbors. If the array contains multiple peaks, return the index of any of them.
Example 1
- Input
- nums = [1,2,3,1]
- Output
- 2
- Why
- 3 is a peak element at index 2 since it is greater than both neighbors 2 and 1.
Example 2
- Input
- nums = [1,2,1,3,5,6,4]
- Output
- 5
- Why
- 6 at index 5 is a peak element since it is greater than its neighbors 5 and 4.
Constraints
- 1 <= nums.length <= 10^5
- -2^31 <= nums[i] <= 2^31 - 1
- nums[i] != nums[i + 1] for all valid i
How to think about it
Updated 2026-09-09You do not need an entirely sorted collection to discard half the search area. Stepping in the direction of an upward slope is guaranteed to lead to a local peak eventually, because out-of-bounds values act as negative infinity and adjacent values are never equal.
Approaches, worst first
Linear neighbor scan
time O(n) · space O(1)
Iterate across the array and check if the current number exceeds both adjacent values. Simple and requires zero assumptions, but evaluates items sequentially instead of exploiting downhill guarantees.
Binary search on slopeWrite this one
time O(log n) · space O(1)
Compare mid against mid + 1. If mid is strictly less than mid + 1, a rising slope guarantees at least one peak in the right half, so set low = mid + 1. Otherwise, a peak must exist at mid or to its left, so high = mid.
Where people lose marks · 3
- Checking mid - 1 without checking for index zero causes array index out-of-bounds errors; comparing mid with mid + 1 keeps index lookups safe when low < high.
- Using high = mid - 1 when mid itself could be the actual peak skips the answer; shrink the upper bound to mid rather than mid - 1.
- Looping with low <= high while setting high = mid causes an infinite loop when low equals high.
The theory behind it
Binary Search — the ground this problem stands on. All Binary Search problems
What Binary Search is
Binary search is the guessing strategy used when searching a thick telephone directory or guessing a secret number between one and a hundred. Rather than inspecting names one by one from the first page, the search opens straight to the middle page. If the target precedes that middle entry, the entire back half is discarded; if it follows, the front half is eliminated. Repeating this halved split finds the item with remarkable speed.
When to reach for it
Reach for binary search when queries target sorted collections, rotated sorted arrays, or monotonic answer spaces. Strong hints include logarithmic time constraints like O(log n) or search ranges exceeding one billion where stepping one value at a time times out. It also applies when validating whether a guessed solution is possible via a monotonic boolean check, known as binary search on answer.
How the pattern works
Define the search territory with two inclusive pointers, low and high. Compute the midpoint using low plus half the difference to high, avoiding integer overflow. Formulate an exact boolean condition that divides the range into true and false halves. Decide whether the boundary condition includes the midpoint or shifts strictly past it. The loop invariant states that the sought target, if it exists, remains trapped inside the interval throughout every iteration.
What each operation costs
| Operation | Time |
|---|---|
| find target in sorted array | O(log n) |
| find boundary in monotonic range | O(log n) |
What usually goes wrong with Binary Search
- Triggering integer overflow by computing middle using low plus high divided by two instead of low plus half of high minus low in fixed-width numeric types.
- Creating an infinite loop when the interval shrinks to two elements by setting low equal to mid when mid was rounded down.
- Mismatched loop condition and bounds updates, such as pairing low less than or equal to high with non-advancing pointer assignments that never terminate.
Which roles need this problem
Binary Search is a core topic for these 7 roles — if you're targeting one of them, this problem is early in your path, not optional.
Secondary for 17 more roles, including Full-Stack Developer, Data Engineer, Android 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 Binary Search problems
Problem set and role mapping as of .