Table of contents

• Where do I apply for an Uber interview?
• What topics should I study for?
• What are some example Uber technical questions?
• What are some example Uber behavioral questions?
• How long is the entire Uber interview process?
• What is the Uber interview like for a full time software engineering role?
• What are the levels and salary for a software engineer at Uber?
• How should I prepare?

Where do I apply for an Uber interview?

Start on the Uber careers site and filter by engineering. You can also use this LinkedIn strategy to get your resume in front of a recruiter directly.

Uber hires into specific orgs like Mobility, Delivery, Grocery, and Freight. If one of those products means something to you, say so on the recruiter call. The recruiter uses that first conversation to decide what your onsite should lean toward, so it's worth being clear about what you want to work on.

What topics should I study for?

• Graph traversal. Uber loves grid and map problems, which makes sense for a company built on maps.
  • Depth first search
  • Breadth first search
  • Union-find comes up a lot in candidate reports, so learn it even though most prep lists skip it.
• Sliding window
• Intervals (scheduling and booking problems)
• Dictionaries and string parsing
• Heaps
• Modified binary search
• Dynamic programming
• Time/space analysis
• System design, especially real-time and location-based systems

Most questions land at LeetCode medium, but candidates regularly report a hard one in the mix. Uber also cares a lot about whether your code actually runs. Uber runs its coding rounds in CodeSignal, where you can execute your code, so practice writing solutions you can test yourself instead of pseudocode you talk through.

What are some example Uber technical questions?

These all come from candidate reports in 2025 and 2026.

• Count delivery zones: group open restaurants on a grid into clusters.
• Assign meetings to rooms so nothing overlaps, using as few rooms as possible.
• Find the longest stretch of a list where the gap between the biggest and smallest number stays under a limit. (One candidate got this framed as driver and cab data.)
• Two players take turns picking a number from either end of a row. What's the best score the first player can guarantee?
• 0/1 knapsack: pick items to fit a capacity and maximize value.
• What's the fewest characters you can add to the end of a string to make it a palindrome?
• Find the closest palindrome to a given number.
• Build a tiny file system that supports mkdir, cd, ls, and pwd.
• Implement Promise.all() in JavaScript. (Frontend roles)
• Design Splitwise.
• Design a food delivery app.
• Design the shopping cart for a grocery delivery service.
• How would you add parking features to a maps app?

Expect the system design round to push on the stuff Uber deals with every day: location data, spreading load across servers, and events flowing between services in real time.

What are some example Uber behavioral questions?

• Tell me about yourself.
• Tell me about a time you disagreed with your manager.
• Tell me about a time you had to deliver under a tight deadline.
• How do you work with your team, and how do you handle stressful stretches?
• Walk me through a project you're proud of. What would you change about it now?
• Why Uber?

Uber's cultural values include "Go get it," "Trip obsessed," "Build with heart," and "Stand for safety." You don't need to quote them. You do need stories where you owned something and can point to a number that changed because of your work. Hiring managers at Uber ask for impact, and "it went well" won't cut it.

How long is the entire Uber interview process?

Plan on four to six weeks from the recruiter call to an offer. It can stretch longer if you pass the onsite and then need to match with a team. If you have a deadline from another company, tell your recruiter early. It gives them a chance to schedule your rounds sooner.

What is the Uber interview like for a full time software engineering role?

Recruiter call (30-45 minutes)

Your background, why Uber, which orgs interest you, location, and compensation expectations.

Online assessment (about 70-90 minutes)

A timed CodeSignal test, usually four problems that get harder as you go. The first couple are easy array and string questions, and the last one is often a graph or DP problem. You don't need a perfect score to move on. New grads and interns usually get this step. Experienced hires sometimes skip it and go straight to the phone screen, so ask your recruiter whether it applies to you.

Technical phone screen (about 1 hour)

Live coding with an Uber engineer in CodeSignal. It's usually one or two algorithm problems, and the interviewer will want to see your code run on real inputs.

Onsite (4-5 rounds, usually virtual, around 4-5 hours total)

• Coding (1 hour). Standard data structures and algorithms in CodeSignal.
• Second coding round (1 hour). This one goes deeper into your specialty. For backend roles it's sometimes a "machine coding" round where you build a small working system, like the file system question above. For mobile or frontend roles it'll be in that stack.
• System design (1 hour). How deep it goes depends on your level. Senior candidates may also get a technical retrospective, where you walk through the architecture of something you actually built.
• Collaboration and leadership (about 75 minutes). The hiring manager leads it, and it mixes questions about your past work with "what would you do if" scenarios.
• Bar raiser (1 hour). A senior engineer from outside the team runs this one. Candidates report very different versions of it. Some got a hard coding problem with nonstop follow-ups. Some spent the full hour being grilled on one project from their resume. Others described it as a relaxed conversation. Treat it as the most important round of the day, because it often is.

After the onsite, the whole panel meets to decide. The goal is a unanimous call, so one weak round can sink an otherwise good day. That's the main reason to prepare evenly for every round and not just the coding ones.

What are the levels and salary for a software engineer at Uber?

*Note that compensation varies based on location. These estimates are likely based on the USA HCOL market.

Those are medians across US offices. Your actual number depends a lot on where you're based and how your level comes out of the onsite. If you have a competing offer, share it with your recruiter before they send the final package.

How should I prepare?

Get comfortable in CodeSignal before your assessment. It feels different from LeetCode, and the clock is tight when you have four problems. Then drill graphs and grids until problems like counting islands feel routine, and add union-find to your list. For the onsite, pick one project you know inside and out and practice explaining the tough calls you made on it, since the bar raiser might spend the whole hour there. If you're just getting started, read how to prepare for a technical interview and keep the cheat sheets open while you practice.