Better questions are those that more closely simulate a work sample, being aware that an interview is high stress and time boxed and thus not actually like work

Better questions are those that more closely simulate a work sample, being aware that an interview is high stress and time boxed and thus not actually like work. I like an hour or more pair programming in a language the candidate is comfortable with on a simplified problem with some relevance to work. For more senior candidates, you definitely wouldn't want to waste everyone's time with brain teasers because if the high risk of a hasty rejection - a deeper probing into systems they've built and and designed in the past, with an angle on relevant problems for the business, along with the pair programming.