Hard disagree on the bit about uncle Bob. Everything he says isn't gold but his take on clean architecture and use case driven development is pure magic.
Coders at work was a far better resource in that regard, every person that was interviewed has made significant impact in the world of computing and is discussing hard earned lessons about building software.
He wrote the books. That's what he did.
What was in the books let me build things faster and with more malleability that has been a game changer in my career.
Do you just ask them to walk you through the architecture by memory? If so what how do you come up with questions about their choices without the specificities of the actual way they wrote their code?
Basically see if they could communicate how the system worked, it’s good points and bad points, and how deep they could go. This quickly separates the good developers from the cargo culters and pretenders. It also is a good gauge of how much real experience they have had.
Generally, if someone can’t describe at least the rough outline of the architecture of an application they have worked on, that’s a strong signal they are going to struggle as a developer
depends on the role, e.g. for infra work i can ask "if you had complete autonomy to stand up this project again, what would be your first step" and then we go from there
Asking random questions about technology mostly tests their ability to memorize facts. I want people who know how to build things in the real world, not those who excel at adding certifications to their LinkedIn.
A parting word - if you are leaning towards Uncle Bob for wisdom, you are heading in the wrong direction.