Recruitment was messy.
The recruiter responded, and we had an initial phone call, which is normal. However, at the end, I was told I'd get a time-sensitive email, but it was never sent. I had to reach out a week later to get the email. The recruiter claimed they were sick and forgot about it, so this was likely an anomaly.
My interview was also a mess. I applied for a front-end-focused role and was interviewed by someone who said they worked on the main Uber app's rideshare pricing algorithm. They gave me the interview question. I struggled with the first way to solve it, and they told me to switch to a different way. I struggled there, and they told me to switch back. By that point, there wasn't enough time to get to the solution.
The interviewer was not a good fit, nor good at conducting interviews. I will admit that at the end of the day, I didn't solve the problem, and that's on me.
The specific question was not provided, but the solution involved either a hashmap-based approach or a recursive approach.
The following metrics were computed from 23 interview experiences for the Uber Software Engineer role in New York, New York.
Uber's interview process for their Software Engineer roles in New York, New York is extremely selective, failing the vast majority of engineers.
Candidates reported having good feelings for Uber's Software Engineer interview process in New York, New York.