Me too. I interviewed at a few places in March for senior roles and there wasn't any algo gotchas. Some coding, I think mostly to make sure I could code. But a lot more emphasis on architecture and team skills.

So maybe there's the gap between senior roles and mid/jr/new.

But my question then is, how are senior folks training/picking folks to replace them? It must not be happening in the interviews, maybe on the job?

I've noticed the more experienced I get the less technical the questions are. My last interview was just a general chat about type systems, the good and bad of Haskell, why I have been using common lisp recently in my spare time, etc... No coding questions, no leetcode, no code walkthroughs -- I really enjoyed it.

Yes, but in my experience you need both. If you are not willing to put in some time at leetcode it might not go well. Of course you can still get lucky, but better to be prepared.

Oh, you definitely need both. But there is a misconception that Leetcode skills alone is enough, but for more senior roles you get judged on more than that.

Leetcode skills are something you need to do in your free time. That's why it is the most talked about.

Well, in my experience working is also sadly something I have to do in my "free time".