Review a series of pull requests
You get two or three pull requests, each harder than the last, in Python or Java. Read each one, leave comments as you would on a real review, and point out bugs, design problems, missing tests and risks in production. The interviewer mostly watches, so you set the pace and decide what matters most.
No answer yet. Write the first one; the best answer gets endorsed.