Uber lays off around 350 more across Eats, self-driving and other departments
This is hardly surprising at all. There used to be lots of complaints, both internally and publicly, about how bloated and ineffective Uber&#x27;s engineering organization was. Many engineers were bitter about many overlapping projects in Uber. It&#x27;s also funny that Uber engineers used many bogus reasons to implement NIH projects. A typical example is that Uber had a team to implement their own Bazel-like system because &quot;Bazel (or any other tool) does not scale in Uber-scale&quot;. Same went for their own GPU database, their own SQS, their own key-value store, their own resource scheduler, their own datacenter, and their own deployment system. The end result was that almost everything sucked. Engineers suffered productivity loss for years. I kid you not that Uber&#x27;s docker system didn&#x27;t support persistent volume for more than three years, so anyone who wanted to build a persistent system like Elasticsearch had to jump hoops and spent weeks even just to get machines. And the sad fact is, Uber did not have a &quot;Uber scale&quot;. The traffic and complexity it had to handle was far less than other internet companies.<p>I wish they didn&#x27;t hire so irresponsibly back in 2015 and 2016.