Uber L4 Interview Experience Ongoing
Anonymous User
5475

I hope this will be helpful for the people preparing for uber interviews

Exp: 4.8y (startups)

BPS round:

  • Alien dictionary
    • covered all edges cases
    • and everything ran pretty good in first go
    • completed in 20 mins

Round 1: Dsa postponed multiple times

  • In a linked list, reverse every k nodes in the list, if the nodes is < k , leave it
    • A->B->C->D->E, k =2 output: B->A->D->C->E
  • similar to bus routes problem (BFS) dont' remember question properly

Round 2: Machine Coding Round

  • My worst interview experience in 4.8 years
  • R1 got postponed next week so they started with R2
  • Interview said to cancel when he is unable to join and asked me to join after 30 mins
  • got the time for 40mins (basically extend it to 10 more mins because he has some meeting)
  • Asked my experience and this went to 15-20mins (kept on asking in detail)
  • gave a problem similar to job scheduler
  • kept on asking the HLD of this problem (he told expectation from this round is LLD + HLD as he is staff engineer)
  • mentioned HLD design quickly but not in structure as I told there is around 10 mins I will start the LLD
  • he is new to go but I have explained the patterns and why? (literally i have 5 mins, I am just speaking quickly)
  • even in this time, he kept asking about push vs pull flow etc instead of LLD and I am unable to write the code and run it
  • Finally just wrote the structures, explained the patterns

Slightly No, but hr knows about this and as r1 is strong hire. she pushed me to bar-raiser+HM. After schedulling the interview, I was ill so I can't attend the interviews. After discussing the Bar-Raiser round has been postponed and HM has been cancelled. Now from the verdict of Bar-Raiser round, they will move forward to HM or drop the application.

Round 3: HLD/Bar Raiser

  • Design Uber Eats home page for customers travelling on train
    • Input PNR
    • Output Ordering food based on station it needs to be delivered
  • This time I followed structure way
    • FR, NFR (cap,scale), core entities, HLD , DB/Cache, Deep-dives

Response: Awaiting

  • He kept on asking many questions and I have answered and in few cases, he corrected me
  • Currently I am unsure of this round

I will update further once I got the feedback

LinkedIn Interview Experience: https://leetcode.com/discuss/post/7196831/linkedin-senior-software-engineer-interv-bjx3/

Comments (3)