This sounds good in theory, but in practice what you're describing will not be stable, sustainable, or at all practical.
You can't really run this sort of revolving-door "talent pool" project for long, certainly not a massive project of 100+ engineers. If every time a new project opens up, its hiring managers get to unreservedly raid the "talent pool" project for star performers, then pretty soon this project will be known internally as a joke, that is at priority zero, and any but its most dysfunctional engineers will be rushing to other projects, either internally within Google or (more likely) outside it.
You'll end up with all the best people quickly leaving for real projects where they can do real work on real products for real pay (bonuses for revenue-yielding projects are much, much higher than for anything else). The project itself will be a dysfunctional joke since you can't run it with the best talent routinely recruited away. The only people who will work on it will be dead weight who don't care to work on real products or even make any progress on a bogus one, which is the definition of the sort of people you should immediately fire.
In fact, the whole initial "pool" of candidates sounds toxic, if the only reason they were given this project is that any other _real_ work would cause them to leave. As a hiring manager, I'd be very skeptical of anyone who seemed to be this sort of indifferent diva, and would not be looking to hire them.
To sum up, it's a fun little theory, but extremely unlikely to work in practice, and I've never seen anything like it. The simple explanation that Fuchsia is an Android successor is much more likely, and there's zero evidence for the far-fetched "talent pool" explanation other than an unsupported comment by some anonymous "one person who has spoken to Fuchsia staff". It's ridiculous.
You can't really run this sort of revolving-door "talent pool" project for long, certainly not a massive project of 100+ engineers. If every time a new project opens up, its hiring managers get to unreservedly raid the "talent pool" project for star performers, then pretty soon this project will be known internally as a joke, that is at priority zero, and any but its most dysfunctional engineers will be rushing to other projects, either internally within Google or (more likely) outside it.
You'll end up with all the best people quickly leaving for real projects where they can do real work on real products for real pay (bonuses for revenue-yielding projects are much, much higher than for anything else). The project itself will be a dysfunctional joke since you can't run it with the best talent routinely recruited away. The only people who will work on it will be dead weight who don't care to work on real products or even make any progress on a bogus one, which is the definition of the sort of people you should immediately fire.
In fact, the whole initial "pool" of candidates sounds toxic, if the only reason they were given this project is that any other _real_ work would cause them to leave. As a hiring manager, I'd be very skeptical of anyone who seemed to be this sort of indifferent diva, and would not be looking to hire them.
To sum up, it's a fun little theory, but extremely unlikely to work in practice, and I've never seen anything like it. The simple explanation that Fuchsia is an Android successor is much more likely, and there's zero evidence for the far-fetched "talent pool" explanation other than an unsupported comment by some anonymous "one person who has spoken to Fuchsia staff". It's ridiculous.