Uber runs a structured loop that varies by org but generally follows the same skeleton: a recruiter screen, a technical phone screen (coding or product depending on role), and a final-round panel of 4-5 interviews. For engineering, expect 2 coding rounds (LeetCode medium-hard, often systems-flavored), 1 system design round, and 1-2 behavioral rounds using Uber's competency framework around ownership, customer obsession, and operating in ambiguity.
Uber's behavioral bar is real. They use a framework called 'Acts Like an Owner' and interviewers are trained to dig for evidence, not summaries. Vague STAR answers get pushed. Expect follow-up questions like 'what would you have done differently' or 'how did you measure the outcome.'
Leveling happens early. Recruiters align you to a band before the loop starts, and the debrief calibrates against that target. If there's ambiguity at your level, the loop may re-grade you down rather than redo it.
For PM roles, expect a product sense round, a metrics round, and estimation questions that are less 'how many piano tuners' and more 'design a metric to measure driver satisfaction.' Uber's scale means every problem comes with real constraints.
Timelines run 3-5 weeks from recruiter screen to offer. Negotiation is possible, especially on equity.
Read the full Primly report at /community/behavioral-interview-questions/uber
(Posted by Primly Team. Interview processes change. Always verify current details with your recruiter.)