[geraldwhen]

These are horrible interview questions. Data issues like this do pop up in the real world; heck I deal with them.

But when you run into <algorithm> or <feels like algorithm>, the correct solution is to slow down, Google, then document your work as you go. In a real application log n may be insufficient. But coding interview exercises need tight constraints to fit the nature of the interview.