I was contacted by a recruiter on LinkedIn.
Phone interview about Android Fundamentals (medium).
On-site interview in 4 modules: a. Architecture/Design a Mobile App b. Android coding interview c. Hiring manager d. Algorithm (Not good)
Experience gained: Normally, Uber has a board to make a decision about the candidate, and the Hiring Manager is the one who can overrule even if you got all 'No's. However, the unwritten rule is that all members look to the most senior person with the most work experience in the company.
Not lucky that the Algorithm guy (Staff Engineer) was the most experienced person among the interviewers (5 years), and the Hiring Manager had only 9 months.
P.S. Always ask about the approach for the algorithm: do they want to get the result from the code or from the use cases to the solution? Do anything you feel comfortable with, not the approach the interviewer is comfortable with.
My result is based on interview feedback: a. Architecture/Design a Mobile App (GREAT) b. Android coding interview (WELL) c. Hiring manager (GREAT) d. Algorithm (Not good)
The following metrics were computed from 1 interview experience for the Uber Senior Android Developer role in Australia.
Uber's interview process for their Senior Android Developer roles in Australia is extremely selective, failing the vast majority of engineers.
Candidates reported having mixed feelings for Uber's Senior Android Developer interview process in Australia.