Uber Frontend Engineer interview questions

5 Frontend Engineers have shared notes from their Uber interviews, with the questions they were asked in each round. That is 2% of the 263 Uber interview notes on Screna AI.

5 Frontend Engineer interview notes

Uber·Frontend Engineer·Technical Phone Screen

Jun 2026
Uber frontend interview that threw a graph problem at me, which felt a bit out of left field for the role. Not a ton of context around the round itself but the problem was meaty enough to remember.
  • Given a list of flights with source, destination, and cost, find the cheapest route between two cities using at most k stops. Return -1 if no route exists.

“Classic shortest path with a constraint, which meant vanilla Dijkstra wasn't quite right.”

View Post

Uber·Frontend Engineer·Onsite - System Design / Architecture

Jun 2026
Virtual onsite for a frontend engineer role at Uber. Single system design question, design Google Calendar. Not a lot to go on but it's a meaty enough problem that there's plenty to talk about.
  • Design Google Calendar.

“This one has more surface area than it looks.”

View Post

Uber·Frontend Engineer·Onsite - Coding / Algorithms

May 2026
Coding round at Uber for a frontend role. The task was to build a Parking Lot system in React, and the in-team interviewer looked like they hadn't slept in days, which made the whole thing feel a bit odd.
  • Build a Parking Lot system using React.

“More of a UI design and state management problem than a pure algorithm question.”

View Post

Uber·Frontend Engineer·Technical Phone Screen

Apr 2026
Phone screen for a frontend role at Uber. One algorithm-ish problem, pretty open-ended, which I wasn't expecting from a company like Uber.
  • Given an array of player ranks, and a defined set of rules for determining win/loss outcomes, write a function that outputs the final tournament result.

“The open-endedness threw me a bit.”

View Post

Uber·Frontend Engineer·Technical Phone Screen

Mar 2026
Uber frontend engineer coding screen, one question, nothing too wild. The more memorable part was realizing mid-interview that my interviewer seemed to be conducting the whole thing from bed.
  • Design a data structure that supports insert, delete, and getRandom in O(1) average time.

“Classic problem, I'd seen it before, but the O(1) getRandom part still takes a second to click.”

View Post