Here's my interview experience:
Round 1: A medium-difficulty string + hashmap question. I found the approach pretty much right away and had no trouble talking it through before I started coding. At the end there was a follow-up on how to make the code more production-ready.
Round 2: An easy heap question. I basically figured out to use a heap and that solved it. The interviewer was pretty nice, and there weren't really any follow-ups — they left about ten minutes for Q&A.
Round 3: A medium-to-hard OOD question. They gave me a scenario where I had to design my own classes/objects and then write a method. At first I didn't really understand the problem, so I spent a while asking clarifying questions, but once I fully understood it I designed the solution pretty quickly. I only finished writing the code with about five minutes left. The interviewer was fairly young and based in Texas, so the whole thing felt pretty chill.
Round 4: A behavioral round. Roughly the first half was about my resume and the second half was hypothetical questions. They dug pretty deep into my resume, but the later questions felt more like a conversation than a Q&A, so overall it was a pretty good experience.
Discussion
Loading comments…