I always struggled with this. Give me a list of things to memorize and a rigid test - and I'll struggle. Put me in a real environment with access to documentat

I always struggled with this. Give me a list of things to memorize and a rigid test - and I'll struggle. Put me in a real environment with access to documentation, actual team members, and time to learn and understand a system? That's where I actually shine. Something I kinda like the idea of for a "code interview" would be a "reverse interview". E.g. give them some sample code (likely from production) and ask them to critique it and review it. I'm no expert in SQL - but I can still spot an injection vector. If I need to use SQL regularly then I'll learn it as needed, etc.