Candidatei-me por meio de recrutador(a). O processo levou 2 semanas. Fui entrevistado pela Uber (New York, NY) em out. de 2018
Entrevista
Initially you start with a phone screen for a coding question
This is a five-round interview loop that touches upon variety of areas:
1) Practical coding (spin up a website from scratch; spin up a RESTful API server from scratch)
2) Algorithms (standard coding questions)
3) System design (design a highly scalable, distributed system on the whiteboard)
4) Bar raiser interview (this is basically a culture fit screening from a third-party team)
5) Hiring manager interview (one that potentially whom you will be reporting to)
Helpful resources are algorithm books (Cracking the Coding Interview) and coding websites like leetcode or haclerrank you might find out there. Also consult engineering blogs to get insights on how to properly design systems at large scale.
Make sure you have enough narratives to tackle situational questions. Typically these are the ones asking for handling disagreements, your daily process at work, etc. Make sure that you justify all your questions and describe your process thoroughly. Basically, thinking in terms of the interviewer's shoes is the key!
They let you bring the laptop onsite, and it is highly encouraged to do so. This is one of the "newer" companies that evaluates on your real skills rather than your ability to do things on the whiteboard.
2
Outras avaliações de entrevista de vagas de Software Engineer da empresa Uber
The interview process started with a recruiter screen where they covered my background and the role's expectations. Next, I had a phone screen focused on technical skills where I faced a DSA question on frequent elements in an array. I had practiced similar problems on prachub.com beforehand, which helped me tackle it effectively. The technical rounds consisted of coding and system design questions, including rate limiting. Finally, I had a behavioral interview where they assessed cultural fit. Overall, the experience was average, but I received and accepted an offer.
Fui entrevistado pela Uber (San Francisco, CA) em abr. de 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
As melhores empresas na categoria “Remuneração e benefícios” perto de você