I've recently started giving a code review interview. I show them a toy example involving a few classes and a some tests and ask them to review it in terms of

I've recently started giving a code review interview. I show them a toy example involving a few classes and a some tests and ask them to review it in terms of correctness, maintainability, testability, etc. Once they've identified some problem areas, I then have them edit the code and ask them to make the changes they suggested. I think it's been working well since there have been examples of people doing well on algorithms questions, but not noticing a single problem with lots of bad code. I think the question works better for more experienced candidates.