I'm using the same technique. Taking MRs from Junior Devs together with the Ticket description, reducing the scope a bit and sprinkling different errors or inco

I'm using the same technique. Taking MRs from Junior Devs together with the Ticket description, reducing the scope a bit and sprinkling different errors or incomplete implementations here and there. In the interview, I'm checking of problems that the applicant notices and see how he approaches the problem. So far I've been satisfied with all hired who passed that test. And they liked not having to solve stupid whiteboard problems.