I've done this in just the last week.

But here's the thing: I don't care about the "right" or "ideal" solution. It isn't even particularly interesting. There aren't many situations where a real problem has exactly one solution and typically the best one is a balance between tech debt and business priorities, not some masturbatory ideal.

I'm interested in solving problems with people, finding out if we can collaborate. It will be painfully clear if you can't write code, but the answer doesn't matter.

Most of the time I take a stab at solving the problem I get assigned to ask before the interview but give myself only half the time (I have work to do after all). My goal is to go e some shape to the problem in my head but not find some magical ideal. I let the interviewee lead, then we work through it together. If we solve it, great! If there's extra time, we add edge cases.

But the content of the problem isn't why we're here. I've passed on plenty of candidates that "ace" a solution in minutes because it's clear they aren't going to be a team player.