Interviewed with Uber a couple of weeks ago as part of hiring event. Had 2 coding rounds, 1 system design and 1 hiring manager / bar raiser. I was expecting one programming exercise and one coding (whiteboarding kind) but to my surprise they both were similar in terms of the style and even the kind of question I was given. Both involved backtracking - one permutation and the other combination. The interviewers in both rounds expected me to execute the code. I was able to generate correct output in the first one. Same for the second coding round except that the final result had duplicate entries and we ran out of time. I have no idea what is the evaluation criteria at Uber. Would be great if someone can share that. Current Location: Seattle YoE 8 Current TC: 205
So i recently got an update from uber about the rejection "the recruiter said it was very close to an offer". Looks like my bar raiser was the behavioral round and I was asked by the recruiter before onsite to mention part of the project with you own contributions, which i did but led to the usage of "I" problem. All my coding, system design were a breeze, and I had lots of time left after each of those rounds, with +ve feedbacks later. But BR kinda jyxed it for me. But its fine, all the best UBER i will try again when i can :)
Did you get a callback from recruiter or an email ?
Running code in general is the expectation. Translating thoughts to code becomes a big gap as you rise in your career. Some BRs tend to go with a smaller coding problem too.
Got it. But do they look for completion with edge cases passing too? Or do they also give as much importance to the communication and collaboration and may overlook edge cases
BR was only on my past projects, no coding involved there. That one went really really well I think but I sense that it wouldn't matter if I did very badly in one of the coding rounds