I was contacted by a recruiter on LinkedIn for Uber ATG and scheduled a phone call.
The HR phone call discussed the work Uber does, asked general questions about my resume, and Uber's safety model.
Afterwards, a technical phone interview was scheduled using a Codepair link. This was with one of their engineers who asked a standard LeetCode question.
After the phone interview, the recruiter followed up within two days, notifying me if the interview was successful and giving feedback on what I did well.
Then an onsite was scheduled, which consisted of 3 technical and 2 cultural interviews.
The technical interviews consisted of:
The behavioral interviews consisted of:
Phone: Variation of Largest Islands question.
What does safety mean to you?
Onsite: Variation of Tower/Goal/Robot grid question.
Onsite: Generic design question (e.g., design Sudoku, Battleship, Tic-Tac-Toe, etc.).
The following metrics were computed from 1 interview experience for the Uber Software Engineer, Backend role in Pittsburgh, Pennsylvania.
Uber's interview process for their Software Engineer, Backend roles in Pittsburgh, Pennsylvania is extremely selective, failing the vast majority of engineers.
Candidates reported having very good feelings for Uber's Software Engineer, Backend interview process in Pittsburgh, Pennsylvania.