How Uber interviews
These are the Uber loops we have researched. Each one lists the rounds, what they test, the follow-up questions to expect, and how to prepare, with the sources we used.
- Distributed Systems Engineer
- Senior, L5a · 5 rounds · 5 h
- Product Manager
- Senior / 5A · 5 rounds · 3 h 25 min
- Product Designer
- Senior · 5 rounds · 4 h 15 min
- UX Researcher
- Senior · 6 rounds · 4 h
What Uber says about its interviews
Uber’s current engineering hiring page describes a collaborative coding interview followed by evaluation with the team and cross-functional partners. Uber Engineering: current hiring stages
Uber's current official PM interview guidance names a Jam Session and Product Insights & Execution, Leadership & Scope, and Technical Depth 1:1s. Inside Uber's Product interview process
Uber's current product material emphasizes real-time multi-sided decisions, physical-world context, global differences, safety, and technical foundations. Building what's next at Uber
Uber Distributed Systems Engineer interview
Prepare for a coding screen followed by algorithmic coding, implementation depth, distributed-system design, and collaboration and leadership. Senior Uber preparation requires clear executable logic, deliberate concurrency decisions, and a design you can drive from requirements to failure recovery. Practice beyond ride matching: stateful services, caches, stream processing, and partitioned workflows. Defend the architecture and measured impact of a system you personally owned.
The 5 rounds
Technical coding screen
Solve an unfamiliar problem with a justified model, complete code and room for a meaningful follow-up.
Expect: An unfamiliar graph, geometry or spatial problem with an extension.
Follow-ups: “What changes if the input cannot fit in memory?” “Which assumption makes the approach valid?”
Algorithms and data structures
Deliver two complete algorithmic solutions while retaining precise reasoning and verification.
Expect: First tree or stateful-data-structure problem. Second graph or dependency-ordering problem.
Follow-ups: “How do cycles or duplicate dependencies affect the result?” “Can you support another operation without changing the complexity?”
Specialization: service implementation
Deliver a cohesive in-memory component with explicit contracts and safe state transitions.
Expect: One small stateful service extended for concurrency or lifecycle behavior.
Follow-ups: “What changes when entries expire?” “Can you preserve correctness while reducing lock contention?”
Distributed systems design
Connect requirements, APIs and partitioned state into a service that remains understandable under partial failure.
Expect: A stateful distributed workflow with hot keys, retries and recovery.
Follow-ups: “How does stale state affect the decision?” “What happens during partition reassignment or regional failure?”
Collaboration and technical ownership
Demonstrate senior responsibility for technical choices, cross-team progress and measurable production outcomes.
Expect: A system you owned through a difficult trade-off. A cross-team delivery disagreement. A failure and its operational follow-through.
Follow-ups: “Which trade-off would you reverse today?” “How did you get another team to change its plan?”
What candidates and sources report
- Uber’s current engineering hiring page describes a collaborative coding interview followed by evaluation with the team and cross-functional partners. Uber
- Uber’s coding guidance favors practical problem solving in a familiar language and an explanation of how the code works. Uber
- An L5A offer report describes five one-hour interviews: phone screen, algorithms, specialization coding, design and leadership. Candidate report
- The L5A screen involved a medium-hard to hard geometry or spatial-reasoning problem. Candidate report
- The same candidate’s algorithms round paired a medium tree problem with a hard graph/topological-sort problem. Candidate report
How to prepare
- Establish senior coding pace: Do an unfamiliar 60-minute problem, including a harder follow-up. Record modeling errors separately from coding slips.
- Practice two distinct problems: Pair a tree or cache exercise with a graph problem. Preserve verification and complexity discussion for both.
- Implement a concurrent component: Build a bounded stateful service, then trace two racing callers and an expiry or lifecycle transition.
- Design beyond ride matching: Model payouts, event delivery or configuration propagation. Stress the design with stale state, duplicates and a hot partition.
- Defend a production decision: Rehearse a project at architecture and incident depth. Tie personal decisions to measured results and partner-team trade-offs.
Mistakes to avoid
- Do not assume the problem is a familiar tagged variant.
- Do not leave complexity or boundary behavior unstated.
- Do not round a scan down to constant time.
- Do not let narration disappear under time pressure.
- Do not add patterns that obscure state ownership.
Questions to ask your interviewers
- Which consistency or latency constraint dominates this team’s systems?
- What distinguishes L5a impact from strong individual execution here?
- How do teams coordinate when an incident crosses service boundaries?
Uber Product Manager interview
Uber's current official PM interview article names the Jam Session and 1:1 interviews in Product Insights & Execution, Leadership & Scope, and Technical Depth. A verified 2026 Senior/5A candidate reports a hiring-manager case, Uber Jam take-home deck and presentation, and five-interview onsite. Practice marketplace decisions with explicit users, North Star metrics, discarded scope, technical feasibility, and leadership evidence.
The 5 rounds
Hiring manager case
Establish product insight and fit through a focused Uber marketplace problem before the broader loop.
Expect: Improve one frustrating Uber journey. Prioritize a feature for a specific marketplace participant.
Follow-ups: “Who loses from this choice?” “What makes this problem worth solving now?”
Uber Jam presentation
Assess whether an ambiguous take-home marketplace problem becomes a clear, prioritized decision that survives panel challenge.
Expect: Present and defend a marketplace case recommendation without depending on visible slides.
Follow-ups: “What is the North Star metric?” “Which excluded problem is most dangerous?”
Product insights and execution
Test product sense, metrics, experimentation, and delivery in a dynamic two-sided marketplace.
Expect: Improve pickups during a large event. Design an experiment for a marketplace or campaign change.
Follow-ups: “How will the experiment affect supply?” “What operational signal triggers rollback?”
Leadership and scope
Verify Senior/5A leadership, prioritization, and ownership through distinct consequential experiences.
Expect: Influenced a feature's priority. Balanced technical debt and new product work. Led through conflict or failure across functions.
Follow-ups: “What did you stop doing?” “How did your scope expand?”
Technical depth
Determine whether the PM can make sound product choices across real system and operational boundaries.
Expect: Trace a marketplace feature through APIs and operational systems. Choose between latency, reliability, and experience trade-offs.
Follow-ups: “Where does latency change user behavior?” “Which failure needs product recovery?”
What candidates and sources report
- Uber's current official PM interview guidance names a Jam Session and Product Insights & Execution, Leadership & Scope, and Technical Depth 1:1s. Uber
- Uber advises Jam candidates to identify the central problem, North Star metric, target user, excluded scope, and explicit trade-offs within about 40 minutes. Uber
- Uber says Technical Depth does not require coding but does require reasoning about APIs, latency, scalability, and technical feasibility. Uber
- One verified Senior/5A candidate reports a hiring-manager case, Uber Jam take-home deck and presentation, and a five-interview onsite. Candidate report
- Reported questions include feature prioritization, large-event pickups and drop-offs, A/B testing, tech debt, and design partnership. Candidate report
How to prepare
- Practice one-sided focus: Take an Uber journey, choose one participant and problem, then show consequences for every other marketplace side.
- Rehearse the Jam opening: Deliver problem, levers, North Star, exclusions, and recommendation in a concise spoken executive summary.
- Run marketplace experiments: Design tests with interference, supply response, operational rollout, guardrails, and a decision threshold.
- Prepare scope evidence: Bring prioritization, conflict, tech-debt, and failure stories with discarded work and measurable impact.
- Explain system consequences: Trace one feature through APIs, latency, degraded modes, support, and the user-visible recovery path.
Mistakes to avoid
- Do not redesign the whole app.
- Do not optimize riders while ignoring earners.
- Do not solve the whole marketplace.
- Do not narrate invisible deck pages.
- Do not use conversion as the only outcome.
Questions to ask your interviewers
- What is the team-specific Jam format and preparation window?
- Which marketplace participant's outcome is hardest for this team today?
- How are the five onsite interviews allocated beyond the three named 1:1s?
Uber Product Designer interview
Uber's design team describes work at the boundary of digital interfaces and physical reality. A current report synthesis describes portfolio review, live design or whiteboarding, and onsite app critique, cross-functional, and behavioral interviews; exact team allocation remains uncertain. Prepare marketplace work that accounts for riders, earners, merchants, safety, connectivity, localization, operations, and measurable outcomes rather than clean screens alone.
The 5 rounds
Portfolio review
Assess end-to-end product design through a clear decision story rather than a screen or process tour.
Expect: Present one shipped digital-to-physical product journey.
Follow-ups: “What happened outside the interface?” “Which outcome changed?”
Marketplace design jam
Observe live framing, multi-sided systems thinking, flow design, safety, and response to collaboration.
Expect: Design a service for riders with a special physical need. Redesign a pickup or delivery handoff under real-world uncertainty.
Follow-ups: “What changes when location data is wrong?” “Which participant can reject the flow?”
Uber app critique
Test product judgment by diagnosing an existing journey and choosing one feasible improvement.
Expect: Critique upfront fare or ride request. Critique an Eats ordering or delivery handoff.
Follow-ups: “How could the change affect supply?” “What physical condition breaks the flow?”
Cross-functional design partnership
Verify that the designer can make better decisions with Product, Engineering, Data Science, Operations, and Safety.
Expect: A systems constraint changed the design. Operations or safety challenged the roadmap. Live feedback required a difficult pivot.
Follow-ups: “What did you change because of them?” “Which quality boundary stayed fixed?”
Responsible design leadership
Assess Senior design judgment and leadership across safety, localization, systems, and team craft.
Expect: A global design failed locally. A safety or trust concern changed direction. Raised design quality across multiple teams.
Follow-ups: “Who bore the risk?” “What guardrail remained after launch?”
What candidates and sources report
- Uber officially describes design as connecting digital and physical worlds across riders, earners, and eaters. Uber
- Uber says designers work with Product and Engineering from discovery through delivery and influence strategy before implementation. Uber
- Current Uber material emphasizes global systems, local context, safety, physical constraints, and high-cognitive-load moments. Uber
- A recent report synthesis describes a 45–60 minute portfolio review and 60-minute live design or take-home variant. Independent guide
- The same synthesis describes onsite app critique, technical feasibility, cross-functional collaboration, and behavioral evaluation. Independent guide
How to prepare
- Tell the decision story: Rehearse one shipped digital-to-physical journey around the pivotal choice, evidence, constraints, outcome, and lesson.
- Map every handoff: Design a marketplace journey across participants, location uncertainty, safety, degraded states, and recovery.
- Critique marketplace effects: Choose one Uber journey, explain the current logic, prioritize a change, and trace effects across participants.
- Prepare co-creation evidence: Bring Product, Engineering, Operations, Data, and Safety disagreements that changed the shipped design.
- Show responsible scale: Prepare safety, localization, and system-quality stories where your learning became a durable guardrail.
Mistakes to avoid
- Do not narrate every screen.
- Do not stop at research and process.
- Do not draw only the rider screen.
- Do not treat safety as a disclaimer.
- Do not list UI preferences.
Questions to ask your interviewers
- Does this team use live whiteboarding or a take-home design exercise?
- Which participant and physical journey will this role primarily serve?
- How does the team evaluate safety and marketplace trade-offs in design?
Uber UX Researcher interview
A recent Senior UXR candidate reports a hiring-manager case presentation, a two-case portfolio panel, then 40-minute 1:1s with each panel member. Another candidate says every interviewer asked about prioritization across roughly 20–30 stakeholders. Uber's current Senior UXR role requires mixed methods, global and safety-aware strategy, decisive synthesis, and influence across Product, Design, Engineering, Data Science, and Operations.
The 6 rounds
Hiring manager research case
Establish research depth and role fit through one consequential case before the panel.
Expect: Present one product research case aligned to the team's domain.
Follow-ups: “Why was research the right intervention?” “Which decision changed?”
Research portfolio panel
Assess breadth and senior research judgment across two cases for a cross-functional audience.
Expect: Present two contrasting research cases without depending on visible slides.
Follow-ups: “Why did these cases belong together?” “Which stakeholder remained unconvinced?”
Methods and rigor
Determine whether the candidate can design credible mixed-method research for a dynamic physical-world product.
Expect: Choose methods for a global safety-sensitive study. Repair a biased research plan under time pressure.
Follow-ups: “Who is missing from the sample?” “What conclusion would the design not support?”
Product insight and metrics
Test synthesis across user evidence, metrics, marketplace behavior, and a concrete product decision.
Expect: Reconcile interview findings with contradictory product data. Plan research for a marketplace metric change.
Follow-ups: “What would change the roadmap?” “Which marketplace participant is invisible?”
Research prioritization
Verify prioritization, scope, and trust when demand exceeds research capacity.
Expect: Prioritized across many product stakeholders. Declined a study and offered a better path. Balanced urgent evaluation with foundational research.
Follow-ups: “What did you refuse?” “How did you preserve trust?”
Research influence and leadership
Assess Senior UXR impact across strategy, product teams, regional partners, and the research craft.
Expect: Research changed a contested roadmap. A global insight failed in one market. Raised research quality across other practitioners.
Follow-ups: “Who changed their decision?” “What remained unresolved?”
What candidates and sources report
- One recent Senior/mid UXR candidate reports a hiring-manager stage where one case study is presented and questioned. Candidate report
- The same candidate reports presenting two case studies to a panel including product, design, UXR, and the hiring manager. Candidate report
- That candidate then completed 40-minute 1:1s with each panel member. Candidate report
- Uber's current Senior UXR role owns global research strategy across safety, marketplace, earner, and rider perspectives. Job posting
- The role requires qualitative, quantitative, and mixed methods plus persuasive synthesis that drives product and business decisions. Job posting
How to prepare
- Sharpen one research case: Rehearse one case around the decision, method choice, limitations, insight, stakeholder action, and outcome.
- Build the two-case arc: Pair contrasting cases and make the method, stakes, audience, and influence difference obvious without visible slides.
- Defend method boundaries: Practice sampling, bias, consent, mixed-method integration, and conclusions the evidence cannot support.
- Reconcile conflicting evidence: Use qualitative and behavioral signals to form competing explanations and choose the next product decision.
- Prepare prioritization evidence: Bring a story with too many requests, a clear decision rule, rejected work, and preserved stakeholder trust.
- Show influence beyond findings: Prepare roadmap, global-context, and craft-leadership stories where another person's decision visibly changed.
Mistakes to avoid
- Do not list methods chronologically.
- Do not claim the team followed every recommendation.
- Do not squeeze in every study detail.
- Do not present recommendations as impact.
- Do not use mixed methods as decoration.
Questions to ask your interviewers
- Which panel member owns each 40-minute 1:1?
- What confidentiality boundaries apply to portfolio research cases?
- How are urgent evaluative studies balanced with foundational research here?
Sources
Research reviewed . Practice exercises are our own; they are not confidential interview questions.
- Uber Engineering: current hiring stages — Uber
- Uber: navigating the engineering coding interview — Uber
- Uber L5A senior offer: five-round experience — Candidate report
- Google, LinkedIn, Uber and Salesforce interview experience — Candidate report
- Inside Uber's Product interview process — Uber
- Uber Senior Product Manager interview experience — Candidate report
- Uber Product Manager candidate-report synthesis — Independent guide
- Senior Product Manager, Autonomous Experience — Job posting
- Building what's next at Uber — Uber
- Uber Design — Uber
- Uber Product Designer interview synthesis — Independent guide
- Uber portfolio-storytelling candidate reflection — Candidate report
- Uber Senior UXR candidate thread — Candidate report
- Senior UX Researcher, Moto — Job posting
- Uber Seattle Senior UXR interview — Uber
Independent preparation using Uber as a practice target. Not affiliated with, endorsed by, or sponsored by Uber.