Uber's loop is structured and takes three to six weeks. It usually runs a recruiter screen, an optional online assessment (CodeSignal or HackerRank), a hiring-manager conversation, a technical phone screen, and a virtual onsite of four to six rounds.
The onsite typically includes two coding rounds (one general, one specialization-focused), a system design round (required from mid-level up), a database/SQL component, and a collaboration/leadership round. Senior candidates may also get a technical retrospective: a deep-dive conversation on a specific past project, like a system design interview tailored to your real work. Most rounds run virtually even for onsite stages.
The interview loop
- Recruiter screen - 15-60 min on background, interest in Uber's domains, and logistical questions; shapes the loop.
- Online assessment (optional) - ~70-90 min CodeSignal or HackerRank test, 3-4 algorithmic problems from easy to medium (hard variants reported). Optional and role/experience-dependent; not all candidates receive it.
- Hiring-manager conversation - A chat with the hiring manager going deeper into your skills, decisions, and how you approach problems at scale.
- Technical phone screen - ~45 min live coding on CodeSignal with one or two Uber engineers, focused on medium-to-hard problems.
- Onsite / virtual loop - 4-6 rounds:
- General coding - Basic data structures and algorithms questions.
- Specialized coding - Domain-specific coding: backend, web, or mobile depending on role (e.g., code a specific component or widget).
- System design - 60 min, required from mid-level up. Real-time and geo-distributed systems (dispatch, matching, surge) are common.
- Database / SQL - Database concepts, SQL, and data lifecycle questions. Know more than basic queries.
- Collaboration / leadership - Led by the hiring manager: experiential and hypothetical questions on ownership, feedback, and past decisions. Mapped to Uber's core values.
- Technical retrospective (senior) - For experienced candidates: a deep-dive on a specific past project from your resume, explored from multiple angles, like a system design interview tailored to your real work.
What they look for
- Algorithmic coding speed plus depth in your specialization
- Scalable system design for real-time, high-throughput services (dispatch, matching, surge)
- Database and SQL fluency beyond basic queries
- Collaboration and leadership signal mapped to Uber's core values (Go get it, Trip obsessed, Build with heart, See the forest and the trees)
How to prepare
- Prep the CodeSignal format; pacing across multiple problems matters. HackerRank is also used, not just CodeSignal.
- For design, study real-time and geo-distributed systems (dispatch, matching, surge).
- Have leadership and collaboration stories ready for the dedicated round, mapped to Uber's core values.
- Brush up on database lifecycle and SQL; it's a distinct onsite component, not just a subtopic.
- If senior, prepare a deep technical retrospective on one past project. It's like a system design interview about your own work.
