Experience: 10 years
Position: MTS
Location: San Jose

I was contacted by Uber recruiter on Linkedin

Round 1 - Phone screen
-- Medium LC with alot of test cases. Similar to top K

Round 2 - DSA -- 60 minutes -- Medium
-- This was a medium-hard question and a variation of alien dictionary . I explained my approach and sort of froze after 10 minutes into coding. Interviewer helped me throughout and came to a final working solution. He had to ask a second coding question too, but could not due to time.
I did the worst in this

Round 3 -- DSA -- 60 minutes -- Dive in depth
-- Variation of Key Value storage. And some Transaction handling. Design LLD and code
I did okay and came to a working solution

Round 4 -- HLD Basic Uber feature
Did great. Overall, the interviewer was happy. I followed this approach

1. Know the user/actors of the system
2. Be clear with features/modules to be designed
3. Understand and discuss the scale of the system
4. Consistency/Availability to be supported
5. Picturise the sequence of events
6. Thourough API design
7. Start architecting the system with microservices
8. Discussing the client-server interaction
9. Indicate and discuss data flow with databases in mind (scaling, caching, sharding)
10. Challenge the resilience of the system
11. Other topics - health checks, logging and monitoring, security, low level design of some features

Round 5 -- Behavioral+Past project
-- Asked me about my previous projects and tech in depth
-- Asked me about all the design choices i made in the project and why so
Explained my past project.

Went well too.

I feel like I messed up in DSA and my chances are perhaps very low.

Thanks for reading.