Uber

• Strong engineering managers. From what I've seen on the money team, managers here have a good business sense and also understand the value of giving engineers the freedom to create. I love how my boss is watching over my progress as an engineer and helping get blockers out of my way.

• Plenty of challenging problems. Uber is growing fast and the business inherently is technically challenging from an engineering perspective because it interfaces with so many things in the real world (cars, people, restaurants, partners, etc.).

• Flexible schedule. I've heard the "long hours" line a couple times, but I definitely do not feel that. I do 9 to 5 basically (or more like 10 to 6), so no more than 8 hours per day, and I've never felt pressure to do more. If you get sh*t done, that's all they care about.

Dealing with systems that have not adapted to Uber's growth. Uber has grown so fast that many of the systems are starting to look hacked together. As an engineer that values simple architecture, it could be painful at times.

I would advise paying attention to two things that may feel the pain of growth the most:

• Hiring practices. Ensure we're introspective in our approach and take hiring seriously so as not to lower the quality of hires.
• Architecture. Uber's growth has caused a lot of technical pain; we should seriously consider the tradeoffs of future-proof systems or even write the infrastructure that would facilitate quick adaptability.