Public preview and process notes

Uber Frontend Interview Questions and Process

Uber publishes its frontend interview loop on its careers site. This page sets those steps beside what candidates reported between 2018 and 2026, round by round, then lists the questions they were asked; the poll widget reported in 2025 and 2026 is open to every reader.

30 reported questionsFrontendAtlas practice set: Coding 1 · Concepts 4Full practice set requires Premium

Editorial practice groupings, not verified official interview questions or endorsements.

Uber’s frontend engineering interview guide, linked below, covers levels L3 to L6+ and says the steps may vary by role, location and business needs; a senior engineer based in Chile describes his own loop on the same careers site. The rest comes from candidates: LeetCode posts from 2021 to 2026, a 2022 Medium account of a frontend loop that brought an offer, Taro accounts from Bengaluru (2018 and 2022) and Brazil (2025), and two full-stack loops, on Medium in 2024 and LeetCode in 2026, used only for their frontend, algorithm and behavioural questions. Four accounts place the candidate in India and one in Brazil; the others do not say where.

What public interview reports describe

The official loop and what candidates met

The guide describes a 30-minute call with a recruiter or sourcer, a HackerRank coding assessment, a 60-minute online phone screen on coding plus design and architecture, then three 60-minute interviews: algorithms and data structures, depth in specialization, and collaboration and leadership. The senior engineer’s story and the accounts that describe the onsite also have a separate design round.

  • Accounts from 2021 and 2022 name CodeSignal rather than HackerRank: a 2021 phone screen in its sandbox, a 2022 senior screen, and a 35-minute test in 2022 of two algorithm questions and eight multiple-choice questions, mostly on what JavaScript and CSS code outputs. See the assessment stage
  • The phone screen was a UI build (in any framework, in React or on CodeSignal), a JavaScript utility, or algorithm and JavaScript questions. A 2022 interviewer did not expect a working solution, and a 2025 India screen decided within ten minutes whether the other four rounds ran the same day. See the phone screen stage
  • The specialization round was a UI build or a JavaScript problem: vanilla JavaScript in a 2022 loop and, at the interviewer’s request, in a 2025 India loop; React with MDN open in a 2025 L5A loop. The 2022 Medium account, whose loop brought an offer, says Uber scored the two coding rounds together before the design and hiring manager rounds, and the 2025 L5A account says both had to be passed.
  • Recruiter labels can differ from what a round holds: a 2025 candidate whom HR told to expect an algorithms round got something else, and a 2026 candidate, after recruiters and Uber’s documents pointed to algorithms, got the poll widget. In a 2025 India loop the recruiter said a strong hire from the hiring manager was needed to move forward.

Round decoder

The Uber depth in specialization round: a UI build or a JavaScript problem

Uber’s frontend guide lists it as Interview 2, Software Engineering: Depth in Specialization (Coding 2), a 60-minute interview that follows the algorithms interview; the senior engineer’s story on Uber’s site calls it Specialization (Web). Candidates describe one UI build or one JavaScript problem in the hour, and two loops asked for vanilla JavaScript.

A 2025 candidate called it the riskiest interview of the loop because it can be either kind, and got a JavaScript problem after preparing a UI build. A 2022 candidate who received an offer and a 2025 L5A candidate say the two coding rounds decide whether the design and hiring manager rounds go ahead.

Position in the loop
Interview 2 of the three after the phone screen in the official guide. A 2022 Medium loop and a 2025 L5A loop had it as the second of two coding rounds that decided whether the design and hiring manager rounds went ahead; a 2022 Bengaluru loop and a 2025 loop held it after the design round.
What you build
A UI component or small app, or a JavaScript problem. A 2022 round tested DOM manipulation and asynchronous code in vanilla JavaScript; a 2025 L5A round was a React build.
Framework
Vanilla JavaScript in a 2022 loop and, at the interviewer’s request, in a 2025 India loop; any framework or vanilla JavaScript in a 2022 Bengaluru loop; React in the 2025 L5A loop in Bangalore.
What you may look up
MDN documentation in the 2025 L5A loop; in another 2025 loop the interviewer let the candidate search the web during a JavaScript problem.
What the interviewer looks for
Modular, functional JavaScript, DOM manipulation, ES6 and problem solving, in the 2022 Medium loop that brought an offer.
Sources
Uber’s frontend guide and the engineer’s story, a 2022 Medium account, a 2022 Taro account from Bengaluru and LeetCode posts from 2025; the page’s closing sources list links each of them.

Reported interview process

Uber frontend interview process

Uber's frontend interview guide lists a 30-minute recruiter call, a HackerRank assessment and a 60-minute phone screen on coding plus design and architecture, then three 60-minute interviews: algorithms and data structures, depth in specialization, and collaboration and leadership. Candidate accounts from 2018 to 2026 fill in the rounds, and every one that describes the onsite adds a separate design round.

Three accounts from 2021 and 2022 name CodeSignal rather than HackerRank; a 2025 candidate told by HR to expect an algorithms round got something else, and a 2026 candidate says recruiters often point to algorithms when rounds hold other tasks. The guide says steps may vary by role, location and business needs. The question list also keeps the frontend, algorithm and behavioural questions of two full-stack loops, from 2024 and 2026. Sources last checked Nov 2026.

Frontend engineers, L3 to L5A

StageWhat happensWhoReported by
Recruiter call 2 reported questions Virtual and 30 minutes with a recruiter or sourcer in the official guide. A 2022 Bengaluru recruiter explained the role and the rounds and asked about experience and the reasons for joining Uber; a short 2025 HR call in Brazil covered backend experience and knowledge, and a few CSS questions. Frontend engineers, L3 to L5AOfficial page and 2 reportsNewest: Frontend developer, Brazil · Oct 2025
Online assessment 2 reported questions A HackerRank coding assessment in the official guide, which gives no length or content. In a 2022 loop it was a 35-minute CodeSignal test of two algorithm questions and eight multiple-choice questions, mostly on what JavaScript and CSS code outputs; a senior engineer's story on Uber's careers site describes a small challenge in vanilla JavaScript. Practice: Valid ParenthesesFrontend engineers, L3 to L5AOfficial page and one reportNewest: Software engineer II (frontend) · Nov 2022
Phone screen 8 reported questions 60 minutes online in the official guide, on coding plus design and architecture. Candidates from 2021 to 2025 got a UI build (on CodeSignal in 2021, in React in 2022, in any framework in 2025 for the poll widget that opens the question list), a JavaScript utility on CodeSignal in a 2022 senior screen, or algorithm and JavaScript questions in 2025 loops. The 2022 senior interviewer did not expect a working solution, and in a 2025 India loop this round decided within ten minutes whether the other four ran the same day. Practice: React fetch and render a listFrontend engineers, L3 to L5AOfficial page and 6 reportsNewest: Front end software engineer II · Nov 2025
Algorithms and data structures 8 reported questions 60 minutes in the official guide, as Interview 1 (Coding 1). A senior engineer's story on Uber's site says any language is allowed. Each account from 2022 to 2025 that describes it had one problem for the hour, medium to hard in a 2022 loop that only had to pass a few test cases; a 2022 Bengaluru account calls it the bar raiser round. In a 2025 India loop the round labelled problem solving held a JavaScript question instead, and a 2025 candidate whom HR told to expect a DSA round got something else. Practice: Build a tree from a flat listFrontend engineers, L3 to L5AOfficial page and 6 reportsNewest: Front end software engineer II · Nov 2025
Frontend specialization 6 reported questions 60 minutes in the official guide, as Interview 2: depth in specialization (Coding 2). Candidates from 2022 to 2025 got a UI build or a JavaScript problem: machine coding in vanilla JavaScript on DOM manipulation and asynchronous code in 2022, a UI component in any framework or vanilla JavaScript in a 2022 Bengaluru loop, vanilla JavaScript at the interviewer's request in a 2025 India loop and a React build with MDN open in a 2025 L5A loop. A 2025 candidate who prepared for a UI build got a JavaScript problem and was allowed to search the web. Practice: Todo list with local stateFrontend engineers, L3 to L5AOfficial page and 5 reportsNewest: Front end software engineer II · Nov 2025
System design 3 reported questions A separate design round in every account that describes the onsite; the official guide has none after the screen. Where the 2022 and 2025 accounts give a length it is an hour on one product: requirements first, then component architecture, API design and data flow, data models, client storage and performance, on a CodeSignal whiteboard in 2022. Its place varies: after both coding rounds had been passed in a 2022 Medium loop and a 2025 L5A loop, first in a 2022 Bengaluru loop, where it opened with a project the candidate was proud of. Practice: Frontend system design blueprintMid and senior levelsOfficial page and 5 reportsNewest: Front end software engineer II · Nov 2025
Collaboration and leadership 60 minutes in the official guide, as Interview 3: collaboration and leadership. Accounts call it the leadership and collaboration, behavioural or hiring manager round: situations in which you applied Uber's values in the 2022 Medium loop, which brought an offer, past projects and work experience in 2022 and 2025 loops, and a walkthrough of previous projects over 1 hour 45 minutes in a 2025 L5A loop. In a 2025 India loop the recruiter said only a strong hire from the hiring manager would have moved the candidate forward. Practice: Behavioral interview guideFrontend engineers, L3 to L5AOfficial page and 5 reportsNewest: Front end software engineer II · Nov 2025

1 more reported question comes from sources that do not name the round.

Online assessment: try Valid Parentheses now, a free task we picked for this round.

Start the free task

Questions from Uber reports

30 questions candidates reported

The first question is open to read; its answer outline opens with a free account. The others show their topic and what is behind the lock; Premium opens all 29 still locked.

Newest account Apr 2026

Locked questions are Premium, but you can open one free with an account: one per account, across all company guides.

  1. 1

    Real-time poll widget

    Open

    In a 2025 L4 screening round, build a voting poll in React or another framework: four options, each a button; a click adds a vote, and every option's share of the votes updates at once, drawn as a coloured bar that moves smoothly as votes come in. A 2026 L5A candidate, who calls it the famous poll widget question, was then asked to make the options dynamic, entered through a form input.

    Phone screenUI buildFrontend engineer (L5A) · Reported in 2 accounts · Apr 2026

  2. 2

    CSS position values

    Premium

    Recruiter callWeb fundamentalsFrontend developer, Brazil · Reported in 1 account · Oct 2025

    Behind the lock: the question only. Its practice task is free for everyone.

  3. 3

    Display none versus hidden

    Premium

    Recruiter callWeb fundamentalsFrontend developer, Brazil · Reported in 1 account · Oct 2025

    Behind the lock: the question only. Its practice task is free for everyone.

  4. 4

    Sliding window over a string

    Premium

    Online assessmentAlgorithmSoftware engineer II (frontend) · Reported in 1 account · Nov 2022

    Behind the lock: the accounts' description (they do not share the prompt) and a Premium practice task.

  5. 5

    Digit manipulation

    Premium

    Online assessmentAlgorithmSoftware engineer II (frontend) · Reported in 1 account · Nov 2022

    Behind the lock: the accounts' description (they do not share the prompt) only.

  6. 6

    Concurrency-limited async map

    Premium

    Phone screenJavaScriptSenior front end engineer · Reported in 1 account · Aug 2022

    Behind the lock: the question and a Premium practice task.

  7. 7

    Progress bars added on click

    Premium

    Phone screenUI buildFront end candidate · Reported in 1 account · Feb 2021

    Behind the lock: the question only.

  8. 8

    Kth lowest elements of an array

    Premium

    Phone screenAlgorithmFront end software engineer II · Reported in 1 account · Nov 2025

    Behind the lock: the question only.

  9. 9

    Memoizing async functions

    Premium

    Phone screenJavaScriptSDE 2 (full-stack) · Reported in 1 account · Nov 2024

    Behind the lock: the question and a Premium practice task.

  10. 10

    Priority queue problem

    Premium

    Phone screenAlgorithmSDE 2 (frontend), India · Reported in 1 account · Jun 2025

    Behind the lock: the accounts' description (they do not share the prompt) only.

  11. 11

    Currying

    Premium

    Phone screenJavaScriptSDE 2 (frontend), India · Reported in 1 account · Jun 2025

    Behind the lock: the accounts' description (they do not share the prompt) and a Premium practice task.

  12. 12

    React performance

    Premium

    Phone screenReact conceptsFrontend engineer II, India · Reported in 1 account · Apr 2022

    Behind the lock: the accounts' description (they do not share the prompt) only.

  13. 13

    Method chaining over a promise queue

    Premium

    Algorithms and data structuresJavaScriptSDE 2 (frontend), India · Reported in 1 account · Jun 2025

    Behind the lock: the question only.

  14. 14

    Earliest meeting time of moving objects

    Premium

    Algorithms and data structuresAlgorithmSoftware engineer II (frontend) · Reported in 1 account · Nov 2022

    Behind the lock: the question only.

  15. 15

    Task order from dependencies

    Premium

    Algorithms and data structuresAlgorithmFrontend engineer II, India · Reported in 1 account · Apr 2022

    Behind the lock: the question only.

  16. 16

    Number of Islands II

    Premium

    Algorithms and data structuresAlgorithmFront end software engineer II · Reported in 1 account · Nov 2025

    Behind the lock: the question only.

  17. 17

    Median of a data stream

    Premium

    Algorithms and data structuresAlgorithmSDE 2 (full-stack) · Reported in 1 account · Nov 2024

    Behind the lock: the question only.

  18. 18

    Grid distances from parked cars

    Premium

    Algorithms and data structuresAlgorithmSDE 2 (full-stack) · Reported in 1 account · Nov 2024

    Behind the lock: the question only.

  19. 19

    Largest plus sign in a grid

    Premium

    Algorithms and data structuresAlgorithmFrontend engineer (L5A), India · Reported in 1 account · Sep 2025

    Behind the lock: the accounts' description (they do not share the prompt) only.

  20. 20

    Course Schedule II variant

    Premium

    Algorithms and data structuresAlgorithmSDE 2 (full-stack) · Reported in 1 account · Jan 2026

    Behind the lock: the accounts' description (they do not share the prompt) only.

  21. 21

    Memory game

    Premium

    Frontend specializationUI buildSDE 2 (frontend), India · Reported in 1 account · Jun 2025

    Behind the lock: the question only.

  22. 22

    Jira-style drag and drop

    Premium

    Frontend specializationReact buildFrontend engineer (L5A), India · Reported in 1 account · Sep 2025

    Behind the lock: the question only.

  23. 24

    Connect Four game

    Premium

    Frontend specializationUI buildSDE 2 (full-stack) · Reported in 1 account · Jan 2026

    Behind the lock: the question only.

  24. 25

    Sequential click binding

    Premium

    Frontend specializationJavaScriptSoftware engineer II (frontend) · Reported in 1 account · Nov 2022

    Behind the lock: the accounts' description (they do not share the prompt) only.

  25. 26

    Graph of async jobs

    Premium

    Frontend specializationJavaScriptFront end software engineer II · Reported in 1 account · Nov 2025

    Behind the lock: the accounts' description (they do not share the prompt) only.

  26. 27

    Google Calendar design

    Premium

    System designFrontend system designFront end software engineer II · Reported in 2 accounts · Nov 2025

    Behind the lock: the question only.

  27. 28

    Collaborative calendar design

    Premium

    System designFrontend system designSoftware engineer II (frontend) · Reported in 1 account · Nov 2022

    Behind the lock: the question only.

  28. 29

    Config-driven UI widget builder

    Premium

    System designFrontend system designFrontend engineer (L5A), India · Reported in 1 account · Sep 2025

    Behind the lock: the question only.

  29. 30

    Task scheduler with a concurrency limit

    Premium

    Round not statedJavaScriptSoftware engineer II (frontend), India · Reported in 1 account · Oct 2018

    Behind the lock: the question only.

Behavioural questions candidates were asked

Open to everyone: 9 questions from 7 public sources.

  • Tell me about yourself.Reported in 1 account · Feb 2021
  • Why do you want to join Uber?Reported in 1 account · Apr 2022
  • Walk through the projects you have worked on.Reported in 4 accounts · Sep 2025
  • Talk about a project you are proud of, and about things in your work you are not proud of.Reported in 1 account · Apr 2022
  • Tell me about a particularly interesting project or situation.Reported in 1 account · Apr 2022
  • Describe situations in which you applied Uber's values; the recruiter had named a challenging project, resolving a conflict in the team and leadership among the likely topics.Reported in 1 account · Nov 2022
  • Tell me about a conflict with a team member or a product manager.Reported in 1 account · Jan 2026
  • Talk about projects you worked on with others, and projects you took from start to finish.Reported in 1 account · Jan 2026
  • What did you do when you pushed a bug to production that broke the system, and how did your team react?Reported in 1 account · Nov 2024

How to prepare with this grouping

Rehearse the screen, then the specialization round

Uber’s accounts differ most in the screen and the specialization round: a UI build in one loop, a JavaScript problem or an algorithm in the next, and vanilla JavaScript whenever the interviewer asks for it. The free tasks rehearse each of those shapes; the Premium case is for the separate design round that mid-level and senior accounts describe.

  1. Free now
    Fetch and render a list with loading, error and empty states

    For screens like the 2022 Bengaluru one, which asked for a UI component in React: one component with every request state, finished and talked through within the hour.

  2. Free now
    Build a dropdown as a JavaScript class, then port it to React

    Specialization rounds in 2022 and 2025 asked for vanilla JavaScript, and a 2025 L5A round for React: build the widget without a framework first, then port it.

  3. Free now
    Retry a promise-returning function with delay

    Promises and timers without a UI, for the JavaScript problems candidates reported from 2018 to 2025.

  4. Free now
    Valid Parentheses

    A short algorithm in JavaScript: a 2025 candidate with four years of React called it a mistake not to have practised LeetCode-style problems in JavaScript before the specialization round.

  5. Premium
    Design a real-time messaging inbox

    For the hour-long design round: requirements, components, API and data flow, data models, client storage and performance, the areas the 2022 and 2025 accounts were questioned on, on a product none of them reports.

Published by Uber

Official preparation pages from Uber

Uber publishes these pages itself. They describe the process and expectations in the company's own words; they are not a list of the questions you will be asked, and FrontendAtlas is not affiliated with Uber.

PageWhat it coversChecked
Frontend Engineering Interview GuideA recruiter conversation, a HackerRank assessment, a 60-minute technical phone screen on coding and design, then three 60-minute interviews: algorithms and data structures, depth in specialisation, and collaboration and leadership.Oct 2026
Landing the job at Uber: Front-End EngineerAn Uber engineer's account of the loop: a vanilla JavaScript assessment, algorithms, web specialisation, system design and a hiring manager conversation, with advice to cap practice problems at 20 minutes.Oct 2026
Get interview readyThe hub that links the Uber interview guides; its Engineering Interview Guide links the frontend, backend, data and iOS guides.Oct 2026

Preparation FAQ

Common questions about Uber frontend interviews

Is design a separate round?

The guide folds design and architecture into the phone screen and lists no design interview after it. The senior engineer’s story on Uber’s site and the accounts that describe the onsite have a separate design round, an hour long where the 2022 and 2025 accounts give its length.

Do recruiter labels match the rounds?

Not reliably. A 2025 candidate whom HR told to expect an algorithms round got something else, a 2026 candidate got the poll widget after recruiters and Uber’s documents pointed to algorithms, and a 2025 candidate who prepared a UI build for the specialization round got a JavaScript problem. The 2026 candidate’s advice is to be ready for JavaScript and asynchronous code, React, and a medium algorithm with a hard follow-up in any round.

Which language should I use?

The senior engineer’s story on Uber’s site says the algorithms interview accepts any language. Two specialization rounds asked for vanilla JavaScript, and a 2025 candidate with four years of React called it a mistake to arrive at that round without LeetCode-style practice in JavaScript.

Try free challenge View pricing

Sources (16)

The links open with a free account. Create a free accountSign in

Each candidate's account describes one loop, not a fixed format.

  • Uber: Frontend engineering interview guide

    An official page read for the process table, where it describes the Recruiter call, Online assessment, Phone screen, Algorithms and data structures, Frontend specialization and Collaboration and leadership. Process context, not interview content.

  • Taro account, around April 2022

    Frontend engineer II, India · Apr 2022

    A public account read for the process table, where it describes the Recruiter call, Phone screen, Algorithms and data structures, Frontend specialization, System design and Collaboration and leadership.

  • Taro account, October 2025

    Frontend developer, Brazil · Oct 2025

    A public account read for the process table, where it describes the Recruiter call.

  • Uber: Landing the job as a front end engineer

    An official page read for the process table, where it describes the Online assessment, Algorithms and data structures, Frontend specialization, System design and Collaboration and leadership. Process context, not interview content.

  • Medium account, November 2022

    Software engineer II (frontend) · Nov 2022

    A public account read for the process table, where it describes the Online assessment, Algorithms and data structures, Frontend specialization, System design and Collaboration and leadership.

  • LeetCode account, February 2021

    Front end candidate · Feb 2021

    A public account read for the process table, where it describes the Phone screen.

  • LeetCode account, August 2022

    Senior front end engineer · Aug 2022

    A public account read for the process table, where it describes the Phone screen.

  • LeetCode account, June 2025

    SDE 2 (frontend), India · Jun 2025

    A public account read for the process table, where it describes the Phone screen, Algorithms and data structures, Frontend specialization, System design and Collaboration and leadership.

  • LeetCode account, November 2025

    Front end software engineer II · Nov 2025

    A public account read for the process table, where it describes the Phone screen, Algorithms and data structures, Frontend specialization, System design and Collaboration and leadership.

  • LeetCode account, October 2025

    Frontend engineer (L4) · Oct 2025

    A public account read for the process table, where it describes the Phone screen.

  • LeetCode account, September 2025

    Frontend engineer (L5A), India · Sep 2025

    A public account read for the process table, where it describes the Algorithms and data structures, Frontend specialization, System design and Collaboration and leadership.

  • LeetCode account, June 2025

    SDE II (frontend) · Jun 2025

    A public account read for the process table, where it describes the Algorithms and data structures.

  • LeetCode account, April 2026

    Frontend engineer (L5A) · Apr 2026

    A public account read for one reported question from the phone screen.

  • Medium account, November 2024

    SDE 2 (full-stack) · Nov 2024

    A public account read for four reported questions from the phone screen, algorithms and data structures and frontend specialization and two behavioural questions.

  • LeetCode account, January 2026

    SDE 2 (full-stack) · Jan 2026

    A public account read for two reported questions from the algorithms and data structures and frontend specialization and two behavioural questions.

  • Taro account, around October 2018

    Software engineer II (frontend), India · Oct 2018

    A public account read for one reported question.