I'm against classic leetcode style interviews - asking questions wholly unrelated to any problems they'll encounter in the job. And understanding someone's abil

I'm against classic leetcode style interviews - asking questions wholly unrelated to any problems they'll encounter in the job. And understanding someone's ability to review code is definitely a useful thing to understand. But I don't see how it tests whether someone can efficiently architect and build an appropriate solution to a problem. I think that's a pretty important thing to test. And that's what leetcode style questions are supposed to do, but have gotten completely out of hand (imo). For what it's worth, I think great interview questions are taking problems you or others have solved (or tried to) at your company - something they might do too - and see what they can manage. It'll start an on topic conversation at the very least, gets sense of their experience, seniority and mental dexterity at the least. If you have them fully implement- coding ability too. I've worked with engineers that are pretty good at reviewing code, but not the strongest engineers for one reason or another (weaknesses in architecture or ability to get stuff done).