Off-by-one on range boundaries
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.
Move from brute-force thinking to an efficient approach using array strategy.
You are given an m x n integer matrix grid.
We define an hourglass as a part of the matrix with the following form:
Return the maximum sum of the elements of an hourglass.
Note that an hourglass cannot be rotated and must be entirely contained within the matrix.
Example 1:
Input: grid = [[6,2,1,3],[4,2,1,5],[9,2,8,7],[4,1,2,9]] Output: 30 Explanation: The cells shown above represent the hourglass with the maximum sum: 6 + 2 + 1 + 2 + 9 + 2 + 8 = 30.
Example 2:
Input: grid = [[1,2,3],[4,5,6],[7,8,9]] Output: 35 Explanation: There is only one hourglass in the matrix, with the sum: 1 + 2 + 3 + 5 + 7 + 8 + 9 = 35.
Constraints:
m == grid.lengthn == grid[i].length3 <= m, n <= 1500 <= grid[i][j] <= 106Problem summary: You are given an m x n integer matrix grid. We define an hourglass as a part of the matrix with the following form: Return the maximum sum of the elements of an hourglass. Note that an hourglass cannot be rotated and must be entirely contained within the matrix.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array
[[6,2,1,3],[4,2,1,5],[9,2,8,7],[4,1,2,9]]
[[1,2,3],[4,5,6],[7,8,9]]
matrix-block-sum)Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #2428: Maximum Sum of an Hourglass
class Solution {
public int maxSum(int[][] grid) {
int m = grid.length, n = grid[0].length;
int ans = 0;
for (int i = 1; i < m - 1; ++i) {
for (int j = 1; j < n - 1; ++j) {
int s = -grid[i][j - 1] - grid[i][j + 1];
for (int x = i - 1; x <= i + 1; ++x) {
for (int y = j - 1; y <= j + 1; ++y) {
s += grid[x][y];
}
}
ans = Math.max(ans, s);
}
}
return ans;
}
}
// Accepted solution for LeetCode #2428: Maximum Sum of an Hourglass
func maxSum(grid [][]int) (ans int) {
m, n := len(grid), len(grid[0])
for i := 1; i < m-1; i++ {
for j := 1; j < n-1; j++ {
s := -grid[i][j-1] - grid[i][j+1]
for x := i - 1; x <= i+1; x++ {
for y := j - 1; y <= j+1; y++ {
s += grid[x][y]
}
}
ans = max(ans, s)
}
}
return
}
# Accepted solution for LeetCode #2428: Maximum Sum of an Hourglass
class Solution:
def maxSum(self, grid: List[List[int]]) -> int:
m, n = len(grid), len(grid[0])
ans = 0
for i in range(1, m - 1):
for j in range(1, n - 1):
s = -grid[i][j - 1] - grid[i][j + 1]
s += sum(
grid[x][y] for x in range(i - 1, i + 2) for y in range(j - 1, j + 2)
)
ans = max(ans, s)
return ans
// Accepted solution for LeetCode #2428: Maximum Sum of an Hourglass
// Rust example auto-generated from java reference.
// Replace the signature and local types with the exact LeetCode harness for this problem.
impl Solution {
pub fn rust_example() {
// Port the logic from the reference block below.
}
}
// Reference (java):
// // Accepted solution for LeetCode #2428: Maximum Sum of an Hourglass
// class Solution {
// public int maxSum(int[][] grid) {
// int m = grid.length, n = grid[0].length;
// int ans = 0;
// for (int i = 1; i < m - 1; ++i) {
// for (int j = 1; j < n - 1; ++j) {
// int s = -grid[i][j - 1] - grid[i][j + 1];
// for (int x = i - 1; x <= i + 1; ++x) {
// for (int y = j - 1; y <= j + 1; ++y) {
// s += grid[x][y];
// }
// }
// ans = Math.max(ans, s);
// }
// }
// return ans;
// }
// }
// Accepted solution for LeetCode #2428: Maximum Sum of an Hourglass
function maxSum(grid: number[][]): number {
const m = grid.length;
const n = grid[0].length;
let ans = 0;
for (let i = 1; i < m - 1; ++i) {
for (let j = 1; j < n - 1; ++j) {
let s = -grid[i][j - 1] - grid[i][j + 1];
for (let x = i - 1; x <= i + 1; ++x) {
for (let y = j - 1; y <= j + 1; ++y) {
s += grid[x][y];
}
}
ans = Math.max(ans, s);
}
}
return ans;
}
Use this to step through a reusable interview workflow for this problem.
Two nested loops check every pair or subarray. The outer loop fixes a starting point, the inner loop extends or searches. For n elements this gives up to n²/2 operations. No extra space, but the quadratic time is prohibitive for large inputs.
Most array problems have an O(n²) brute force (nested loops) and an O(n) optimal (single pass with clever state tracking). The key is identifying what information to maintain as you scan: a running max, a prefix sum, a hash map of seen values, or two pointers.
Review these before coding to avoid predictable interview regressions.
Wrong move: Loop endpoints miss first/last candidate.
Usually fails on: Fails on minimal arrays and exact-boundary answers.
Fix: Re-derive loops from inclusive/exclusive ranges before coding.