Uber at a glance
- After the screens
- 3 interviews × 60 min
- Phone screen
- 60 min: coding + design
- Coding assessment
- HackerRank
- Role guides
- 9 engineering specialties
The stages
- 1Recruiter30 min call
- 2AssessmentHackerRank coding
- 3Phone screenCoding + design, 60 min
- 4InterviewsCoding, depth, collaboration
- 5DecisionVirtual
Live interview time
- Phone screen60 min
- Algorithms & data structures60 min
- Depth in specialisation60 min
- Collaboration & leadership60 min
From Uber's backend and frontend engineering interview guides.
Uber publishes interview guides on its careers site for nine engineering specialties, from backend and frontend to mobile, data, ML and security. Uber says the process is the same shape across engineering roles; what changes is the expertise each specialty is tested on, and the scope expected as levels rise. This guide follows Uber's backend and frontend software engineering guides.
How the process runs
Step through: Uber's software engineering interviews
Step 1 of 7
Talk with a recruiter or sourcer (30 min, virtual)
Your background, the role and the business line you'd join.
Uber's guides name three competencies: Software Engineering, Design & Architecture, and Collaboration & Leadership. Uber says it uses competencies to make evidence-based hiring decisions, so every round is looking for evidence of one or more of them.
Uber also asks you to keep your scheduled slots: its engineering guide says rescheduling is limited and other slots may not be available.
The HackerRank assessment and phone screen
The assessment comes first, so treat it as a real interview. Practise in a timed, online editor until reading a problem, writing a solution and testing edge cases feels routine, because there's no interviewer to nudge you.
The 60-minute phone screen covers coding and design and architecture in one call. Plan for both: solve a problem cleanly, then expect to talk about how a piece of a system would be built. Keep your design answers grounded: what the components are, where the data lives, and what happens when traffic jumps.
Interview 1: Algorithms and data structures
A classic coding round. The usual toolkit applies: hash maps, heaps, sorting, two pointers, intervals, graphs and BFS/DFS. What sets a strong answer apart is the same everywhere:
- Clarify first. Ask about input sizes, duplicates and empty cases before writing code.
- Say the plan, then code it. A working simple solution plus a stated improvement beats an unfinished clever one.
- Test out loud. Walk through one normal case and one edge case before you say you're done.
Uber's frontend guide adds advice that suits every round: explain your reasoning clearly and challenge assumptions collaboratively.
Interview 2: Depth in specialisation
This is where the specialty guides matter. It's still a coding interview, but on your area: backend candidates should expect server-side problems, frontend candidates browser and UI work, mobile candidates Android or iOS. Read the guide for your specialty on Uber's engineering guide page before you prepare.
Uber's guides suggest thinking through real-world scenarios. Uber's product gives you plenty: matching riders to nearby drivers, live demand in a city, estimated arrival times, trip state that must survive an app crash. Practise turning one of these into a small piece of working code, then talking about what changes at real scale.
Quick check
In the depth-in-specialisation round, your solution works on the example. What's the strongest next step?
Practice questions (original)
Written in the spirit of a ride-hailing product. Each solution was tested against a brute-force version on thousands of random inputs.
Practice question
Nearest available drivers
mediumA rider is at point (x, y). You get a list of drivers as (driver_id, x, y, available). Return the ids of the k nearest available drivers, nearest first. Break ties by id. Straight-line distance is fine.
Practice question
Minutes online
easyA driver's online sessions are given as (start, end) in minutes. Sessions can overlap, for example when the app restarts or the driver uses two phones. Return the total number of minutes the driver was online, counting overlapping time once.
Practice question
Requests per zone, live
mediumBuild ZoneDemand(window) with record(zone, t) for a ride request in a zone at time t (seconds, never decreasing), and count(zone, now) for the number of requests in that zone in the last window seconds, meaning times in (now - window, now]. It should stay fast when it runs all day.
Interview 3: Collaboration and leadership
A 60-minute behavioural interview. Uber's interviewing tips say teams ask questions like "Tell me about a time when…" and "Describe how you have…", and assess both job-related competencies and Uber's values through your past experience.
Uber's engineering guides list seven success attributes. Prepare a true story that shows each, and expect follow-ups on the details:
Flip cards · 0 of 7 revealed
The prompts on the back of each card are Nokku's suggestions, not Uber's definitions; Uber's guides list the attribute names only.
How Uber suggests answering:
- Use STAR: Situation, Task, Action, Result.
- Prepare one or two examples per competency, and back up claims with concrete examples.
- Have an elevator pitch ready about yourself.
- Understand the role and its business line, and think about the day-to-day of the job.
- Pause if you need to gather your thoughts, and ask thoughtful questions at the end.
What one Uber engineer says
Uber's careers site also publishes engineers' own accounts of being hired. In one, a backend engineer describes their loop as three coding interviews, two design and architecture interviews and one collaboration and leadership interview, and prepared with algorithm practice, Uber's mock interview videos and the book Designing Data-Intensive Applications. That account differs from the current guide above, which is a good reminder that loops change by level and over time. Prepare for design and architecture whatever your level; the phone screen tests it either way.
Before a virtual interview
From Uber's tips: download and test Zoom beforehand, test your equipment, join early, and find a quiet, well-lit place with no distractions. Do this a few days ahead, not five minutes before.
A 4-week prep plan
Step through: Four weeks to interview-ready
Step 1 of 4
Week 1: Timed coding
One or two problems a day in a timed online editor, like the HackerRank assessment. Arrays, hash maps, sorting, intervals.
Keep going
- Practise patterns with the free DSA practice and its in-browser runner.
- Refresh a weak area with a free Nokku course.
- Show your impact on your resume with the free resume builder.
- Browse remote jobs and set up weekly alerts.
Sources
Checked on November 18, 2026. Hiring processes change, so confirm details with your recruiter.
- Uber Careers: Get interview ready
- Uber Careers: Engineering Interview Guide
- Uber Careers: Backend Engineering Interview Guide
- Uber Careers: Frontend Engineering Interview Guide
- Uber Careers: Interviewing tips
- Uber Careers: Landing the job at Uber, Backend Engineer (an engineer's account)
Nokku.ai is not affiliated with or endorsed by Uber. Company names are used only to describe their publicly documented hiring process. Practice questions are original.