Updated by Uber candidates
Software Engineer Interview Experience
Interview process
The process involved two coding rounds and a system design interview. The coding rounds went smoothly - I was comfortable with the data structures involved, including a question on binary indexed trees (Fenwick trees) for range sum queries. What didn't go well was the system design round; the interviewer gave very little feedback or direction, making it hard to gauge if I was on the right track. Communication from the recruiter between rounds was also slow.
- Phone interview
Interview tips
Brush up on tree-based data structures (especially binary indexed trees and segment trees). Practice explaining your thought process out loud clearly, since the interviewers aren't very forthcoming with hints. Also, don't expect a warm or conversational interview style; treat it as a purely technical evaluation and prepare accordingly.
Company culture
The interviewers seemed disengaged and gave the impression they'd rather be elsewhere. There wasn't much enthusiasm when discussing the team or the problems they work on. It didn't feel like a place that invests heavily in making candidates feel welcomed or valued during the process, which raises questions about the day-to-day culture.
Questions asked
Question types asked
Specific questions asked
Get full access with a membership, or share your experience to try it free.
