Me postulé en línea. El proceso tomó 5 semanas. Acudí a una entrevista en Uber (San Francisco, CA)
Entrevista
Time to explore new opportunities, so I submitted my resume to a few top Valley companies and startups including Uber. Got contacted by the recruiter a few days later after my online submisson.
1) Recruiter initial phone call. (30 mins)
2) TPS (1 hour)
You need to solve the coding exercise via online code sharing editor. Some follow-up discussions.
3) Take home code challenge.
I spent a weekend on building the solution and making sure I like what I submitted. I got feedback next day. Amazing efficiency.
4) 4 onsite interviews (4 - 5 hours) at Uber HQ.
Jam with a group of Uber engineers, plus a nice onsite lunch break. Each interview is designed with 2 engineers except the Culture fit one which is a product discussion with one of the engineering managers. I did some coding questions on my laptop.
5) Wrap up with my recruiter.
All questions are reasonable. Marked the interview as difficult in the sense that you definitely want to be well prepared. There were quite a few problems I never saw before. Know your stuffs well -- you should be OK.
The interview process is very smooth. I have no issue with my onsite travel reimbursement, although it took ~3 weeks to get it completed.
I got a call in the next one or two days after my onsite with an offer! The package is excellent. I chose Uber over other offers/opportunities because I really believe in Uber's mission that is happening in an incredible scale. And all the engineers I met are super cool, sharp and resourceful.
Preguntas de entrevista [1]
Pregunta 1
OOD, Data Structure (Hashtable, String manipulation)
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.
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
