3 ms·
To repeat myself from an earlier comment. How does one even arrive at the number 200 based on the complexity of the problem? Secondly not all 2000 will be worki
by thisisit 10y ago
To repeat myself from an earlier comment. How does one even arrive at the number 200 based on the complexity of the problem? Secondly not all 2000 will be working on their core app. There will be solutions required at each level. For example in some countries cab services are provided by larger contractors employing drivers and not individual drivers themselves. So Uber needs to have a billing system which collates data from their individual drivers and then calculates the payout to the company. This requires a separate set of engineers, not working on the core app.
And then there are HR systems, Finance Systems, every bit they are not contracting to an Indian Service company has to be handled by an "engineer".
- wellpast 10y agoOkay. Then how many engineers would Uber need to have for you to say "that's too many"?
- thisisit 10y agoI don't really know. What I do know is people seem to misunderstand engineering team size as a simple sum of people working on the Uber app. It is not only the android/ios developer or the full stack developer who is an engineer in Uber. An IT administrator who helps people, technical or non-technical, with their work laptops also qualifies as an engineering team staff to the outside world.
- ufmace 10y agoWhat makes it your or my place to decide that? They're a private company, and they have plenty of profit motive for efficiency. If they didn't think they were getting value from all of those engineers, then they would fire them and save themselves some money. Or are we going to argue that corporate executives aren't greedy enough?