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 two integer arrays startTime and endTime and given an integer queryTime.
The ith student started doing their homework at the time startTime[i] and finished it at time endTime[i].
Return the number of students doing their homework at time queryTime. More formally, return the number of students where queryTime lays in the interval [startTime[i], endTime[i]] inclusive.
Example 1:
Input: startTime = [1,2,3], endTime = [3,2,7], queryTime = 4 Output: 1 Explanation: We have 3 students where: The first student started doing homework at time 1 and finished at time 3 and wasn't doing anything at time 4. The second student started doing homework at time 2 and finished at time 2 and also wasn't doing anything at time 4. The third student started doing homework at time 3 and finished at time 7 and was the only student doing homework at time 4.
Example 2:
Input: startTime = [4], endTime = [4], queryTime = 4 Output: 1 Explanation: The only student was doing their homework at the queryTime.
Constraints:
startTime.length == endTime.length1 <= startTime.length <= 1001 <= startTime[i] <= endTime[i] <= 10001 <= queryTime <= 1000Problem summary: Given two integer arrays startTime and endTime and given an integer queryTime. The ith student started doing their homework at the time startTime[i] and finished it at time endTime[i]. Return the number of students doing their homework at time queryTime. More formally, return the number of students where queryTime lays in the interval [startTime[i], endTime[i]] inclusive.
Start with the most direct exhaustive search. That gives a correctness anchor before optimizing.
Pattern signal: Array
[1,2,3] [3,2,7] 4
[4] [4] 4
Source-backed implementations are provided below for direct study and interview prep.
// Accepted solution for LeetCode #1450: Number of Students Doing Homework at a Given Time
class Solution {
public int busyStudent(int[] startTime, int[] endTime, int queryTime) {
int ans = 0;
for (int i = 0; i < startTime.length; ++i) {
if (startTime[i] <= queryTime && queryTime <= endTime[i]) {
++ans;
}
}
return ans;
}
}
// Accepted solution for LeetCode #1450: Number of Students Doing Homework at a Given Time
func busyStudent(startTime []int, endTime []int, queryTime int) (ans int) {
for i, x := range startTime {
if x <= queryTime && queryTime <= endTime[i] {
ans++
}
}
return
}
# Accepted solution for LeetCode #1450: Number of Students Doing Homework at a Given Time
class Solution:
def busyStudent(
self, startTime: List[int], endTime: List[int], queryTime: int
) -> int:
return sum(x <= queryTime <= y for x, y in zip(startTime, endTime))
// Accepted solution for LeetCode #1450: Number of Students Doing Homework at a Given Time
impl Solution {
pub fn busy_student(start_time: Vec<i32>, end_time: Vec<i32>, query_time: i32) -> i32 {
let mut ans = 0;
for i in 0..start_time.len() {
if start_time[i] <= query_time && end_time[i] >= query_time {
ans += 1;
}
}
ans
}
}
// Accepted solution for LeetCode #1450: Number of Students Doing Homework at a Given Time
function busyStudent(startTime: number[], endTime: number[], queryTime: number): number {
const n = startTime.length;
let ans = 0;
for (let i = 0; i < n; i++) {
if (startTime[i] <= queryTime && queryTime <= endTime[i]) {
ans++;
}
}
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.