The bar has also been raised significantly. I had an interview recently where I solved the algorithm question very quickly, but didn't refactor/clean up my code perfectly and was rejected.
I truly don't doubt that's what happened, I've had it happen, but when it did their feedback was (insultingly) not up to their professional standard. I say insultingly because it was an amateurish evaluation of what I did, specifically because it was like the 5th god damn interview by that point and really they should have been looking for more than trivialities like the coding style I chose to use in HackerRank with a visible ticking clock.
The reason I ask is just for context; if people are interviewing for Senior roles and being rejected for code formatting problems, something is even more deeply wrong than it seems, since they probably shouldn't be concerning themselves with that _at_all_. If it's possible though that you were rejected for some other reason, but that your code style was the strongest negative apparent signal, that's also worth exploring. In my case, that's a possibility, that they were looking for just one more reason to narrow the funnel, but it can be hard to accept.