The interview process included a standard technical phone screen followed by an onsite interview. The onsite consisted of:

• Two coding questions
• An architecture question
• A "bar raiser" interview, which was essentially a business conversation with a general manager from another team
• A one-on-one with a manager to discuss cultural fit

All coding interviews, including the onsite, were conducted using CoderPad, which was a positive aspect.

Overall, the team was working on interesting projects. However, the offer was lowballed in both equity and salary. The company's process seems optimized for "offer collectors," so it's advisable not to interview at Uber unless you are also interviewing at similarly sized companies. The recruiter was upfront about their strategy: they offer the lowest possible amount within the band unless competing offers are presented, and they are unwilling to negotiate otherwise. This was disappointing, as Uber was chosen for an interview due to genuine interest in the company. This approach also suggests something about career development within Uber. Ultimately, the offer was declined, and I remained at my current employer.

Phone screen: Given a stream of events, bucket them into buckets of a given time window.

Also had a derivative of the Two Sum question and a Knapsack problem in disguise as something else.