The Uber Coding Interview

What are people saying about Uber's Interview

PROS

Good compensation and work life balance
Get to work on and solve some of the toughest engineering challenges
Ample growth opportunities with respect to learning and career advancement

CONS

It’s fast-paced and sometimes planning takes a hit and we end up doing some not-so-impactful work.
Not a strong mentorship culture–you’re frequently left to figure out things on your own
Prone to reorganization which can lead to stressful times

What Uber employees have to say about interviewing?

“It is a good idea to begin prepping for your technical interviews very early in the process. Your preparation should include three key components: preparing to talk about yourself, reviewing computer science fundamentals, and working on practice problems.”

“It is important to be able to give an “elevator pitch” about your background and why you are interested in the position that you are interviewing for. When talking about your previous experience, be sure to explain your personal contribution. For example, if you were part of a team developing a full-stack web application, be specific about what you contributed to the project.”

“We have found that the most practical way to interview software engineers is to present them with coding problems founded in real world engineering challenges. This means that we will not present you with logic puzzles or brain teasers such as “how many golf balls could fit in a school bus?” In short, what we are interested in seeing his how you translate your thoughts into code, and whether or not our approach to engineering matches well with yours.”

Uber SDE II Interview Experience | Motivational

What are people saying about Uber's interview?

“For the coding challenge/screening I was asked 4 coding problems with a 70 minute time limit. Two were on average Leetcode easy with the rest being medium/hard. The goal was to pass around 75% of the test cases combining all problems.”

“1 machine coding , 1 problem solving, 1 design, 1 HM and 1 Bar Raiser. All rounds were 1 hour except the 1st which was 90 mins long.”

“4 questions were asked in the technical assessment using code signal. Usually they recommend spending 10-15 min on each question. The passing score is around 780. Very easy to score 720 by solving 2.5/4 questions. One question is the tricky one but that’s what that gets you the score.”

Compnay Guides