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.
There are n soldiers standing in a line. Each soldier is assigned a unique rating value.
You have to form a team of 3 soldiers amongst them under the following rules:
i, j, k) with rating (rating[i], rating[j], rating[k]).rating[i] < rating[j] < rating[k]) or (rating[i] > rating[j] > rating[k]) where (0 <= i < j < k < n).Return the number of teams you can form given the conditions. (soldiers can be part of multiple teams).
Example 1:
Input: rating = [2,5,3,4,1] Output: 3 Explanation: We can form three teams given the conditions. (2,3,4), (5,4,1), (5,3,1).
Example 2:
Input: rating = [2,1,3] Output: 0 Explanation: We can't form any team given the conditions.
Example 3:
Input: rating = [1,2,3,4] Output: 4
Constraints:
n == rating.length3 <= n <= 10001 <= rating[i] <= 105rating are unique.Problem summary: There are n soldiers standing in a line. Each soldier is assigned a unique rating value. You have to form a team of 3 soldiers amongst them under the following rules: Choose 3 soldiers with index (i, j, k) with rating (rating[i], rating[j], rating[k]). A team is valid if: (rating[i] < rating[j] < rating[k]) or (rating[i] > rating[j] > rating[k]) where (0 <= i < j < k < n). Return the number of teams you can form given the conditions. (soldiers can be part of multiple teams).
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array · Dynamic Programming · Segment Tree
[2,5,3,4,1]
[2,1,3]
[1,2,3,4]
Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1395: Count Number of Teams
class Solution {
public int numTeams(int[] rating) {
int n = rating.length;
int ans = 0;
for (int i = 0; i < n; ++i) {
int l = 0, r = 0;
for (int j = 0; j < i; ++j) {
if (rating[j] < rating[i]) {
++l;
}
}
for (int j = i + 1; j < n; ++j) {
if (rating[j] > rating[i]) {
++r;
}
}
ans += l * r;
ans += (i - l) * (n - i - 1 - r);
}
return ans;
}
}
// Accepted solution for LeetCode #1395: Count Number of Teams
func numTeams(rating []int) (ans int) {
n := len(rating)
for i, b := range rating {
l, r := 0, 0
for _, a := range rating[:i] {
if a < b {
l++
}
}
for _, c := range rating[i+1:] {
if c < b {
r++
}
}
ans += l * r
ans += (i - l) * (n - i - 1 - r)
}
return
}
# Accepted solution for LeetCode #1395: Count Number of Teams
class Solution:
def numTeams(self, rating: List[int]) -> int:
ans, n = 0, len(rating)
for i, b in enumerate(rating):
l = sum(a < b for a in rating[:i])
r = sum(c > b for c in rating[i + 1 :])
ans += l * r
ans += (i - l) * (n - i - 1 - r)
return ans
// Accepted solution for LeetCode #1395: Count Number of Teams
struct Solution;
impl Solution {
fn num_teams(rating: Vec<i32>) -> i32 {
let n = rating.len();
let mut res = 0;
for i in 0..n {
for j in i + 1..n {
for k in j + 1..n {
if rating[i] < rating[j] && rating[j] < rating[k] {
res += 1;
}
if rating[i] > rating[j] && rating[j] > rating[k] {
res += 1;
}
}
}
}
res
}
}
#[test]
fn test() {
let rating = vec![2, 5, 3, 4, 1];
let res = 3;
assert_eq!(Solution::num_teams(rating), res);
let rating = vec![2, 1, 3];
let res = 0;
assert_eq!(Solution::num_teams(rating), res);
let rating = vec![1, 2, 3, 4];
let res = 4;
assert_eq!(Solution::num_teams(rating), res);
}
// Accepted solution for LeetCode #1395: Count Number of Teams
function numTeams(rating: number[]): number {
let ans = 0;
const n = rating.length;
for (let i = 0; i < n; ++i) {
let l = 0;
let r = 0;
for (let j = 0; j < i; ++j) {
if (rating[j] < rating[i]) {
++l;
}
}
for (let j = i + 1; j < n; ++j) {
if (rating[j] > rating[i]) {
++r;
}
}
ans += l * r;
ans += (i - l) * (n - i - 1 - r);
}
return ans;
}
Use this to step through a reusable interview workflow for this problem.
Pure recursion explores every possible choice at each step. With two choices per state (take or skip), the decision tree has 2ⁿ leaves. The recursion stack uses O(n) space. Many subproblems are recomputed exponentially many times.
Each cell in the DP table is computed exactly once from previously solved subproblems. The table dimensions determine both time and space. Look for the state variables — each unique combination of state values is one cell. Often a rolling array can reduce space by one dimension.
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.
Wrong move: An incomplete state merges distinct subproblems and caches incorrect answers.
Usually fails on: Correctness breaks on cases that differ only in hidden state.
Fix: Define state so each unique subproblem maps to one DP cell.