• Recruiter call

• 1-hour easy phone interview

• Onsite:

  • Create an app that loads images from Flickr and displays them on a collection with a search bar. Everything should work, and the architecture should be good. (1.5 hours; I couldn't finish the project on time because it would take a minimum of 2.5 hours to complete.)
  • 1-hour discussion of the code you wrote with some vague and unclear questions.
  • Easy coding question on HackerRank. The code must build and pass test cases.
  • Lunch and behavioral interview. The interviewer eats and asks you questions (you can't eat because he is talking; you just have to watch him eat).
  • Bar raiser: A terribly hard question that they struggled with for days, and now they want you to implement it within 1 hour.
  • Another system design with a junior engineer (I will keep the rest for you to guess).

Overall, if you are interviewing with Uber for the money, it is definitely not worth it (don't make my mistake). But if you are interviewing because you are passionate about Uber (I don't think anyone is), then give it a try, and you might make it.

• You have a list of function names and timestamps. Print the time spent on a function when exiting it.

Example:

• main, 0 entering
• foo, 10 entering
• foo, 15 exiting
• main, 25 exiting