imo, self-driving cars should probably be a separate company owned by the parent... and likely is, and doesn't even apply to the thousands of developers alone t

imo, self-driving cars should probably be a separate company owned by the parent... and likely is, and doesn't even apply to the thousands of developers alone they are stafing. And for each developer there is probably 1:1 for other staff... in my experience for a team of 4 devs, you usually get 1/2 time for a PM, 1/2 time for an owner, a QA, 1/3-1/4 dba and a BA and maybe 1/4 time of a designer. The primary application could probably do very well with 3-5 dedicated teams to portions of the application with less general conflict and bottlenecking... The support staff would need to scale to meet the larger demands though. Given their funding, even top-tier engineers at $250-300k (Northern California) base would still be less expensive than hundreds or thousands of developers. Putting the self-driving car research into a separate company. The site is not THAT complex, and they are, or should be leveraging a number of existing tools. They probably have a byzantine codebase that takes days to make what should be a 15 minute change at this point because of the shear numbers.