That’s similar to the “thought process” questions I use to try to figure out how someone thinks in interviews as well, they are super useful.

A few years ago I started asking just one question:

Can you describe the architecture of a recent project you worked on?

Usually we’d then start a discussion about deployment pipelines, tech stacks, methodologies and the like used. I haven’t done many interviews and I hate trying to corner people into sneaky tech corners. It makes me uncomfortable . I just want to know if the person understands the big picture when they are working on isolated pieces and it gives me a good sense of their communication/ “presentation” skills.

Very much agree on all that!