Me postulé a través de un reclutador. El proceso tomó 2 meses. Acudí a una entrevista en Uber (San Francisco, CA) en nov 2018
Entrevista
Started by talking to the recruiter. Recruiter scheduled an interview with one of the engineers which was more technical. After that interview, I was invited onsite for a full day interview. I flew out to San Francisco. I talked to the team that was interested in hiring me. I first spoke to the manager and we talked about my experience. The next person did whiteboard problem. The way it's done here is that you start thinking about how to solve it and then go code it afterwards. After this, there is a lunch break with the team. After that, there is another whiteboard problem similar to the previous, but with other people. After that, there was a system design interview. This was the only part of the interview I did not like. The interviewer did not explain what he wanted clearly. The problem was to add functionality to a project I had previously worked on. The hardest part of this was trying to explain to him that this functionality already exists, but he didn't get that. The last part is a deep dive into my experience similar to the first part of the interview. This was more about what I did instead of explaining how I handled a situation. Overall, the interview was great. I only wish I had brushed up on my CS fundamentals. I have a few years under my belt so it's been a while since I had to use them.
Me postulé en línea. Acudí a una entrevista en Uber en may 2026
Entrevista
The interview process begins with an initial BFS screening to evaluate overall fit and relevant experience, followed by three virtual onsite interviews that focus on coding ability, an in-depth discussion of technical background and past projects, as well as behavioral and collaboration-related questions to assess communication and teamwork skills.
Acudí a una entrevista en Uber (San Francisco, CA) en abr 2026
Entrevista
Recruiter screen then there was a hiring manager round which felt more like a mix of product sense + execution - mostly a mix of OOP algorithms in Python or Java and some high-level system design. The onsite was 5 back to back rounds covering data structures, database management (heavy on SQL and data lifecycles), deep sys design, and behavioral. The sys design round was the real test where I had to walk through building a scalable real-time gaming leaderboard, discussing tradeoffs ofcourse in architecture, APIs, and data flow. The coding rounds was around things like linked lists and tree traversals, while the behavioral part focused heavily on ownership of my code and handling feedback. When you prep, make sure you can go a level deeper on database management and object oriented patterns instead of just grinding LC I’d say. I did grind LC though but ensure you understand the depth behind everything you solve. I also did a few mocks with uber swe on prepfully specifically for the sys design and database rounds and that honestly helped me catch some blind spots in my architecture knowledge and practice explaining my tradeoffs clearly. I’d say get a mock or two from anywhere if you can - helped me a lot!
3
Las mejores empresas en cuanto a "Remuneración y prestaciones" cerca de ti
