I was referred by a friend.
After that, I had a basic phone screen to see who I was.
Following that, I had two technical phone screens.
It took about one week for them to schedule the first one, and then I waited two more weeks until the second.
The first was pretty easy, with basic array algorithm questions similar to those found in "Cracking the Coding Interview."
The second phone screen was much harder. There was only one question, but it was much more involved to answer.
(Easier) You have a sorted array of integers. Find the element where the array index is equal to the value of the corresponding element. Or return that no such element exists.
(Harder) You have a dictionary of words. Create a matrix of letters such that each row of the matrix is a word and each column of the matrix is a word. Kind of like a very dense crossword puzzle.
The following metrics were computed from 373 interview experiences for the Uber Software Engineer role in United States.
Uber's interview process for their Software Engineer roles in the United States is very selective, failing most engineers who go through it.
Candidates reported having good feelings for Uber's Software Engineer interview process in United States.