Overall, it was a nice experience with Uber in Amsterdam. The recruiters and interviewers were respectful and timely with their answers.

I was scheduled to have two phone interviews before an on-site. I made it to the second one before being unexpectedly cut, for reasons I'll detail below. When I asked for more specific feedback, the recruiter was kind enough to collect it and share it over the phone.

The first phone screen was mostly a coding question using a shared editor on HackerRank. It was primarily data structures-related, and when I got a bit stuck on one part of the problem, the interviewer and I talked it through.

The second phone screen involved a short discussion about a past project, followed by a high-level design discussion, and a coding question at the end. I really thought I breezed through every portion. The interviewer never challenged me and only had to sit back and watch while I was implementing the live coding question. There were some minor compilation errors at the end (a missing constructor and getters/setters, and using a method that was part of the List interface instead of the Collection interface). Nothing was show-stopping, and immediately afterwards, the algorithm printed the correct solution on the first try.

Afterwards, I received a rejection. After the call, I found out that although the interviewer found me to be very communicative, my "coding speed" and "syntax errors" ultimately led to my rejection. I'll let you draw your own conclusions there.

Basic data structures and algorithms, with more emphasis on data structures.

However, I suppose more emphasis should be placed on coding speed and syntax, even if you can solve the question in the required time and get a running program.