I replied to a LinkedIn email from the recruiter about a newly opened Seattle office and expressed my interest. After the phone call with the recruiter, I was scheduled for a 45-minute technical phone screen. I was extremely nervous and managed to bomb both the behavioral part of the screen and the coding portion too. So, no surprises, I was promptly rejected.
What could have been improved.
A recruiter could have set clearer expectations for the interview (e.g., that there would be a significant non-technical portion). As is, I failed to showcase any of my abilities and, as a result, had a terrible experience as a candidate.
A large portion of the technical screen was spent detailing and drilling down on past work experience. Know your resume and be prepared to talk about specifics. This was followed by a coding task in CoderPad.io.
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.