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.
Build confidence with an intuition-first walkthrough focused on array fundamentals.
Given an integer array arr, return the mean of the remaining integers after removing the smallest 5% and the largest 5% of the elements.
Answers within 10-5 of the actual answer will be considered accepted.
Example 1:
Input: arr = [1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,3] Output: 2.00000 Explanation: After erasing the minimum and the maximum values of this array, all elements are equal to 2, so the mean is 2.
Example 2:
Input: arr = [6,2,7,5,1,2,0,3,10,2,5,0,5,5,0,8,7,6,8,0] Output: 4.00000
Example 3:
Input: arr = [6,0,7,0,7,5,7,8,3,4,0,7,8,1,6,8,1,1,2,4,8,1,9,5,4,3,8,5,10,8,6,6,1,0,6,10,8,2,3,4] Output: 4.77778
Constraints:
20 <= arr.length <= 1000arr.length is a multiple of 20.0 <= arr[i] <= 105Problem summary: Given an integer array arr, return the mean of the remaining integers after removing the smallest 5% and the largest 5% of the elements. Answers within 10-5 of the actual answer will be considered accepted.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array
[1,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,2,3]
[6,2,7,5,1,2,0,3,10,2,5,0,5,5,0,8,7,6,8,0]
[6,0,7,0,7,5,7,8,3,4,0,7,8,1,6,8,1,1,2,4,8,1,9,5,4,3,8,5,10,8,6,6,1,0,6,10,8,2,3,4]
Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1619: Mean of Array After Removing Some Elements
class Solution {
public double trimMean(int[] arr) {
Arrays.sort(arr);
int n = arr.length;
double s = 0;
for (int start = (int) (n * 0.05), i = start; i < n - start; ++i) {
s += arr[i];
}
return s / (n * 0.9);
}
}
// Accepted solution for LeetCode #1619: Mean of Array After Removing Some Elements
func trimMean(arr []int) float64 {
sort.Ints(arr)
n := len(arr)
sum := 0.0
for i := n / 20; i < n-n/20; i++ {
sum += float64(arr[i])
}
return sum / (float64(n) * 0.9)
}
# Accepted solution for LeetCode #1619: Mean of Array After Removing Some Elements
class Solution:
def trimMean(self, arr: List[int]) -> float:
n = len(arr)
start, end = int(n * 0.05), int(n * 0.95)
arr.sort()
t = arr[start:end]
return round(sum(t) / len(t), 5)
// Accepted solution for LeetCode #1619: Mean of Array After Removing Some Elements
impl Solution {
pub fn trim_mean(mut arr: Vec<i32>) -> f64 {
arr.sort();
let n = arr.len();
let count = ((n as f64) * 0.05).floor() as usize;
let mut sum = 0;
for i in count..n - count {
sum += arr[i];
}
(sum as f64) / ((n as f64) * 0.9)
}
}
// Accepted solution for LeetCode #1619: Mean of Array After Removing Some Elements
function trimMean(arr: number[]): number {
arr.sort((a, b) => a - b);
let n = arr.length,
rmLen = n * 0.05;
let sum = 0;
for (let i = rmLen; i < n - rmLen; i++) {
sum += arr[i];
}
return sum / (n * 0.9);
}
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.