Uber · Software engineer · L5 (Senior), scope-weighted for seniority

Leadership & Values (Behavioral)

Conversational, STAR-driven, calibrated interviewer

What they actually ask

The question shapes this round uses. Larpy does not read these out. It builds each one from your own resume, because the generic version is the one you have already rehearsed.

“Tell me about a project you owned end to end, what was YOUR individual impact and how did you measure it?”
“Describe a time you disagreed with a teammate or manager and how you resolved it.”
“Tell me about a time you worked under significant ambiguity or shifting requirements.”
“Describe a hard technical tradeoff you made and how you decided.”
“Tell me about a time you failed or a project that didn't go as planned, what did you learn?”
“Tell me about a time you influenced others without formal authority.”

What this round is judged on

Ownership & impact · acted like an owner; measurable individual contribution
Collaboration & conflict · resolved disagreement, influenced without authority
Ambiguity · progressed under shifting or unclear requirements
Values fit · alignment with Uber's culture and 'why Uber' motivation
Leadership scope · weighted up for senior levels

Where this round sits

Uber’s published process. Lime marks the stage this round runs.

01
Recruiter or sourcer call
02
HackerRank coding assessment (not simulated here)
03
Technical phone screen
04
Interview 1: Algorithms & data structures
05
Interview 2: Depth in specialization
06
Interview 3: Collaboration & leadershipthis round
07
Decision

What happens in each stage›

Recruiter or sourcer call: Uber publishes this as "Talk with a Recruiter or Sourcer (Virtual | 30 min)". Background, motivation, logistics, and level calibration against the ladder Uber displays: L3, L4, L5A, L5B, L6+. Non-technical.
HackerRank coding assessment (not simulated here): An online coding assessment Uber lists between the recruiter call and the technical screen. Uber does not publish a duration or a problem count for it.
Technical phone screen: Uber's own label is "Business (Technical) Phone Screen to Assess Coding + Design & Architecture Competencies (Online | 60 min)". Design and architecture are assessed inside this screen rather than as a separate round.
Interview 1: Algorithms & data structures: Uber publishes this as "Software Engineering - Algorithms & Data Structures (Coding 1)", 60 minutes.
Interview 2: Depth in specialization: Uber publishes this as "Software Engineering - Depth in Specialization (Coding 2)", 60 minutes. The applied round, weighted toward your domain rather than general algorithms.
Interview 3: Collaboration & leadership: A named 60-minute competency round. Uber assesses competencies through STAR-style behavioral questions, and this round appears at every level Uber lists, not only senior ones.
Decision: Uber names a "Decision" stage in which recruiters and hiring teams review performance against the role criteria. Uber does not publish committee mechanics or a debrief format.

Sources

Built from what Uber publishes about its own process and from real interview data. No leaked question lists. The questions you get are generated against your own resume, so they are not from anyone else's interview.

companyUber Engineering, Teams (jobs.uber.com)jobs.uber.com
Engineering culture and values framing: engineers 'trusted to explore and experiment freely, using innovation to drive impact'; 'systems that learn from billions of signals in real time'; domains include AI/ML, autonomous vehicles, real-time and marketplace systems.
datalevels.fyi, Uber Software Engineerlevels.fyi
Uber SWE level ladder: L3 (SWE I, entry) through L4 (SWE II), L5 (Senior 5a / Staff 5b), and L7+. Compensation context only, no interview-process detail.
companyUber, Backend Engineering Interview Guidejobs.uber.com
Uber's published engineering loop with its own stage names and durations: recruiter or sourcer call (30 min), HackerRank coding assessment, "Business (Technical) Phone Screen to Assess Coding + Design & Architecture Competencies" (60 min), Algorithms & Data Structures (60 min), Depth in Specialization (60 min), Collaboration & Leadership (60 min), Decision. Shows the L3, L4, L5A, L5B, L6+ ladder and names no standalone system design round.

Sources last checked August 10, 2026. Hiring loops change, so this date is the honest limit on everything above.

Other Uber rounds

Templates

All Uber rounds