Sr Software Engineer applicants have rated the interview process at Uber with 3.7 out of 5 (where 5 is the highest level of difficulty) and assessed their interview experience as 67% positive. To compare, the company-average is 44.4% positive. This is according to Glassdoor user ratings.
Candidates applying for Sr Software Engineer roles take an average of 30 days to get hired, when considering 3 user submitted interviews for this role. To compare, the hiring process at Uber overall takes an average of 37 days.
Common stages of the interview process at Uber as a Sr Software Engineer according to 3 Glassdoor interviews include:
Phone interview: 100%
Here are the most commonly searched roles for interview reports -
I applied online. The process took 1 week. I interviewed at Uber (Seattle, WA) in Jul 2018
Interview
Initial Phone Screen with Hiring Manager. After that technical interview with one of the Engineers. First 10 mins he discussed about my background and the work I do. After that he gave me an online coding challenge.
I applied through a recruiter. The process took 2 weeks. I interviewed at Uber (Haiderabad)
Interview
The hiring process started off positively, but completely went off the rails starting from the day of the interview.
One interview that was scheduled to happen, did not happen. The recruiter told me they will contact me again, but never did. They never even got back to me with the final outcome, and completely ghosted me.
The engineers are not really trained well in interviewing. Instead of evaluating the candidate based on their skills and experience, they are more interested in whether candidates can answer the question that fits a template that the interviewers have already determined.
I had a phone screen that I feel was not set up well. I asked Recruiter to schedule it in afternoon but he scheduled it like early in the morning, maybe because he could not realize his time zone is different from mine. The phone screen also did not went well because the speaker phone the interviewer was very muffled. I told him the connection was not good but he did not want to try calling back. As a result I could not hear his questions clearly and had to ask him to repeat a few times, and that ate the time I needed to solve the problems.