The process included a phone screen by a recruiter, a Google Hangout with two engineers, and an in-person interview with four pairs of engineers.

The questions were different than in other interviews I've had with this structure. In those interviews, the questions leaned more towards algorithms and problem-solving. These questions were open-ended architecture questions, and I definitely prefer the more open-ended architecture questions.

All of the interviewers were pleasant, with the exception of one. I was struggling to communicate my answer, and that interviewer was openly frustrated—the first time I've seen this happen, though I've interviewed with this structure at three other companies. They even sighed out loud in frustration.

Uber expressed that the interview was meant to simulate a regular workday. In my opinion, this would have been unprofessional in a meeting, but perhaps this is normal at Uber? My opinion may also stem from the fact that I have never worked at startups with a very young engineering culture.

I was excited to be given the chance to interview at Uber, but after the interview, it was clear I didn't fit in with the culture.