Started with a phone interview which went fine. The on-site interview was really a mess. You have no idea what type of role you're interviewing for until you get there and they place you with a team they think you would be a "best fit" for. I had absolutely no interest in that teams project and had I known what I was interviewing for I would have declined the interview completely.

First part of the on-site was a manager interview which is the normal interview routine of talk about projects and your work history. My first technical interview was ok until it turned into a permutation algorithm that I needed to implement intuitively. I hope you have a permutation algorithm memorized because it's not easy to figure out on a whiteboard.

Lunch was an interview with another manager. It included more info about another team I had no interest in working on.

The second technical interview was an absolute mess though. There were two people conducting the same interview at the same time because they didn't know who was supposed to be interviewing me so they both did. Which lead to them disagreeing with each other multiple times and lead to me having to convey that I understood the problem and having the issue where one of them was satisfied with my understanding and the other wasn't. So the whiteboard hazing continued.

The whiteboard hazing was kind of unreal. We used it to explain the problem using diagrams and such and then go over an approach to solve the problem. But what they wanted was for me to peusdocode out the entire problem, into the finest details of how long my loops, arrays, and what my grid sizes were all on the whiteboard. Code without actually coding.

I asked if I could peusdocode on my laptop that was hooked up to a giant monitor and one guy said yes and was satisfied with it but the other guy wasn't because it wasn't on the whiteboard.

So we talk about the same aspects of the problem over and over again while I was sitting there ready to start coding until time was up.

Coins on a clock, it's basically the hashlife problem.

Sum of squares within squares.