The interview lasted 24 minutes and ended very badly. I was not expecting a technical interview; I was expecting a more general and recruiter kind of talk. The interviewer asked me about SQL syntax, which I felt was not a good estimate of my programming skills. The second part, OOP design, was very difficult: implement a version control system. I totally blew this problem because I was overwhelmed by the complexity of a VCS (I use Git, so I was thinking about Git the entire time), and was not able to focus on the bare minimum components that made a VCS work. There were few hints. The questions were harder than my Google interview questions. I consider them very difficult for the entry level job I intend to interview for. Maybe there are people fresh out of college capable of answering those questions, but they certainly will not end up being at TripAdviser.

Good, although, sometimes struggling in providing you information about when interview will be leaving you wondering. Technical interview was good, I went into in uncertain as I wasn't sure about if I could solve a challenge. Recruiter was very nice and informative as well. Gutted to not progress onto next stages but they layout whole process for you and provide with you with feedback even if you fail the technical interview. I hope to re-apply soon when I become more confident with approaching technical assessments cause these do not correlate with your day to day duties as SE.