Standard tech hiring process:
An external Uber recruiter reached out for the initial rounds. For the onsite interviews, internal Uber HR was assigned. The recruiter was supposed to set up a 15-minute call with me beforehand to give me some familiarity with the rounds and the teams I would be interviewing with. I tried to follow up with the recruiter several times to set up this call, but they never responded to any of my questions. My onsite was set up by the coordinator.
I agreed to the onsite with no clue about the teams I was being considered for, which was my mistake, but I hoped my onsite experience would be better.
On the day of my onsite, I reached the Uber office and the recruiter never showed up after I waited for 25 minutes. I then asked the receptionist to reach out to the recruiter again as it was time for my initial interview. Someone else showed up, saying the recruiter was busy. I still hoped the recruiter would show up after all the rounds, but they were still nowhere to be seen.
I didn't even bother to thank the recruiter or follow up after the onsite.
The technical rounds were fun and engaging, and I hadn't solved those previously.
I could have done a little better in the design and behavioral rounds, though.
The following metrics were computed from 9 interview experiences for the Uber Software Engineer role in Palo Alto, California.
Uber's interview process for their Software Engineer roles in Palo Alto, California is extremely selective, failing the vast majority of engineers.
Candidates reported having very negative feelings for Uber's Software Engineer interview process in Palo Alto, California.