Any software role
Coding problem: Moving Median. Given a list of integers `values` and a window size `k`, return the median of every window of `k` consecutive values, from left to right. There are `len(values) - k + 1` windows; return an empty list when `k` is larger than the list.
TechnicalSeniorTests: Problem solving
Drill this questionCreate a free account to answer out loud with Ava and get feedback.
What the interviewer is looking for
- What a strong solution looks like: two heaps — a max-heap for the lower half and a min-heap for the upper half — with lazy deletion of values leaving the window (a hash map of pending removals) and rebalancing; or a sorted container with binary-search insert and delete. Heaps give O(n log k). A sorted list with bisect insert/remove is O(n·k) in the worst case but fast in practice; re-sorting every window is O(n·k log k). Accept the simpler versions if they can explain the cost.
- Think aloud. Interviewers are judging how you reason, not only the final code.
- Be ready for: A moving average is O(1) per step — why is the median harder? Approximate percentiles over an unbounded stream (t-digest, HDR histograms). How would you report p95 latency per minute across a fleet?
A structure to follow: Clarify, plan, code, test, analyse
- Step 1
Clarify
Restate the problem, ask about empty input, duplicates and size limits, and agree on one example.
- Step 2
Plan
Say the simple approach first and its cost, then the better one. Explain why before you type.
- Step 3
Code
Write small named steps and talk through each. A clear solution beats a clever one.
- Step 4
Test
Walk your own example through the code, then an edge case. Fix what you find calmly.
- Step 5
Analyse
State time and space cost in plain words and say what you would change for much larger input.
This is guidance on shape, not a script. Use your own real experience and facts; never invent details to fill a gap. See the STAR guide and answer frameworks.
Common slips
- Starting to code before agreeing what the answer must be.
- Going silent when stuck instead of saying what you are trying.
- Never running your own example through the code.
How to practise it
Solve it once in the editor without hints, then explain your solution aloud in under two minutes.
Related questions
- Coding problem: Pair With Target Sum. You are given a list of integers `nums` and an integer `target`. Return the positions of the two different entries that add up to `target`, as a list `[i, j]` with `i < j`.
- Coding problem: Balanced Brackets. Given a string `text`, decide whether its brackets are balanced. The bracket pairs are `()`, `[]` and `{}`; every other character is ignored.
- Coding problem: First Unrepeated Character. Given a string `text`, return the index of the first character that occurs exactly once in the whole string. Return `-1` if every character repeats.
- Coding problem: Palindrome After Cleanup. Decide whether `text` reads the same forwards and backwards once you drop every character that isn't a letter or a digit and ignore letter case.
- Coding problem: Totals by Category. Each record is an object `{"category": string, "amount": integer or null}` describing one sale, with the amount in cents. Return an object that maps each category to the sum of its amounts.