Uber Software Development Engineer interview questions

I applied via campus recruitment. 1st round consisted of 3 coding questions – on arrays, strings matrices. There were 3 rounds of interviews. 1st 2 rounds were tech interviews & 3rd was tech + HR.

Uber is working on some cool problems, as a software engineer it excited me to try it. Reached out to a recruiter via LinkedIn. Good - Standard questions and decent food in cafeteria. Actually, there is nothing else to write in this section. Cons - unorganized, not open to new ideas, un-professional, rude and not on time. Its a total chaos. Read below to see for yourself. After the initial phone screen. Had to wait, reached out again after 4 days and they wanted me to fly the very next day for f-f rounds. Which i declined due to sudden invite. Again there is no response from them for a week, reached out again and asked to fly in couple of days and i did this time (unorganized). Coming to f-f rounds. 1. A room was booked for me for whole day but people keep coming in saying they booked the room as well during my breaks (un-organized). 2. In one of the round a DP question was asked and i answered with Greedy which in this case works. Though the interviewer couldn't come up with a case where it fails, he kept on saying it will fail. So, i ended up giving DP solution (not open to ideas) 3. After 2 rounds of interview, next round was supposed to start on 1215 but nobody turned up till 1240 (not on time) 4. When i searched for my recruiter and reached out with this concern. She said the interview will happen by 1 or 1:15. And, i openly said, want to have lunch. Her reply was, didn't you have BreakFast while coming (rude). 5. When all the rounds including hiring manager round is over, i again called and asked the recruiter, what next ? Her reply was, its done, you can leave. Like i am in the middle of nowhere and no idea, how to exit from the building as well (chaos) Walked out happily that i am not going to work in this firm whatsoever. Uber has lived upto its expectation.