0
Challenge · 75The Interview Itself

Answering 'can you do better?'

Interviewused in ~85% of apps

The question is not a rejection. It is usually the point at which you have passed the first bar and the interviewer is finding out how high you go. Answering it badly is the most common way to turn a good session into an average one.

Core idea. Do not guess at a faster algorithm. Name the waste in what you have, and the improvement follows from removing it. If there is genuinely no waste, say so and say why, because a defended lower bound is a strong answer.
Playground, this isn't a screenshot
where 37 minutes actually go

Writing code is under half the time. Most lost interviews are lost in the twelve minutes before it, not during it.

↑ play a little first, then dig in