I agree. Our interview has 3 coding rounds, and one of them I call "clean code". For that I ask a straightforward question that requires candidate to define some APIs and write some classes / functions. Then I ask several follow ups, adding or changing requirements.

This is by far my favourite question, the one closer to on-the-job coding. It also lends itself well to deep conversations with candidates.

But alas I don't own the process and still have to work within the parameters of the company. Whenever possible I ask this kind of questions, but other interviewers will default to leetcode-style rounds.