The interview process began with a standard phone screen, followed by an onsite interview with five individuals, primarily engineers and the hiring manager.
One engineer stood out and made my experience less than ideal. He didn't seem particularly interested in being there, and I struggled with his question.
Overall, the process went smoothly, and most of the team was friendly.
I did not accept the offer. The company attempted to down-level me, and I missed a main algorithmic question. Additionally, the offer was low, consisting of approximately 125,000 in base salary and about 200,000 in RSUs vested over four years.
System Design:
Algorithms:
Similar to LeetCode questions. I did not perform well here; there was only one way to solve the problem, and I did not arrive at it.
Coding:
Build a practical front-end component using HTML, CSS, and vanilla JavaScript. Be proficient in:
No trickiness or algorithms are involved here.
Behavioral:
Interview with the Hiring Manager. Discussed typical behavioral questions, such as how to handle situations with peers.
The following metrics were computed from 1 interview experience for the Uber Front End Engineer role in Seattle, Washington.
Uber's interview process for their Front End Engineer roles in Seattle, Washington is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Uber's Front End Engineer interview process in Seattle, Washington.