July 8, 2026
Median madness in the comments
A software engineering interview question I like: computing the median
A tiny math test sparked big feelings, flexes, and a full-on comment-section showdown
TLDR: An engineer says asking candidates to find the median is a great simple interview test because it exposes real coding ability without resorting to silly puzzles. Commenters turned that basic idea into a drama fest, arguing over faster shortcuts, showing off advanced tricks, and joking about developers overcomplicating everything.
A software engineer shared his favorite interview test: find the middle number in a list. On paper, it sounds harmless — almost suspiciously harmless. But the community instantly turned this humble question into a full-on personality test. Supporters loved it because it reveals whether someone can handle basic coding, think through edge cases like an empty list, and explain simple design choices without hiding behind brain-bending riddles. In other words: less “genius puzzle,” more “can you actually do the job?”
But the comments quickly became the real entertainment. One crowd basically screamed, “Why sort everything when you only need the middle?” That opened the door for the algorithm show-offs, who wasted no time parachuting in with claims about faster methods and linear-time tricks. Another commenter cheerfully escalated the whole thing from median to percentiles, because apparently one innocent interview question was not enough suffering for the rest of us. Then came the pure comedy: a jab about “high-quality candidates” bravely importing a mountain of outside code just to check whether a number is even — a joke that hit because everyone knows that one developer.
The vibe? Half practical hiring advice, half nerd peacocking, with a side of academic one-upmanship. Even a bare Wikipedia link landed like a mic drop. For a question about the middle, the comments were absolutely all over the place.
Key Points
- •The article describes a software engineering interview question that asks candidates to compute the median of an array of numbers.
- •The author says the question is intended to assess straightforward programming ability while allowing deeper technical discussion.
- •The article highlights design considerations including sorting strategy, caller versus function responsibility, mutation of inputs, and performance implications.
- •The problem includes common implementation details such as empty-input handling, off-by-one risks, and separate logic for even- and odd-length arrays.
- •The article provides a Python example that sorts the input, raises an exception on an empty list, and returns either the middle value or the average of the two middle values.