The amount of code you can write grows linearly with number of engineers, but communication costs grow quadratically. Therefore, the speed at which you can execute is inversely proportional to the size of the team, unless you can cut communication costs. Established projects can do this with architectural decisions that prevent one engineer from needing to know about or communicate with other engineers working on unrelated parts of the product. New projects cannot, because the architecture hasn't been established yet. That's why every innovative product grows out of a small team.
Not to mention that the monumental risk that a company takes on when they do moonshot projects. There are very lax expectations of any profitability in the near term, so there seems to be large disincentives to invest heavily ... esp when the company is public and facing quarter by quarter scrutiny.
Many engineers at tech companies like Google, Facebook, Microsoft, etc. report that they feel overqualified for their work. I imagine many yearn for the chance to work on moonshot projects like these - is there any reason why secretive research divisions at these companies are so small, when there is plenty of engineering talent to go around internally?