in the phone interview: - pretty basic python algorithm question. Having read the others here, I assumed I'd get pitched a softball and then a harder question. I was able to solve it within the first several minutes, but spent the rest of the session trying to optimize the solution. - some basic SQL questions on joins and such. I answered probably 5 or 6 questions. Both of these interviews seemed like minimum bar screens. For the in-person interview: - more difficult python question and had to code on a white board. It was a pretty simple sorting question that was easy to solve but less trivial to optimize. - more difficult SQL questions. I struggled here but I was a bit weaker in SQL so I figured as much. This progressed into dashboard design. - Lunch was at a cafe on campus and delicious. Interviewer was just asking me about work experience and culture and it seemed just like a general personality compatibility test. - Full Stack interview was my favorite part and a lot of fun. Without giving too much away, I was given a realistic problem and tasked with conceptualizing the solution in real time, from start to finish, on a white board. It was a mix of coding and conceptual and seemed to be meant to test product sense.
Anonymous
Yes PLease can you please let us know what kind of coding is asked during the full stack interview
Check out your Company Bowl for anonymous work chats.