Uber Interview Experience for SDE

Improve Article

Save Article

Like Article

Improve Article

Save Article

Round 1: DSA (45 mins): The interviewer introduced himself first and then asked about me. I told him in brief(2 mins only), and he laughed when I completed it. 

  • Then he shared a link to the Codesignal platform, the question was about graphs. 
  • You are given a 2D grid, with D(down), R, L, and U characters, a source, and destination coordinates. You can either take the path as the one given in the cell, i.e. if D is present you can go down or you can change the edge.
  •  You have to give the minimum number of edge changes to reach the destination. 
  • He gave me 3 test cases and ran the code on them. Initially, the code was giving answer 2 and we both thought that the answer should be 3 but on the dry run, we found that 2 was the right answer(so don’t stop and think u r wrong dry run your code), there were redundant loops so asked me to concise the code 

So I did it, and at last, he was satisfied with the solution.

Round 2:OOPs(Low-level system design 50-60 mins): 

  • You have to design an application that comprises multiple devices, FAN, TV, etc. 
  • There are 4 functions that must be implemented 1) register device 2) unregister_device 3) run command 4) add command.
  • There were some generic commands like ON / OFF devices common to all and some that were device-specific. The question was quite unclear, I asked a lot of questions as he told me to write the whole code (again on code signal). I told him I would go with Interfaces and class that would implement each device but
  • I was facing a problem so I switched to Class and extended others from this Device class. I was continuously talking with the interviewer about what I am doing,
  • Do you think this will work or what do you want the function to do,
  • What type of command will be given, 
  • Do we know the device and commands beforehand etc?

Round 3: HR(45 mins): He asked me to introduce myself(again don’t talk for more than 2-3 mins). He was impressed with the intro a bit. 

  • Then he asked about my projects
  • He asked about uber, then I took him into the discussion of uber’s architecture, he went to the details of its architecture, 
  • Then he asked about my MTP, then asked whether I did any work in a team, did I face any problems, what was the negative feedback in the MTP presentation, 
  • What is my plan for the proposed architecture, 
  • How did I decide on the architecture, 
  • How much do I implement, what would I do if my teammate is not doing work, what will I do if I have a decision conflict during my work with a colleague, and similar behavioral questions?

Verdict: Selected
 

Like this post? Please share to your friends:
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: