Initial recruiter call 2 hour first round 4 hour final round I had the absolute worst coding interview experience I have ever had during the final loop. (I've done ~30 coding interviews in my past.) one of the final round interviews was a coding problem with a Principal engineer. There were two different instances in which he assumed I was wrong in my approach and the code later demonstrated I was correct. In both instances, he took up a significant portion of the 1 hour interview to try to explain to me what was wrong with my approach when there was absolutely nothing wrong with it.

He also didn't come with test cases written so I had to take 10 minutes to create input for test cases. It seemed he doesn't usually ask people to write test cases but wanted me to because he was convinced it wasn't going to work. (the input was a multi-layered data structure so it wasn't trivial.) once I did, it worked perfectly without any modifications. Throughout the process, it was clear that when he didn't understand what I was doing right away, he assumed it was incorrect and wasted a lot of my precious time in the process. This was the only interview I had that didn't go super well so I'm confident it's the reason I didn't get an offer.

Given a library of books, write a function to return all words that occur in every book in the library. Create an OOD diagram to represent a parking garage. Design a system that will build word clouds. It has access to the words from all books that have ever been written and can create a word cloud from that dataset using filters, potentially multiple at a time: year, author, etc. Design a system to support 1-player and 2-player solitaire.