Ace Your Uber Frontend Interview

Hey everyone!

I have recently watched an Interview Experience / Hiring Process video by Shreya Prasad, SDE 2 @ Uber.

So, in this article, let’s break down and discuss the hiring process at Uber and interview experience of her using the insights she has provided.

Uber Hiring and Interview Process

Every Round is around 60 minutes

Combination of DSA and Technology applied for (Frontend / Backend / Fullstack, etc.)
Level Questions is mostly Medium
Uber specific DSA Questions can be found on Leetcode
Trees, Stacks, Queues, etc. can be asked
Follow-up questions can be asked based on our answer for the DSA questions

Frontend questions could be :-

Frontend interview resources :-

UBER EXPECTS CANDIDATES TO BE VERY GOOD AT DSA
Harder DSA questions will be asked
We should be comfortable with Leetcode medium questions and Interview standard questions
We are expected to solve the question quickly, so that they can ask follow-up questions on the same question
1 or 2 follow-up questions can be asked, and we are expected to modify our code as expected from us
Concepts can be Dynamic Programming, Arrays
We can solve the question in any language of our choice - no constraints here

(Frontend / Backend / Fullstack - Depends on what we applied for)

IN DEPTH UNDERSTANDING AND KNOWLEDGE OF JAVASCRIPT IS VERY MUCH REQUIRED.
Either pure JavaScript-based questions can be asked, or UI based questions can be asked.
Advanced JavaScript concepts like Handling asynchronous JavaScript, memoization, currying, etc.
For UI based questions, we should provide a working solution, which is high quality, readable, bug-free
Sometimes the Machine coding question can be as long as 3/4th the screen's height. It is important to read through the details, exclude irrelevant details.
Our way of approaching the problem, decoding it, etc., is judged by the interviewer.
Communication with the interviewer is very important.

These are typically asked for SDE 2 and above roles
The questions can be straightforward, like Designing a Google Calendar, etc.
We need to consider load, performance, security, etc. while designing the application
We might be expected to also talk about the backend design of the task
Resources - YouTube videos, Namaste Dev frontend system design course, MDN Docs
Justifying the approach, the tech stack we have chosen, etc, is very much important

(Behavioral Round, Past Projects, Situational Questions)

MANAGERS CAN EASILY FIND OUT IF WE ARE TELLING LIES ABOUT OUR PROJECT EXPERIENCE OR SKILLS
It can be technical + management kind of round
Past projects and experience can be asked
Interviewers try to delve into the technical details and our skills
Managers try to understand our ownership in the project, our contribution in the project, the technical complexity of the project, etc.
We can be asked about the challenges we have faced while working on the project, what was the purpose of the project, how many members are involved, whom are we looping in while working on the project, etc.
We can be asked about why the project was using those technologies involved in it, and why other technologies can't be used.
We can be asked situational questions and our answers are evaluated and checked if they are aligning with Uber's values, to check if we are a cultural fit or not.
Managers also try to understand how truthful we are, how interested we are in the role and the company, how much we know about the company, its cultures, values, etc.

Like, share and follow me for more such content. Take care!