Uber frontend interviews lean hard on async JavaScript: concurrency limits, task scheduling, timers, and queues, plus LeetCode-style DSA and a bar raiser round.
This guide is built from 38 Uber interview reports shared by FrontendLead members between November 2023 and May 2026, cross-checked against Uber’s official careers pages and engineering blog. You’ll learn how each round works, which topics each round tests, what strong answers look like, and a prep plan that maps every round to practice on FrontendLead.
The biggest pattern is clear: Uber keeps testing asynchronous control flow in plain JavaScript. Members were asked to write concurrency-limited async utilities, dependency-aware task scheduling, sequential UI queues, async caching, and timer logic. The exact prompts are in the members-only sections below. If you are fluent in these patterns and can explain the edge cases, you have covered the round that fails the most candidates.
By Shivam Bhalla · Updated
01Uber frontend interview at a glance
- Timeline
- About 3 to 6 weeks; one member went from online assessment to virtual onsite in under two weeks
- Process
- Recruiter call, online assessment or technical phone screen, virtual onsite, decision
- Onsite
- Usually 5 rounds of about 1 hour each, roughly 5 hours total
- Coding language
- Your choice; JavaScript or TypeScript for frontend rounds
- Frameworks
- React for UI rounds; many JavaScript rounds are framework-free
- Signature topic
- Async JavaScript: concurrency limits, dependency scheduling, timers, and queues
- DSA
- Expect at least one LeetCode medium (sometimes hard), even for frontend roles
- Special rounds
- Bar raiser and hiring manager rounds, both heavy on projects and behavior
- Leveling
- Members reported L4 (SWE II), L5 (Senior), and Senior II; confirm the target level with your recruiter
02Uber frontend interview process
Uber’s official hiring page describes a talent team call, a hiring manager conversation, a technical interview, and a team interview. Uber’s engineering blog adds that each interview is about an hour, with 30 to 40 minutes of real-world coding rather than brain teasers. Member reports fill in the frontend-specific details.
- 1
Recruiter call
20 to 30 minutesThe recruiter asks about your background, why Uber, why you are looking now, your most challenging project, and visa status. Uber’s blog recommends a short, specific pitch about your contribution, not the team’s. Ask the recruiter whether your screen is an online assessment, a JavaScript round, or a DSA round, because members got all three.
- 2
Online assessment (some roles)
35 to 70 minutes, CodeSignalSeveral members started with a CodeSignal assessment. One SWE II frontend candidate got two algorithm questions plus five or six frontend multiple-choice questions in about 35 minutes. Most described the frontend OA as simple. A backend-leaning OA had four progressive questions that ended in a stateful simulation.
- 3
Technical phone screen
About 60 minutesThis is the round with the most variety. Some members got a framework-free JavaScript problem on async control flow, caching, or stateful evaluation. Others got a React UI task with a mocked API. Others got a LeetCode medium on trees or intervals. One member spent the first 30 minutes being grilled on a past project before any coding. Uber’s blog says interviewers use CodeSignal during phone screens and usually run prepared test cases against your code.
- 4
Virtual onsite
About 5 hours, 5 roundsMost onsite reports list five rounds. A typical senior mix is one frontend coding round, one algorithms round, one or two system design rounds, a hiring manager round, and a bar raiser round. Some loops swap a system design round for a past-project deep dive. Uber’s blog says team interviews can include up to six back-to-back sessions.
- 5
Decision
A few days to 2 weeksRecruiters and the hiring team review results against the role’s criteria. One member heard back the same day after a strong onsite; another got a rejection about ten days later that cited the system design round. Uber says a recruiter walks you through the outcome, and some candidates received per-round feedback when they asked.
03How the Uber onsite loop is structured
Round names vary by team, but member reports converge on the same building blocks. Use this table to plan which skill each hour tests.
| Round | Typical focus | What it tests |
|---|---|---|
| Frontend coding | Interactive UI components and async utilities | Clean UI state, async logic, extending code as requirements grow |
| Algorithms | Grids, caches, tries, and selection problems | Standard DSA at medium to hard level, complexity analysis |
| System design | Productivity apps, media feeds, real-time location, streaming media, messaging | Component architecture, APIs, data model, performance |
| Hiring manager | Project deep dive with constant “why” follow-ups | Ownership, depth, testing practices |
| Bar raiser | Proud and not-so-proud projects, teaching exercise | Communication, judgment, raising the team’s bar |
Two things surprise frontend candidates. First, DSA is not optional: almost every loop included at least one pure algorithms round. Second, some loops include two system design rounds, one low-level (object-oriented design of a small game) and one high-level (a full product with endpoints and responses).
Members only
Coding rounds: questions Uber candidates were asked
10 real Uber interview questions
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
Members only
Async JavaScript: the round that decides Uber frontend loops
The exact Uber interview prompts
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
Members only
Algorithms rounds for Uber frontend roles
8 real Uber interview questions
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
Members only
Uber frontend system design questions
6 real Uber interview questions
Every prompt members reported, with the round, the level, and the follow-ups interviewers asked.
08Behavioral, hiring manager, and bar raiser rounds at Uber
Uber usually spends two of five onsite hours on non-coding rounds, and they carry real weight. Uber describes its Bar Raiser program as trained engineers who moderate the debrief and push the panel toward a consistent hiring decision.
Hiring manager round. Expect a project deep dive with constant interruptions: why this design, why not the alternative, how you tested it. One phone screen spent 30 minutes on a single project before coding. Pick a project where you made the key decisions and can defend each one.
Bar raiser round. Members were asked about a project they are proud of, one they are not proud of, and what they like about their current company. One bar raiser asked the candidate to teach a new concept in five minutes as if to a college student. Practice a short, jargon-free explanation of something you know well, such as how the browser renders a page.
Questions members reported:
- What is your most challenging project?
- Why are you looking for a new opportunity now?
- Tell me about a disagreement with a colleague and how you handled it.
- How do you test your frontend code?
- What do you know about autonomous vehicles? (asked in one loop)
Map stories to Uber’s values. Uber’s published cultural values include “Go get it,” “Trip obsessed,” “Build with heart,” “Stand for safety,” “See the forest and the trees,” “One Uber,” “Great minds don’t think alike,” and “Do the right thing. Period.” A strong story shows ownership and detail at the same time: you saw the big picture and fixed the specific thing that mattered.
“The page’s p95 load time was 6 seconds on low-end Android. I traced it to an unvirtualized list, shipped a fix behind a flag, and cut it to 2 seconds. Then I added a performance budget to CI so it wouldn’t regress.”
09What changes by level at Uber
Member reports cover L4 (SWE II) through Senior II. The rounds look similar, but the grading bar shifts. Confirm your target level with your recruiter.
| Signal | L4 / SWE II | L5 / Senior and above |
|---|---|---|
| Coding | Working async utility or UI component with clean state | Same, plus errors, cancellation, and the follow-up you predicted |
| Algorithms | Solve a medium with correct complexity | Solve quickly, optimize (O(n) to O(1)) without hints |
| System design | Clear components and API calls | Trade-offs across client, transport, caching, and backend |
| Projects | Explain your contribution clearly | Defend architecture under repeated “why” questions |
10How to prepare for the Uber frontend interview
Split your time three ways: async JavaScript, LeetCode-style DSA, and system design. Candidates who over-index on React UI and skip DSA are the ones who report failing screens.
Three-week plan
| Days | Focus | Practice |
|---|---|---|
| 1 to 3 | Concurrency limits and ordering | Async Map with Limit, Settled Pool Map |
| 4 to 5 | Task runners and dependencies | Task Dependency Order, Sequential Installer Steps |
| 6 to 7 | Timers, caching, and memoization | Fake Timer, Expiring Storage, Memoize II |
| 8 to 10 | React UI rounds | Progress Bar, Nested Comments I, File Navigation |
| 11 to 14 | DSA mediums | Intervals, heaps, tries, grids, and caches |
| 15 to 18 | System design | Spreadsheet, Pinterest, Uber |
| 19 to 20 | Behavioral and projects | One deep-dive project, a proud and a not-so-proud story, a 5-minute teaching pitch |
| 21 | Mock onsite | Three timed 60-minute sessions back to back |
Uber’s own interviewers recommend reading every prep document your recruiter sends, and its blog suggests timing practice problems to about 30 minutes. Browse all coding questions, or use the study plans to turn your interview date into a daily schedule.
11Uber frontend interview FAQ
How long is the Uber frontend interview process?
Usually three to six weeks. One member applied in May, heard from a recruiter in mid-July, took the online assessment at the end of July, and had a virtual onsite on August 3, with a decision ten days later. Timelines vary by team and recruiter load.
Does Uber ask LeetCode questions for frontend roles?
Yes. Most onsite reports include at least one pure algorithms round, and some phone screens are DSA only. Members reported mediums on intervals, grids, caches, and tries, with occasional hards.
What JavaScript questions does Uber ask?
Async control flow dominates: concurrency limits, dependency scheduling, async memoization and caching, event handling, and timers. One new grad also got a classic scoping question. The exact prompts are in the members-only sections above.
How many rounds are in the Uber frontend onsite?
Members consistently reported five rounds of about an hour each: typically frontend coding, algorithms, one or two system design rounds, a hiring manager round, and a bar raiser round. Uber’s blog says team interviews can include up to six sessions.
What is the bar raiser round at Uber?
A behavioral and project round with a trained interviewer who also moderates the hiring debrief. Members were asked about proud and not-so-proud projects, and in one case to teach a new concept in five minutes.
Can I use React in Uber frontend interviews?
Yes for UI rounds. Many JavaScript rounds are framework-free, and Uber’s blog says you can generally choose your language. Confirm the format with your recruiter.
Is the Uber online assessment hard?
Frontend members described the CodeSignal assessment as fairly simple: two algorithm questions, sometimes with a few frontend multiple-choice questions, in about 35 minutes. The phone screen and onsite are where most candidates struggle.
Real Uber questions and reports
Verified Uber questions
Candidate interview reports
- Uber - Frontend Interview
- Uber - Senior Frontend Engineer - Phone Screen
- Uber - SWE interview
- Uber - L5 - PhoneScreen
- Uber-SR full stack - Phone screen
- Uber-SR full stack-HR
- Uber SDE2 Technical Round
- Uber frontend interview experience - 2025
- Uber Interview Experience Full
- Uber - Senior Frontend Engineer - Onsite Interview