An Uber mock interview on Devana is a voice interview with an AI interviewer on one of 39 Uber-style questions from Devana's bank: 12 coding, 9 system design, 11 technical deep dives and 7 behavioral. Your code runs, the interviewer asks follow-ups, and you get a score out of 100. Company question sets are on the Free plan. Devana is not affiliated with Uber, and these are not leaked or confirmed Uber questions.
For the stages and their sources, read the Uber interview process.
What the Uber software engineer interview looks like
Uber's How we hire page lists its steps: apply, talk with the talent team, chat with the hiring manager, a technical interview for technical roles, a functional exercise or assessment on some roles, a team interview, and a decision. In the technical interview you may work through a shared problem or real scenario with an interviewer, collaboratively and in real time. It states no timeline or round lengths.
Accounts from its own engineers on its careers site add detail. A backend engineer describes a recruiter screen, three coding interviews, two design and architecture interviews and one on collaboration and leadership; a senior front-end engineer describes a code assessment, algorithms and data structures, a web specialization interview, system design and a hiring manager discussion. Those are individual experiences, so expect yours to vary by role and level.
The full guide, with the sources, is the Uber software engineer interview process.
What Devana practices for Uber
Devana's Uber set has 39 questions, 24 of them rated hard. The topics that come up most are Scalability, Systems Design, Graphs and Databases. They are Devana's own questions, written to reflect what Uber and its candidates have said publicly about its interviews. Start any of these as a mock interview:
| Round type | Questions | Examples (start a mock interview) |
|---|---|---|
| Coding | 12 | |
| System design | 9 | |
| Technical deep dives | 11 | |
| Behavioral | 7 |
Counted from Devana's question bank. Technical deep dives run as a system design round. Devana is not affiliated with Uber.
How to practice for Uber
- Say the trade-off before the code. The coding set includes matching a rider to a driver, where the nearest driver is not automatically right, and computing a surge multiplier. Uber says it cares as much about how you solve problems as the solution itself, and Josh asks why you chose what you chose.
- Design for the marketplace. The designs are the dispatch system, real-time location tracking, the pricing service and the trip lifecycle. Say what happens to each side of the market when part of the system is slow.
- Know what breaks on the road. The technical deep dives include building for an unreliable connection, battery and data on a driver's phone, why an ETA is wrong, and deploying to a system with no quiet period.
- Bring stories about pressure. The behavioral set asks about deciding fast with incomplete information, an outage you were responsible for, and pushing back on something you thought was wrong.
How to set up an Uber mock interview
- Open the Uber set. The "Start a free Uber mock interview" button opens Devana's question bank filtered to Uber.
- Choose the round. Filter by type: coding, system design, technical deep dive or behavioral. A technical deep dive runs as a system design round, with a whiteboard.
- Choose the level. Filter by difficulty: the company sets are rated medium or hard. 24 of the 39 Uber questions are rated hard. You can also filter by topic.
- Start it. Press "Practice this question" and the voice interview starts on that question. Signed out, you are asked to sign in first; the Free plan needs no card.
- Role and style. A question from a company set uses your saved interviewer style and coding language from Settings. To choose your role, such as frontend or backend, and run a full two-problem round, start a standard interview from Practice instead; that setup cannot be pointed at one company.
How an Uber mock interview runs on Devana
Pick a question from the Uber set and you talk it through with Josh, Devana's AI interviewer, for up to 30 minutes on a paid plan (45 for a design question) or 20 on the Free plan. In a coding question your code runs in Python, JavaScript, TypeScript, Java or C++; a design question has a whiteboard the interviewer reads; a behavioral question gets follow-ups about what you personally did. Each session ends with a score out of 100 on that round's rubric and a list of what raised and lowered it. For a full-length round with two problems, start a standard mock interview from Practice instead: up to 60 minutes on a paid plan, though you cannot choose the company. The mock interviews by round page shows each round type.
Guides to study first
- Graphs, for road networks and routing
- Heaps, for picking the best candidates quickly
- Sharding and replication, for sharding by geography
- Message queues and async work, for streams of driver locations
- Ambiguity and changing priorities, for deciding with incomplete information
- Failure and mistakes, for the outage you were responsible for
Devana is not affiliated with, sponsored by or endorsed by Uber. The questions are Devana's own and are not leaked or confirmed Uber interview questions.
Frequently asked questions
Are Devana's Uber questions real Uber interview questions?
No. Devana's 39 Uber questions are its own, written to reflect what Uber and its candidates have said publicly about its interviews. They are not leaked or confirmed Uber questions, and Devana is not affiliated with Uber.
Can I do an Uber mock interview for free?
Yes. Company question sets are on Devana's Free plan, which includes 3 mock interviews a month of up to 20 minutes each, on any of the 39 Uber questions. On the Sprint Pass or Pro, a single question runs up to 30 minutes, or 45 for a system design question.
What does Uber's technical interview involve?
Uber's How we hire page says you may work through a shared problem or real scenario with an interviewer, collaboratively and in real time, and that it cares as much about how you solve problems as the solution itself. Practice talking through your plan before you code, and checking it with the interviewer.