Phone interview and then a coding exercise.

They provided a coding exercise for a simple mobile application, stating it should not take more than 4 hours. If it did, they advised against adding new features. I focused on the basic functionality, which took nearly 8 hours, leaving no time for UX improvements. I submitted the exercise, and they responded saying they had decided to move on.

One aspect I didn't understand was what they were looking for in the exercise. The basic features were working and bug-free. The UI was decent, and the UX was not bad, although it could have been improved. However, I lacked the time to do so.

I believe Uber has product people who focus on UX. Therefore, why are they looking for an engineer who excels at UX? An engineer's role is to convert product specifications into working code. Rejecting or evaluating an engineer based on incomplete UX seems illogical. I am glad I did not waste more time on it.

Advice to interviewers: Reconsider your expectations of an engineer. You are hiring someone to be an engineer, not a product manager with technical knowledge. They deserve at least a decent interview process. You cannot ask someone to spend 8 hours on a coding exercise and then reject them, not based on their code or knowledge, but solely on UX.