The most responsive and open interview process I have ever been involved with. From the very beginning, I was given all-star help and guidance.
The process began with a quick talk about the company and my background, which served as the initial screening. This was followed by a coding challenge, unless I already had public code I preferred they look at. I enjoy a good challenge, so I chose one of theirs: a full-stack, single-page web application.
After a week, I submitted the project. They had a single day to review the entire thing! The following day was a technical overview of my experiences. Later the same day, I was informed I was invited for an onsite interview at HQ.
I was to front the bill for travel, but their expense reimbursement process is painless; they ultimately pay for everything. The onsite interview was, to respect their process, both a pleasure and a challenge.
An architecture question.
A problem-solving question.
A coding/data structures challenge.
A one-on-one with the manager for a culture fit.
The following metrics were computed from 121 interview experiences for the Uber Software Engineer role in San Francisco, California.
Uber's interview process for their Software Engineer roles in San Francisco, California is fairly selective, failing a large portion of engineers who go through it.
Candidates reported having very good feelings for Uber's Software Engineer interview process in San Francisco, California.