Describe a time when your project failed.

"Not that hard, pretty easy SQL coding challenge. Have to run the SQL live in a Python NB. The behavioral was also pretty easy and mostly about past projects and failures and probing more on resume."

"I got in through a referral, had a lightweight recruiter call, then an initial coding screen, and then a five-round final. The final was two coding rounds, one system design, one past-project round that turned into a behavioral deep dive, and one straight behavioral. What stood out was how much Uber cared about technical depth over polished cross-functional storytelling, especially for a staff role. Even the coding rounds felt like they wanted system-design-style tradeoff thinking, and they gave me the Number of Islands variant in the final coding round."

"What went well: interesting questions, everybody kind and smart. What didn't go well: I should have prepared more to tell about business impact."

"The interview process was well-structured and fairly rigorous compared to others I’ve experienced. I appreciated that the recruiter clearly communicated expectations upfront, which helped me prepare in the right direction. The technical rounds were challenging but relevant to the role, and the interviewers were professional and engaging."

"Overall pretty straightforward, their interviews are pretty standard and are not there to surprise you. Recruiter and interviewers were professional."

"The process was relatively straightforward. The hiring manager was very conversational and introduced himself. It felt like we were just having a chat. I was an internal hire so I might have had it easier than someone who would have interviewed from outside."

"Answered effectively, they were looking more for an international experience (Asia) and the job description didn't mention"