Taro Logo

Software Engineer Interview Experience - San Francisco, California

February 1, 2016
Negative ExperienceNo Offer

Process

Great onsite experience but terrible follow-up phone screen experience. I believe that I did well for the onsite interview, but got the phone from recruiter saying that they want to make sure that they are making the right decision and would like to add another phone screen. No problem, recruiter followed up with a codepen.io link which I assumed that it's a frontend phone screen. I double-checked with the recruiter and the recruiter said yes, this will be a pure frontend interview. And I spent days preparing for the frontend interview. At that day, an interviewer called my phone. After a brief introduction of herself, then we proceeded to the coding part. I passed a chunk of JSON object and description and asked me to implement it. First of all, why are we doing algorithm questions on codepen.io????? Secondly, codepen.io was buggy. As soon as I shrunk the UI display part, part of the description was gone. I refreshed my window and got the message saying that the room has exceeded the maximum amount of people allowed. I asked the interviewer and she said that she doesn't know what to do. After minutes of trying, we moved on to using jsfiddle collaborate, which also a poor choice for algorithm-based coding. The interviewer were moving her mouse around for the entire time. It was extremely distracting and rude, but I got distracted a lot as her mouse constantly stayed on my code and I had to scroll around to see my coding. That distracted me a lot. Secondly, there was no way to really debug and code on jsfiddle collaborate, as there were tons of exceptions/errors flowed into the console at any given time, which were extremely distracting as well. The interviewer also threw me off multiple times. She said things like, why you use DFS or BFS (which is perfectly fine)? Then she asked whether we should use stack or queue for BFS and DFS? I said that for BFS we should use queue and DFS we should use stack. Then she said no, we should use stack for DFS and queue for BFS. Excuse my accent, but that's exactly what I said. Then I repeated myself, and she said no again. Even though I said exactly what she said. Then I have to specifically say Depth First Search and Breadth First Search to stop her confusing my pronunciation of "B" and "D". Once I was close to complete with my implementation, she said that can't you just return results directly within your recursion when there is clearly no way to do so, which threw me off again. A non-stop interruptions and distracted phone screen experience. But I admitted that I didn't perform well on the phone. I am actually doing better in person. Redid the problem and completed it in 10 minutes after phone. Anyway, I blamed myself not able to perform on the phone.

Questions

Why Uber?

Was this helpful?

Interview Statistics

The following metrics were computed from 117 interview experiences for the Uber Software Engineer role in San Francisco, California.

Success Rate

32%
Pass Rate

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.

Experience Rating

Positive62%
Neutral16%
Negative21%

Candidates reported having very good feelings for Uber's Software Engineer interview process in San Francisco, California.