Having a good time so far!
Having a good time so far!
- You get to solve interesting and meaningful problems.
- You work with very smart and friendly co-workers.
- You have high impact, and your code gets deployed in production frequently.
- You are flexible on design decisions while you take ownership of projects.
-
Code review and code style are not strongly enforced, which sometimes can cause trouble or make it difficult to understand legacy code.
-
Test in production culture: There is no QA at Uber, so everyone is QA. You are responsible for your own bugs, but many times people are not careful enough and cause outages in production.
-
Technical debt.
-
Sometimes people get fired simply because they aren't in a good relationship with their direct manager.
- Reduce the number of meetings every week.
- Simplify politics and focus more on productivity.
- Reduce the frequency of org changes.
Was this helpful?
Uber Interview Questions
Uber Interview Experiences
Software Engineer
The interview process was straightforward. It included one technical phone interview and four onsite interviews: * One coding interview * Two architecture/systems design interviews * One culture fit interview The process itself was quite slow
Software Engineer
I got the inside referral, and it moved fast. I got the phone call from HR and scheduled the phone interview three days later. The onsite interview was five days after the phone interview. The onsite one started from noon, after lunch. There were f
Software Engineer
I was contacted by a recruiter for the software engineer role. There was an initial phone screen testing usual algorithms questions. Then I was called for the onsite the next day and fixed a time over the next week. Had 5 rounds of interviews with
Software Engineer
San Francisco, California, United StatesDecember 1, 2015The interview process was straightforward. It included one technical phone interview and four onsite interviews: * One coding interview * Two architecture/systems design interviews * One culture fit interview The process itself was quite slow
Software Engineer
San Francisco, California, United StatesMarch 1, 2016I got the inside referral, and it moved fast. I got the phone call from HR and scheduled the phone interview three days later. The onsite interview was five days after the phone interview. The onsite one started from noon, after lunch. There were f
Software Engineer
San Francisco, California, United StatesMarch 1, 2016I was contacted by a recruiter for the software engineer role. There was an initial phone screen testing usual algorithms questions. Then I was called for the onsite the next day and fixed a time over the next week. Had 5 rounds of interviews with
